What this category's data looks like
Student status establishment and changes in primary and secondary schools involve three core types of materials: student status records, transfer applications, and leave/resumption materials. Student status records mainly consist of student identity information, enrollment status, and guardian fields, and are continuously updated with semester registration and change registration; transfer applications include the names of both the transferring-in and transferring-out schools, dates, handler signatures, and receipts, and are filed separately for each transfer event; leave/resumption materials record the reason for leave, start and end dates, approval opinions, and signatures, and are maintained on a rolling basis according to the approval cycle. The three types of materials play different roles when entering workflow orchestration: student status records provide the basic fields and current status, while transfer applications and leave/resumption materials provide the event-level basis for changes, jointly supporting the generation of the version ledger and change records and the synchronization of references.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to 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 records | Whether the fields, dates, and signatures are consistent with the current version, and whether the names and quantities match | Check the options and branch connections one by one in the node, compare the record fields with the corresponding records in the transfer application and leave/resumption materials, and reference variables and nodeId in subsequent nodes for a trial run |
| Transfer application | Whether the names, quantities, and dates of the same record are consistent across the two materials, and whether the signatures and receipts are complete | Reference the selection result variable in a subsequent node and run it once, check whether the names and dates of both the transferring-out and transferring-in parties are synchronized, and verify the branch direction corresponding to nodeId |
| Leave/resumption materials | Whether the version is synchronized, whether the old version is traceable, and whether references are updated synchronously | Trigger the user selection node once, view the node status and branch direction in the run record, and confirm that variables have been passed to subsequent nodes |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | Reference variables and nodeId in subsequent nodes, check the branch direction and interaction status records, and confirm that the tokens of the referenced text and the number of array items are recorded separately |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the student status record and the transfer application. Cause: The field sources are not unified, and the materials are maintained separately.
- Symptom: The version of the leave/resumption materials is not synchronized, and the old version is still referenced. Cause: After the change, the ledger and reference targets were not updated.
- Symptom: The transfer application lacks a handler signature or receipt. Cause: The approval step was not recorded, and the materials are incomplete.
How to verify the setup
Feature acceptance: Run each option one by one, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and verify the references of variables and nodeId.
Business testing: Change one piece of content, see whether the version number and references are updated synchronously, and confirm that the current version is unique and the old version is traceable.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference
variablesandnodeIdin subsequent nodes and run once, and check the interaction status and branch direction.