What this category's data looks like
Student status changes and graduation eligibility review cover three types of materials: leave/resumption of schooling applications, major transfer applications, and graduation review checklists. Leave/resumption of schooling applications include the change type, effective term, and signature field; major transfer applications include the names of the transfer-in and transfer-out majors, the number of course recognitions, and the date; graduation review checklists include total credits, required components, review conclusion, and receipt. The material sources are academic affairs system exports and department submissions. The update cadence is centralized submission according to semester milestones; change-type materials are triggered immediately with the application, while graduation reviews are aggregated by batch. When entering workflow orchestration, leave/resumption of schooling applications and major transfer applications serve as pre-branch inputs, and graduation review checklists serve as the summary verification object. Each of the three plays the role of branch decision basis and handover evidence, and fields, dates, and signatures must be aligned item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Draft materials that can be issued and handover records" are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 | Whether the change type, effective term, and signature field are complete and consistent with the date of the major transfer application | Check the options and branch connections one by one in the node, and reference variables and nodeId in subsequent nodes to run a trial once |
| Major transfer application | Whether the names of the transfer-in and transfer-out majors, the number of course recognitions, and the date match the graduation review checklist | Trigger the user selection node once and check the node status and branch direction in the run record |
| Graduation review checklist | Whether total credits, required components, review conclusion, and receipt signature are complete and the versions are synchronized | Reference variables and nodeId in subsequent nodes to locate the branch, and verify the name and quantity of that record in the two materials |
| Handover record | Whether the responsible person, receipt time, and version number are clear and consistent with the date of the material draft | Draft one according to the template and complete one handover, then check whether missing items are blocked |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the leave/resumption of schooling application and the major transfer application. Cause: The two materials are filled out separately, lacking a unified field verification and version comparison step.
- Symptom: The version of the graduation review checklist is not synchronized, and the dates of the draft and the signed receipt are inconsistent. Cause: After the material is updated, the branch decision is not re-triggered, and subsequent nodes still reference old variables.
- Symptom: The handover record lacks a signature or receipt, and the responsible person is unclear. Cause: The branch direction is not recorded in the run log, and the receipt step does not continue execution according to the option branch.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and verify by referencing variables and nodeId in subsequent nodes.
Business test: draft one according to the template and complete one handover, then see whether missing items are blocked.
- 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, run a trial once, and check the node status in the run record.