What this category's data looks like
This page covers three types of materials in the student awards, grants, loans, and hardship determination scenario: the family financial hardship determination form, the scholarship/grant application form, and the loan receipt. The determination form comes from student submissions and class review, is submitted centrally by academic year, and is updated as the hardship level is re-reviewed; the application form comes from individual applications and departmental preliminary review, opens by batch, and is locked after the deadline; the loan receipt comes from the handling bank and the student-origin institution, and is returned according to the disbursement cycle. After the materials enter the workflow, the determination form plays the role of hardship level and review basis, the application form plays the role of award category and amount range, and the receipt plays the role of loan arrival and confirmation signature. Field characteristics center on name, student ID, hardship level, award name, amount, date, and signature; versions change with academic year and batch, and fields, dates, and signatures must be checked separately by material type for completeness and consistency.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution according to the branch. When the 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 |
|---|---|---|
| Family financial hardship determination form | Fields include hardship level and review date; the signature section must have the reviewer's and student's signatures; if either is missing, it is deemed undetermined | Check the hardship level, review date, and signatures, and confirm consistency with the reference in the application form |
| Scholarship/grant application form | The award name, amount range, and application date must match the hardship level in the determination form; cross-level applications are not allowed | Check the award name and amount by batch, and check whether the date falls within the open period |
| Loan receipt | The receipt number, arrival date, and handler signature must be complete, and the receipt amount must match the loan amount in the application form | Check the receipt number and arrival date, and check whether the signature and receipt are missing |
| User selection node | Each option corresponds to one branch; when entering the node, the interaction state is recorded, and the selection result variable is passed to subsequent nodes | In the node, check the options and branch connections one by one, and run a test referencing variables and nodeId |
Three common errors
- Symptom: the hardship level names for the same student do not match between the determination form and the application form. Cause: the versions of the two materials are not synchronized; the determination form has been re-reviewed while the application form still uses the old level.
- Symptom: the loan receipt amount does not match the loan amount and date in the application form. Cause: the receipt is returned by disbursement batch, and the application form has not updated the amount and date by batch.
- Symptom: after selecting an option, the default branch is still taken, or the process stops after the interaction is completed. Cause: the options and branch connections were not checked one by one, and the interaction state was not recorded.
How to verify the setup
Feature acceptance: run a test for each option one by one, check the branch direction and interaction state in the run records, and reference variables and nodeId in subsequent nodes to confirm that the selection result variable has been passed.
Business testing: check each item once according to the handover list, see which record is missing, and confirm that the version, connection, and task record are consistent.
- In the user selection node, check the options and branch connections one by one, and trigger once to view the node state in the run records.
- Reference the selection result variable in a subsequent node and run a test once to confirm that the branch direction and interaction state record are consistent.