What this category's data looks like
Compulsory education dropout prevention and school retention materials mainly consist of dropout risk ledgers, persuasion-to-return records, and home visit records. Their sources are daily school registration, township review, and county-level aggregation, and their update cadence rolls forward with the semester and the persuasion-to-return progress. The three types of materials have different field emphases: the dropout risk ledger contains student identifiers, risk levels, determination dates, and responsible persons; persuasion-to-return records contain persuasion time, method, result, and signatures of both parties; home visit records contain visit date, participants, parent opinions, and receipts. When materials enter the HTTP interface and external systems, the ledger assumes the role of master data, while persuasion-to-return records and home visit records are attached as process evidence. Version changes must ensure that the current version is unique, old versions are traceable, and references are synchronized.
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 version ledger and change records are parsed from the response by subsequent nodes, or handled by the external system according to the agreement and then completed. The request URL, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Student identifiers, risk levels, determination dates, and responsible persons are consistent across versions, and the current version is unique | Take one ledger record, check the path parameters and request body fields in the request preview, and compare the returned fields with the registration form |
| Persuasion-to-return record | Persuasion time, method, result, and signatures are complete, and the name, quantity, and date of the same record match across the two materials | Use a sample request to compare the response, check the persuasion-to-return fields in responseData against the paper record, and check whether the receipt is missing |
| Home visit record | Visit date, participants, parent opinions, and receipt are complete, old versions are traceable, and references are synchronized | Check the source of variables in the variable panel, and confirm that the home visit fields' references are synchronized after the ledger version is updated |
| Request header | Authentication information is passed in according to the external system's requirements, and the value source is traceable | Check the Authorization name and value source, and confirm that the request header does not use an empty value |
Three common errors
- Symptom: The date of the same persuasion-to-return record does not match between the ledger and the home visit material. Cause: The two are registered separately and are not merged under the same version number.
- Symptom: The ledger has been updated, but the persuasion-to-return record still references fields from the old version. Cause: The version was not synchronized, and the reference was not refreshed with the master data.
- Symptom: The home visit record lacks a parent signature or receipt. Cause: The material circulation step was not backfilled, and the interface returns empty fields.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; at the same time, check the source of variables and the fields in responseData.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the request preview, view the complete rendered URL and confirm that the placeholder variables are resolved into actual values.
- Use one sample request to compare the response, and check that the request body fields are consistent with the external interface agreement.