What this category's data looks like
Student awards, grants, loans, and hardship determination involve three types of materials: 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 audited by the department; its fields include household population, income sources, hardship level, and signature fields. The application form includes student ID, award name, amount, and date. The loan receipt includes contract number, disbursement date, and receipt seal. Materials arrive in concentrated batches by semester and are submitted gradually during the week; the update cadence is weekly or monthly summary reporting. The three types of materials play different roles in progress records and statistical verification: the determination form establishes eligibility, the application form establishes disbursement, and the receipt establishes arrival of funds; fields and dates must be stated in the header to define the statistical basis.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "progress table and statistical basis description" is parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the next step. The request URL, request headers, and request body can all use variable placeholders; variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Family economic hardship determination form | Fields include household population, income sources, hardship level, and signature fields; dates must match the review record | Check each placeholder source in the variable panel, and confirm that signature and date fields are non-empty |
| Scholarship/grant application form | Name, quantity, and date must match the determination form; when versions are not synchronized, the latest signed version prevails | Compare the response with a sample request, and check the name and amount fields in responseData |
| Loan receipt | Receipt number, disbursement date, and seal must all be complete; if the receipt is missing, it is not counted in arrival statistics | Check the request header Authorization and request body fields, and confirm that the receipt number is returned |
| Statistical basis description | The header states the basis for record counts and statistical counts; exceptions are listed separately | View the fully rendered URL in the request preview, and check the variables values |
Three common errors
- Symptom: the same student's name or amount does not match between the determination form and the application form. Cause: the two materials are entered separately, without field-level comparison and version synchronization.
- Symptom: the loan receipt lacks a signature or the receipt number is empty, but it is still counted in arrival statistics. Cause: receipt fields are not set as required, and missing items do not go through exception marking.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: authentication information is not passed in as required by the external system, and placeholder variables are not parsed into actual values.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the fields in responseData match the external interface agreement.
Business test: verify totals using one week of records, check whether the basis and exceptions are clearly stated, and confirm that record counts and statistical counts match and that the basis is written in the header.
- Check the request header names and value sources, and confirm that
Authorizationis passed in as required by the external system. - Check each placeholder source in the variable panel, and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes.