What this category's data looks like
This page focuses on three types of materials in the student scholarships, grants, loans, and hardship determination category: the family economic hardship determination form, the scholarship/grant application form, and the loan receipt. The determination form is filled out by the student, reviewed by the class, and submitted level by level; its fields include family population, income sources, hardship level, and signature fields. The application form is updated as each academic year's scholarship and grant programs open; its fields include student ID, program name, amount tier, and date. The loan receipt is issued by the bank or the financial aid center; its fields include contract number, disbursement date, and receipt status. The three types of materials play different roles when they enter the workflow: the determination form serves as the underlying record of hardship status, the application form serves as the evidence for the current application, and the receipt serves as proof of loan disbursement. The update rhythm is affected by semester applications, bank disbursements, and review announcements; the field characteristics are multi-table crossover, dense signatures and dates, and versions rolling with batches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. When the user selection node is triggered, the conversation enters an interactive state and the workflow status is recorded. After the user completes the selection, execution continues along the branch corresponding to the selected option. The "exception list and review conclusion" is then completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Family economic hardship determination form | Whether family population, income sources, hardship level, signature fields, and date are consistent with the application form; if a signature is missing, it is listed as an exception | Check the options and branch connections one by one in the node, use variables to reference the determination form fields, and compare signatures and dates |
| Scholarship/grant application form | Whether student ID, program name, amount tier, and application date match the determination form and receipt; if the version is not synchronized, it is listed as an exception | Reference the branch corresponding to nodeId in subsequent nodes, and run a test once to see whether the selection result variable has been passed to subsequent nodes |
| Loan receipt | Whether contract number, disbursement date, and receipt status match the amount tier in the application form; if the receipt is missing, it is listed as an exception | Trigger a user selection node once, check the node status and branch direction in the run record, and verify the receipt fields |
| Exception list and review conclusion | Whether exception items are supported by original records, whether reviewer signatures are complete, and whether conclusions can be traced back to source materials | Check variables and nodeId in the run record, and confirm that the branch direction is consistent with the interaction status record |
Three common errors
- Phenomenon: The family population and income source dates for the same student do not match between the determination form and the application form, and during review it is impossible to determine which one prevails. Cause: The two forms were filled out in different batches, versions were not synchronized, and no field-level comparison was performed.
- Phenomenon: The loan receipt is missing or the receipt status has not been updated, and the amount tier in the application form cannot be matched with the disbursement date. Cause: The receipt is issued by an external institution and was not collected into the same record in time; the process still proceeds to the next stage when the receipt is missing.
- Phenomenon: After selecting a certain option, the default branch is still followed; after the interaction is completed, the process stops and the exception list is not generated. 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 of this function: run tests for each option one by one, check the branch direction and interaction status in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes and that the status is recorded.
Business test: create an exception record and see whether it can be traced back to the source materials, and check whether the fields, dates, and signatures of the determination form, application form, and receipt are consistent.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and view the node status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a test once to confirm that the exception list and review conclusion can continue execution along the branch and be traced back to the source materials.