What this category's data looks like
Student status changes and graduation qualification review involve three types of materials: leave/resumption applications, major transfer applications, and graduation review checklists. A leave/resumption application contains the change type, effective date, and signature field; a major transfer application contains the transfer-in and transfer-out majors, assessment conclusion, and receipt; a graduation review checklist contains course names, credits, and review conclusion. The materials come from this institution's academic affairs system and paper archives, are updated as semester batches progress, and the current stamped version is authoritative. When entering workflow orchestration, the leave/resumption application serves as the change trigger source, the major transfer application serves as the basis for qualification changes, and the graduation review checklist serves as the ledger for graduation conclusions; together, the three support the generation of basis entries that can be traced back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Basis entries that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Leave/resumption application | Fields, dates, and signature must be consistent with the current version, and the change type must match the original text | Check the change type, effective date, and signature field; confirm the nodeId correspondence in the node options and branch connections |
| Major transfer application | Transfer-in and transfer-out majors, assessment conclusion, and receipt must be complete and consistent with the checklist names | Compare the major names and dates in the two materials; run a trial to see whether variables are passed to subsequent nodes |
| Graduation review checklist | Course names, credits, and review conclusion must correspond one by one with the application records | Check courses and credits one by one, and inspect entries missing signatures or receipts; trigger once to view node status in the run record |
| User selection node | Each option corresponds to one branch, and the interaction state is recorded | Run a trial for each option and check the branch direction and interaction state; confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: The name and date of the same record do not match between the leave/resumption application and the graduation review checklist. Cause: The two materials are entered separately and version synchronization is not performed, so the current version is not unified.
- Symptom: A major transfer application is still treated as valid basis when it lacks a signature or receipt. Cause: The signature field and receipt field are not verified during material archiving, and the version is not synchronized.
- 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 referenced correctly.
How to verify the setup
Acceptance of this feature: run a trial for each option, check the branch direction and interaction state in the run record, and confirm the correspondence between nodeId and variables.
Business test: ask a basis question spanning materials and see whether the answer provides a traceable source.
- Check the options and branch connections one by one in the nodes, and trigger once to view node status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the branch direction is consistent with the recorded interaction state.