What this category's data looks like
This page addresses the scenarios of student awards, grants, loans, and hardship determination. Materials come from three types: family economic hardship determination forms, scholarship and grant application forms, and loan receipts. Determination forms are submitted centrally by academic year, with fields including family members, income sources, hardship level, and signature; application forms open by batch, with fields including student ID, award name, amount, and date; loan receipts are returned according to the disbursement cycle, with fields including contract number, disbursement amount, and acknowledgment. The three types of materials have different roles when entering the workflow: the determination form serves as the eligibility basis, the application form serves as the declaration basis, and the receipt serves as the proof of arrival. The update rhythm is affected by the semester and disbursement cycle. Drafts and handover records can only be issued after fields are complete, the responsible person is clear, and the version and date are consistent.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The issuable material drafts and handover records are completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Family economic hardship determination form | Fields complete, responsible person clear, version and date consistent | Check options and branch connections one by one in the node, trigger a view of the node status in the run record, and test-run with reference to variables and nodeId |
| Scholarship and grant application form | The name, quantity, and date of the same record do not match between the two materials | Reference the selection result variable in subsequent nodes and test-run, checking whether the name, amount, and date in the application form and determination form are consistent |
| Loan receipt | Missing signature or receipt, version not synchronized | Trigger an interaction, view the node status in the run record, and check whether the receipt signature and version date are synchronized |
| Handover record | Responsible person clear, version and date consistent | Check options and branch connections one by one in the node, and confirm that the handover record is generated according to the branch direction |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the determination form and the application form. Cause: The fields in the two places are maintained separately, and the same variable is not uniformly referenced before branching.
- Symptom: The version is not synchronized, and the dates of the draft and handover record are inconsistent. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue execution according to the branch.
- Symptom: Missing signature or receipt, and the material cannot be issued. Cause: A certain option is selected but the default branch is still taken, and the signature and receipt nodes are not triggered.
How to verify the setup
This function acceptance: test-run each option one by one, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and verify with reference to variables and nodeId.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check options and branch connections one by one in the node, trigger an interaction, and view the node status in the run record.
- Reference the selection result variable in subsequent nodes and test-run once, confirming that the branch direction is consistent with the interaction status record.