What this category's data looks like
This page focuses on student awards, grants, loans, and hardship determination materials, covering three types: the family financial hardship determination form, the scholarship/grant application form, and the loan receipt. The determination form is submitted by the student and reviewed by the counselor, with fields including family members, income, hardship level, and signature; the application form is filled out by the student and preliminarily reviewed by the department, with fields including grade ranking, award history, and signature; the loan receipt is issued by the bank or the financial aid center, with fields including loan amount, term, and receipt number. Materials are updated by semester or academic year; the determination form and application form are adjusted with the evaluation cycle, and the receipt flows with the loan batch. When the three types of materials enter the form input node, each plays its own information collection role: the determination form provides the basis for hardship level, the application form provides the basis for award/grant eligibility, and the receipt provides proof of loan disbursement. After submission, the field values are used by subsequent nodes or manual processing to generate the external entry point and authorization scope.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The external entry point and authorization scope are then 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 and signature are complete, and the date is consistent with the application form | Check field names, required markers, and signature fields one by one, and confirm that the field values can be referenced by subsequent nodes after submission |
| Scholarship/grant application form | Grade ranking and award history have no missing items, and the signature is complete | Check the required settings, and run a trial to confirm that subsequent nodes can retrieve the corresponding field values |
| Loan receipt | The receipt number, amount, and term are consistent with the application form records | Check the receipt fields and date, and confirm that the version is synchronized and there is no missing signature or receipt |
| Form input node | Submission is not allowed when required items are empty, and fields are passed successfully after submission | Check field names and required markers one by one in the node configuration, reference the fields with subsequent nodes, and run a trial |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the determination form and the application form. Cause: The two materials are filled out separately, without cross-checking and version synchronization.
- Symptom: The loan receipt is missing or the signature field is blank, and the material is returned. Cause: The receipt was not synchronized with the batch, and the signature and receipt completeness were not checked before submission.
- Symptom: After submission, subsequent nodes cannot retrieve the field values, and the conversation remains in the interaction state. Cause: Submission is possible even when required items are empty, or the field names are inconsistent with subsequent references.
How to verify the setup
Acceptance of this feature: fill in and submit once, check the field values retrieved by subsequent nodes, confirm that formInputResult and selectResult output correctly, and if necessary use formInput to run a trial again.
Business test: access once with a restricted identity and see whether the visible scope matches the setting
- Check field names and required markers one by one in the node configuration, and ensure that key material fields are marked as required
- Reference the field in subsequent nodes and run a trial to confirm that the field values can be retrieved after submission and that the conversation no longer remains in the interaction state