What this category's data looks like
This page focuses on Q&A intake and missing-item follow-up in student status changes and graduation eligibility review. The materials come from leave and return-to-study applications, major transfer applications, and graduation review checklists, with updates synchronized on a rolling basis by semester batch and departmental receipt. Field characteristics center on name, student ID, change type, effective date, signature, and receipt number. The three types of materials play different roles when entering the workflow: leave and return-to-study applications and major transfer applications serve as the basis for status changes, the graduation review checklist serves as the master list for eligibility verification, and intake records and supplemented question items are generated by subsequent nodes continuing execution along branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. Intake records and supplemented question items are then completed by subsequent nodes continuing execution along branches.
| Object | Check | Verification action |
|---|---|---|
| Leave and return-to-study application | Field check: whether change type, effective date, signature, and receipt number are complete; missing items enter the follow-up branch | Trigger the user selection node, check options and branch connections one by one in the node, and reference variables and nodeId to view the run record |
| Major transfer application | Date and signature check: whether transfer-in and transfer-out dates connect, whether signature or receipt is missing; missing items enter the follow-up branch | Reference the selection result variable in a subsequent node and run a test once, checking whether the name and date of this application match the graduation review checklist |
| Graduation review checklist | Checklist field check: whether course names, quantities, dates, and status change records match, and whether the version is synchronized | Trigger an interaction status once, view the node status in the run record, and check whether the checklist version and status change records are synchronized |
| Intake records and supplemented question items | Missing items are identified and followed up, answers have material basis, and are forwarded to the handler | Reference variables in a subsequent node and run a test, checking whether the follow-up items correspond to the material fields |
Three common errors
- Symptom: The name and date of the same record do not match between the leave and return-to-study application and the graduation review checklist. Cause: The versions of the two materials are not synchronized, and the field definitions are inconsistent.
- Symptom: A major transfer application is missing a signature or receipt but still enters a subsequent branch. Cause: Options and branch connections were not checked one by one, and the missing item was not identified.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The selection result variable was not passed to subsequent nodes, or the same session repeatedly entered the interaction.
How to verify the setup
In the node, check options and branch connections one by one, and trigger once to view the node status in the run record.
Reference variables and nodeId in a subsequent node and run a test once, checking whether the variable takes effect.
- This feature's acceptance: run tests 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, the status is recorded, and the selection result variable has been passed to subsequent nodes.
- Business test: submit a question missing key information and see whether it follows up first before answering.