What this category's data looks like
Progress records and statistical verification for kindergarten operation behavior and quality self-assessment. The materials come from three texts: the self-assessment report, the issue list, and the rectification plan, updated weekly or monthly. Fields include name, quantity, date, signature, and receipt. The self-assessment report provides overall conclusions and indicator items; the issue list lists items to be rectified along with responsible persons and deadlines; the rectification plan gives steps and completion times. When these three materials enter this function, the self-assessment report serves as the primary record source, while the issue list and rectification plan serve as reference sources, respectively taking on the roles of item splitting and progress tracking. The progress table and statistical scope description must state the statistical scope, exception handling, and date baseline in the header, to facilitate weekly or monthly report aggregation.
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 "progress table and statistical scope description" is parsed from the response by subsequent nodes, or handled externally by an external system according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | Whether the name, quantity, date, and signature are consistent with the issue list | In the request preview, view the complete rendered address, and verify the name and quantity in the returned fields |
| Issue list | Whether the name, quantity, and date of the same record match across the two materials | Verify the request header names and value sources, and compare the returned fields with the list items |
| Rectification plan | Whether the version is synchronized, and whether signatures or receipts are missing | Use a sample request to compare the response, and check the date and signature fields |
| Request body | Whether the fields are consistent with the external interface agreement | In the variables panel, verify the source of each placeholder, and confirm the mapping of variables and responseData |
Three common errors
- Symptom: The name and quantity of the same record do not match between the self-assessment report and the issue list. Cause: The two entry sources are different, and no field mapping was performed.
- Symptom: The rectification plan version is not synchronized, and dates and signatures are missing. Cause: The external system did not return a receipt, and subsequent nodes did not verify it.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in according to the external system's requirements, and the placeholder variables were not parsed.
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 a sample, and confirm that the three placeholders Authorization, variables, and responseData can be resolved into actual values.
Business test: use one week of records to verify the totals, check whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match and that the scope is written in the header.
- In the variables panel, verify the source of each placeholder, and confirm that the variables in the request address, request headers, and request body can all be traced to global variables, system variables, or outputs from preceding nodes.
- Use a sample request to compare the response, check whether the returned fields are consistent with the external interface agreement, and then verify the totals against one week of records.