What this category's data looks like
This page focuses on the student status changes and graduation eligibility review category. The materials come from leave-of-absence and return-to-school applications, major transfer applications, and graduation review checklists, updated by semester milestones and status change events. Field characteristics include student ID, name, status change type, effective date, approval signature, course credits, and graduation conclusion. After leave-of-absence and return-to-school applications and major transfer applications enter the workflow, they serve as the branch basis for the user selection node, determining the subsequent authorization scope; the graduation review checklist serves as the data source document for external services, carrying the publishable graduation conclusion and destination fields. The three types of materials each assume the entry, branch, and output roles in the authorized access and external services stages, and the external entry and authorization scope are completed by subsequent nodes continuing execution according to the branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branch), outputting the branch direction and interaction state records. The external entry and authorization scope are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the 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-of-absence and return-to-school application | Whether the fields, dates, and signatures are consistent with the major transfer application | Check the options and branch connections one by one in the node, and reference variables to run a test once |
| Major transfer application | Whether the name, quantity, and date of the same record match across the two materials | Trigger the user selection node once and check the node status in the run records |
| Graduation review checklist | Whether the version is synchronized, and whether signatures or receipts are missing | Reference the selection result variable in a subsequent node and run a test once, checking the nodeId reference |
| External entry and authorization scope | Whether the visitor identity matches the visible scope, and unauthorized access is not visible | Access once with a restricted identity and see whether the visible scope matches the settings |
Three common errors
- Symptom: The status change dates for the same student ID do not match between the leave-of-absence and return-to-school application and the major transfer application. Cause: The two materials are entered separately without version synchronization, causing the branch direction and authorization scope to be misaligned.
- Symptom: The graduation review checklist is missing a signature or receipt but still enters external services. Cause: The signature status is not verified during the material circulation step, and the node continues execution along the default branch.
- 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
Acceptance for this feature: run a test for each option one by one, check the branch direction and interaction state in the run records, and confirm that the variables and nodeId references are correct.
Business test: access once with a restricted identity and see whether the visible scope matches the settings.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a test once, checking
variablesandnodeId.