What this category's data looks like
Kindergarten operation behavior and quality self-assessment materials usually include three types: self-assessment reports, issue lists, and rectification plans. Self-assessment reports are produced by semester or academic year, recording items such as operation direction, care and education process, and safety and hygiene; issue lists itemize the issues found, the responsible persons, and rectification deadlines; rectification plans give measures, completion dates, and signature fields corresponding to the issues. When these materials enter the authorized access and external services function, the self-assessment report serves as the main record carrying the overall conclusion, and the issue list and rectification plan serve as subsidiary records attached under the same kindergarten entity. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures: the name of the same issue in the list and the plan must be consistent, the rectification quantity must match the statistics in the report, the plan completion date must be later than the issue discovery date, and signatures or receipts must be complete. The update rhythm is mostly once per semester, and temporary versions are added when special inspections occur.
Configuration and implementation checks
This part is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The externally available entry point and authorization scope are parsed from the response by subsequent nodes, or the external system handles them as agreed and then completes the rest. The HTTP node is only responsible for sending requests as agreed and retrieving results; it does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | The number of issues in the report corresponds item by item to the issue list, and dates and signature fields are complete | In the request preview, view the complete rendered address, and check whether the report fields in responseData match the number of list entries |
| Issue list | The list entry names, responsible persons, and rectification deadlines match in the two materials | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
| Rectification plan | The plan completion date is later than the issue discovery date, and receipts or signatures are not missing | Use one sample request to compare the return, and check whether each placeholder in variables can be traced to a specific source |
| Request body fields | The fields are consistent with the external interface agreement, and names, quantities, and dates are all non-empty | Check the source of each placeholder in the variables panel, and confirm that the request body fields match the sample |
Three common errors
- Symptom: The name or quantity of the same issue does not match between the list and the plan. Cause: The two materials are maintained separately, without field-level comparison.
- Symptom: The self-assessment report has been updated, but the issue list is still the old version. Cause: The versions are not synchronized, and the external service reads expired records.
- Symptom: The rectification plan lacks a signature or receipt, but the external entry point still returns success. Cause: The authorization scope does not verify the signature field, making it visible beyond authority.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that all three placeholders Authorization, variables, and responseData can be parsed.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting.
- In the request preview, check the complete rendered address and path parameters, and confirm that the placeholder variables are parsed into actual values.
- In the variables panel, check the source of each placeholder, and confirm that the request header and request body fields are consistent with the external interface agreement.