What this category's data looks like
Student status establishment and changes in primary and secondary schools cover three core types of materials: student status records, transfer applications, and suspension/resumption materials. A student status record consists of basic information and change records, with fields including name, ID number, national student status number, enrollment status, and change date; a transfer application includes the transferring-in and transferring-out schools, application date, signatures from both parties, and receipt; suspension/resumption materials include the reason for suspension, start and end dates, resumption verification, and seals. The materials are submitted by school academic affairs offices and homeroom teachers, and the update cadence is triggered by semesters and change events, featuring multiple versions, multiple signatures, and a tightly linked date chain. When entering workflow orchestration, the three types of materials each play different roles: the student status record serves as the master record providing baseline fields, the transfer application and suspension/resumption materials serve as change evidence driving branch direction, and the handover record binds the responsible person and receipt status.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The material drafts and handover records that can be issued are completed by subsequent nodes continuing execution along the branch. When the user selection 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 | Fields are complete and consistent with the name, national student status number, and change date in the transfer application and suspension/resumption materials | Compare the three materials field by field, and check whether signatures and receipts are complete |
| Transfer application | The application date is consistent with the change date in the student status record, and there are no missing items in the signatures from both parties and the receipt | Draft one according to the template, and check whether the version number and date chain are synchronized |
| Suspension/resumption materials | The suspension start and end dates match the resumption verification records, and the seals are complete | Reference variables and nodeId to locate the branch, and check the interaction status in the run records |
| Handover record | The responsible person is clear, the version and date are consistent, and the receipt status of the next step is traceable | Trigger a handover once, and see whether missing items are blocked |
Three common errors
- Symptom: The name and national student status number of the same student do not match between the student status record and the transfer application. Cause: The two materials were drafted separately, without field-level comparison and version synchronization.
- Symptom: The start and end dates in the suspension/resumption materials are inconsistent with the change date in the student status record. Cause: The date chain was not maintained against the same baseline, and the update cadence was not synchronized.
- Symptom: The handover record lacks a signature or receipt, and the next step cannot be signed for. Cause: The responsible person was not specified in the node branch, and the handover status was not recorded.
How to verify the setup
Feature acceptance: Try running each option one by one, check the branch direction and interaction status in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the nodes, check the options and branch connections one by one, and run once to view the node status in the run records.
- Reference the selection result variable in a subsequent node and run it, and confirm that
variablesandnodeIdpoint to the correct branch.