What this category's data looks like
This category's data consists primarily of dropout risk ledgers, return-to-school persuasion records, and home visit records. Ledger fields include student name, student ID number, risk level, determination date, and signature; persuasion records include persuasion time, participants, result, and receipt; home visit records include home visit date, teacher signature, and parent signature. When these three types of materials enter the authorized access and external services function, the ledger provides the baseline for identity and visibility scope, while persuasion records and home visit records provide process evidence and serve as the basis for returns at the external entry point. The update cadence stays in sync with the progress of persuasion and home visits, and dates, quantities, and signatures must be consistent. During external services, parents or higher-level authorities see only their corresponding scope, and unauthorized access is not visible.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "externally accessible entry point and authorization scope" is completed by subsequent nodes parsing the response, or by an external system handling it as agreed.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Name, student ID number, risk level, determination date, and signature are consistent across the three types of materials | In the request preview, check the rendered address, and verify the variables source and ledger fields |
| Persuasion records | Persuasion time, participants, result, and receipt are complete, and match the ledger dates | Use a sample request to compare the return, and verify the persuasion fields in responseData |
| Home visit records | Home visit date, teacher signature, and parent signature are not missing, and match the ledger name | Verify the source of the request header Authorization value, then verify the returned home visit fields |
Three common errors
- Symptom: The name and date for the same student do not match between the ledger and the persuasion record. Cause: The two materials were entered separately and were not checked against the same record in sync.
- Symptom: The home visit record is missing the parent signature or receipt, but the external return still shows completed. Cause: The signature and receipt were not passed into the interface together with the record.
- Symptom: The request returns 401 or times out, and the external system receives empty fields. Cause: Authentication information or variable sources were not passed in as agreed.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be parsed into actual values. - Check the request header name and value source, and confirm that
Authorizationis passed in according to the external system's requirements.