What this category's data looks like
This page focuses on primary and secondary school student status establishment and changes, involving three types of materials: student status records, transfer applications, and suspension/resumption materials. Student status records are entered by the student status administrator when establishing status for new students; the fields include name, ID number, national student status number, enrollment status, and guardian information, with an update cadence of centralized verification at the beginning of each semester and updates during the semester as changes occur. Transfer applications are submitted by the receiving or sending school; the fields include sending school name, receiving school name, application date, seals from both parties, and receipt. Suspension/resumption materials are submitted by parents and reviewed by the school; the fields include suspension start and end dates, resumption date, hospital certificate number, and signature. When the three types of materials enter workflow orchestration, their roles differ: student status records are the master record, while transfer applications and suspension/resumption materials are the basis for triggering changes, and nodes determine branch direction based on their fields.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The handover-ready deployment status and operation records are continued and completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Student status record | Whether name, ID number, national student status number, enrollment status, and guardian information correspond item by item with the transfer application and suspension/resumption materials, and whether dates and signatures are complete | Compare the three materials field by field, verify whether the name, quantity, and dates of the same record match, and separately flag missing signatures or receipts |
| Transfer application | Whether the sending school name, receiving school name, application date, seals from both parties, and receipt are consistent with the enrollment status change in the student status record | Check the options and branch connections one by one in the node, confirm the branch direction corresponding to the transfer application, and reference the selection result variable in a subsequent node and run a trial once |
| Suspension/resumption materials | Whether the suspension start and end dates, resumption date, hospital certificate number, and signature are consistent with the enrollment status in the student status record, and whether the version is synchronized | Trigger a user selection node once, check the node status in the run record, verify the interaction status and branch direction, and confirm there are no missing items |
| Deployment status and operation records | Whether version, connection, and task records are consistent, and whether each item in the handover form is traceable | Check the passing of nodeId and variables in the run record, and confirm that the process continues downward after the interaction is completed |
Three common errors
- Symptom: The name and dates for the same student do not match between the student status record and the transfer application. Cause: The two materials were entered separately, were not compared field by field against the same record, and the versions were not synchronized.
- Symptom: Suspension/resumption materials are missing a signature or receipt but still proceed to the next stage. Cause: The handover form did not verify signatures and receipts item by item, and missing items were not flagged.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and check the tokens of the reference text related to nodeId, variables, and quoteMaxToken; record the array length separately.
Business testing: verify each item once according to the handover form, see which record is missing, and confirm that version, connection, and task records are consistent.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and view the node status and interaction status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, check the passing of
nodeIdandvariables, and confirm that the process continues downward after the interaction is completed.