What this category's data looks like
Student awards, grants, loans, and hardship determination involve three types of materials: the family financial hardship determination form, the scholarship/grant application form, and the loan receipt. Sources include student submission, departmental preliminary review, financial aid center re-review, and bank receipts. The update cadence advances by academic year and batch: the determination form is refilled as family circumstances change, the application form is adjusted with each review round, and the loan receipt is supplemented according to the disbursement cycle. Field characteristics center on name, student ID, hardship level, amount, date, and signature fields; the absence of either a signature or a receipt affects archiving. Once the three types of materials enter the workflow, their roles differ: the determination form serves as the entry material for eligibility judgment, the application form serves as the object for verifying award/grant level and amount, and the loan receipt serves as the supporting material for the disbursement result. Material versions and reference relationships must be maintained in the same ledger, with old versions retained for traceability and the current version kept unique.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interactive state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Family financial hardship determination form | Whether the fields, date, and signature are consistent with the application form | Compare name, student ID, hardship level, and signature date item by item, and check the option branch connections and nodeId |
| Scholarship/grant application form | Whether the name, quantity, and date of the same record match across the two materials | Reference variables in subsequent nodes for a trial run, and check whether the amount on this form and the level on the determination form are synchronized |
| Loan receipt | Whether the receipt is complete and the version is synchronized | Check the receipt number and disbursement date, and confirm that the old version is traceable and the current version is unique |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously |
Three common errors
- Symptom: The hardship level for the same student does not match between the determination form and the application form. Cause: The two materials are maintained separately, versions are not synchronized, and references still point to the old version record.
- Symptom: The loan receipt lacks a signature or the receipt number is missing, making disbursement impossible to confirm at archiving. Cause: The receipt supplementation step was not checked against the application form date, and the materials were not updated synchronously.
- Symptom: After selecting an option, the default branch is still taken, 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 trial for each option one by one, check the branch direction and interaction state in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check the correspondence between variables and nodeId in the run records.
- In the node, check the options and branch connections one by one, trigger once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction is consistent with the interaction state record.