What this category's data looks like
This page focuses on the student status changes and graduation eligibility review category. The source materials are three forms exported from the academic affairs system—leave/resumption of schooling applications, major transfer applications, and graduation review checklists—along with their attachment receipts. The update cadence rolls forward by semester batch, and each batch contains four rounds: application submission, department preliminary review, academic affairs office re-review, and result publication. Field characteristics center on name, student ID, change type, effective date, original major and target major, review conclusion, signature field, and receipt number. When the three materials enter workflow orchestration, their roles differ: leave/resumption of schooling applications and major transfer applications serve as branch trigger bases, the graduation review checklist serves as the summary verification worksheet, and receipts and signature pages serve as version synchronization evidence. For the same student ID, the major name, course count, and effective date in the major transfer application and the graduation review checklist must be aligned item by item; if a signature or receipt is missing, that record is deemed non-handoverable.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The handoverable deployment state and operation 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 state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Leave/resumption of schooling application | Fields include student ID, change type, effective date, signature field, and receipt number, and are aligned item by item with the record of the same name in the major transfer application | Check the options and branch connections one by one in the node; after triggering once, view the node status in the run records; and reference the selection result variable in a subsequent node for a trial run, verifying whether nodeId and variables are consistent |
| Major transfer application | The original major and target major, course count, and effective date must be consistent with the graduation review checklist; if a signature or receipt is missing, mark it as inconsistent | Check the branch connection corresponding to each option, check whether the interaction state is recorded, confirm that the selection result variable has been passed to subsequent nodes, and verify the reference path of variables |
| Graduation review checklist | The review conclusion, course count, and effective date must match the two materials, the leave/resumption of schooling application and the major transfer application; if the version is not synchronized, pause the handover | Check the branch direction and interaction state in the run records, compare the names, counts, dates, and signature receipts of the three materials item by item, and verify the node status corresponding to nodeId |
Three common errors
- Symptom: For the same student ID, the major name, course count, and effective date in the major transfer application and the graduation review checklist do not match. Cause: The two materials were exported in different batches, the versions were not synchronized, and the receipt number is missing.
- Symptom: The signature field of the leave/resumption of schooling application is blank, but the handover form marks it as verified. Cause: The receipt was not archived with the material, and verification only looked at the electronic form without looking at the signature page.
- 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 a trial for each option one by one, check the branch direction and interaction state in the run records, and confirm that the selection result variable has been passed to subsequent nodes; verify the correspondence between variables and nodeId in the run records, record the reference count separately according to the array length, and budget the reference content by checking the tokens of the referenced text.
Business testing: verify item by item according to the handover form once, see which item is missing from the records, and focus on comparing the names, counts, dates, and signature receipts of the leave/resumption of schooling application, major transfer application, and graduation review checklist.
- Check the options and branch connections one by one in the node; after triggering once, view the node status in the run records, confirm that the selection result variable has been passed to subsequent nodes and run a trial once, and verify
nodeIdandvariables. - Verify the fields, dates, and signatures of the leave/resumption of schooling application, major transfer application, and graduation review checklist item by item according to the handover form; when a name or count does not match, mark the version as unsynchronized and pause the handover.