What this category's data looks like
Student awards, grants, loans, and financial hardship determination involve three core materials: the family financial hardship determination form, the scholarship and grant application form, and the loan receipt. The determination form is submitted by the student with family circumstances and supporting information, and is the entry point for eligibility judgment; the application form carries forward the determination result and states the applied-for item and amount; the loan receipt is filled in back by the processing step, recording disbursement and acknowledgment. The fields of the three materials overlap, and name, student ID, amount, and date must be consistent. Material sources are scattered across the class, department, and financial aid center, and the update rhythm advances with the semester batch: the determination form and application form come out first, and the loan receipt is supplemented later. When the materials enter the form input node, each assumes its own field collection role: the determination form collects family information, the application form collects application intent, and the loan receipt collects acknowledgment records; after submission, the field values are passed to subsequent nodes.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The material drafts that can be issued and the handoff records are completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters the interaction state and records the workflow state; after the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Family financial hardship determination form | Fields correspond to the determination dimensions, key items are marked as required, and date and signature fields are complete | Check the field names one by one in the node configuration, check the required settings, and do a trial run to confirm that subsequent nodes can retrieve the corresponding field values |
| Scholarship and grant application form | The applied-for item, amount, and student ID are consistent with the determination form records, and the version and date are synchronized | Compare item by item against the determination form for name, quantity, and date, check the version number and signature fields, and confirm there are no missing items |
| Loan receipt | The disbursement amount, date, and acknowledgment person are consistent with the application form records, and the receipt has been signed | Check the correspondence between the receipt fields and the application form fields, and check whether the signature and date are complete |
| formInputResult and selectResult | The form fields correspond one-to-one with the material fields, and after submission the field values can be referenced by subsequent nodes | Reference the formInputResult and selectResult fields in subsequent nodes and do a trial run to confirm the values are retrieved; check that the userSelect options are consistent with the material options |
Three common errors
- Symptom: The name, amount, and date for the same student do not match between the determination form and the application form. Cause: The two materials were drafted separately, the fields were not cross-checked, and the versions were not synchronized.
- Symptom: The loan receipt lacks a signature or the receipt was not returned, so the material cannot enter the next step. Cause: The acknowledgment field was not marked as required, and the signature and date were not checked item by item during handoff.
- Symptom: After submission, the conversation remains in the interaction state, and subsequent nodes cannot retrieve the field values. Cause: Required items can still be submitted when empty, or the field names are inconsistent with the subsequent references.
How to verify the setup
Acceptance for this feature: fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that the field values of formInputResult and selectResult are both passed correctly, and that submission is blocked when required items are empty.
Business test: draft one according to the template and complete one handoff, and see whether missing items are blocked.
- Check the field names and required settings one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and do a trial run to confirm that the corresponding field values can be retrieved after submission.