What this category's data looks like
This page is for student awards, grants, loans, and hardship determination scenarios. Material sources include the family economic hardship determination form, the scholarship and grant application form, and the loan receipt, as well as class review records, public announcement lists, and the financial aid ledger. Determination forms are submitted centrally by academic year, application forms open and close by batch, and loan receipts are returned in batches according to the disbursement cycle, with updates on a weekly basis. Field characteristics center on name, student ID, class, hardship level, application amount, loan amount, date, and signature fields; signature and receipt status determine whether materials can enter statistics. After materials enter the workflow, the determination form serves as the basis for identity and level, the application form serves as the basis for project and amount, and the loan receipt serves as the basis for arrival and confirmation; together, the three support progress records and statistical verification.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Family economic hardship determination form | Fields include name, student ID, hardship level, date, and signature; the name, level, and date of the same record as in the application form must be consistent, and the signature must not be missing | Check the name, student ID, level, and date of the determination form and application form one by one, and record inconsistent items |
| Scholarship and grant application form | Fields include project name, application amount, batch date, and signature; the amount, quantity, and date of the same record as in the ledger must be consistent | Extract one week of application forms, check the amounts against the ledger totals, and mark exceptions and scope notes |
| Loan receipt | Fields include loan amount, arrival date, and receipt number; the amount and date of the same record as in the application form must be consistent, and the receipt must not be missing | Check the receipt number and arrival date, check whether receipts are complete, and record missing items |
| User selection node | Each option corresponds to one branch; the options and branch connections must be checked one by one, and the selection result variable must be passed to subsequent nodes | Check the options and branch connections one by one in the node, reference variables and nodeId, and run a test once |
Three common errors
- Phenomenon: The name, level, and date of the same record do not match between the determination form and the application form. Cause: The two forms are entered separately and no field-level comparison is performed, lacking a unified verification scope.
- Phenomenon: A loan receipt is missing a signature or the receipt has not been returned, yet statistics still include it in the total. Cause: Receipt status is not synchronized to the ledger, and missing items are not marked as exceptions.
- Phenomenon: After selecting an option, the default branch is still followed, or 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 referenced correctly.
How to verify the setup
This feature acceptance: run a test for each option one by one, and check the branch direction and interaction status in the run records; reference variables and nodeId in subsequent nodes to confirm that the selection result has been passed.
Business test: use one week of records to check the totals, see whether the scope and exceptions are clearly stated, and whether the number of records matches the statistical count.
- Check the options and branch connections one by one in the node, trigger it once, then view the node status in the run records to confirm that it enters the interaction state and that the branch direction is correct.
- Reference the selection result variable in a subsequent node and run a test once to confirm that
variablesandnodeIdare available, and that the process continues downward after the interaction is completed.