What this category's data looks like
This page addresses abnormal traceability and manual review for kindergarten safety protection and emergency drills. The materials come from hazard inspection records, drill plans and sign-in sheets, access control and school bus checklists, and responsible person signature pages. Hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus check items, and responsible person signatures are the four verification dimensions. When materials enter this function, the original records serve as the traceability source, the check items and signatures serve as the basis for determination, and the abnormal list and review conclusions serve as the output product. The update rhythm rolls with inspection, drill, access control, and school bus check batches. The field characteristics are hazard number, check item, deadline, headcount, and signature status.
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 "abnormal list and review conclusions" are parsed from the response by subsequent nodes, or handled externally according to the agreement. The HTTP module sends requests to the target address. Path parameters, request body, and request headers can all use variable placeholders. Variables come from global variables, system variables, or outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Hazard inspection records | Whether the hazard items and rectification deadlines form a closed loop, and whether the deadline field can correspond to a specific check item | In the request preview, view the complete rendered address and request body, and verify whether the source of variables can be traced to the original records |
| Drill plans and sign-in sheets | Whether the drill headcount and sign-in match the plan, and whether absentees have remarks | Use a sample request to compare the response, and verify whether the headcount and sign-in fields in responseData match the plan |
| Access control and school bus checklists | Whether access control and school bus check items are missing, and whether responsible person signatures are complete | Verify the request header names and value sources, and confirm that Authorization is passed in according to external system requirements |
| Abnormal list and review conclusions | Whether abnormalities are supported by original records, and whether reviewer signatures are complete | In the variable panel, verify the source of each placeholder, and confirm that conclusion fields can be traced to the source materials |
Three common errors
- Symptom: The hazard record shows rectification completed, but the deadline field is blank and there is no re-inspection signature. Cause: The hazard is not closed-loop, and rectification items and check items do not correspond one-to-one.
- Symptom: The drill sign-in headcount does not match the planned headcount, and the absentee list is missing. Cause: The drill record does not match the plan, and the sign-in sheet was not updated with the plan.
- Symptom: The access control or school bus checklist is missing a check item, and the responsible person signature column is empty. Cause: Check items are missing, and the signature page was not synchronized with the checklist.
How to verify the setup
This function's acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against a sample to confirm that the abnormal list and review conclusion fields in responseData are traceable.
Business test: create an abnormal record, see whether it can be traced to the source materials, and confirm that the reviewer signature corresponds to the original record.
- In the variable panel, verify the source of each placeholder, and confirm that
variablescan be traced to global variables, system variables, or outputs from preceding nodes. - Verify the request header names and value sources, confirm that
Authorizationis passed in according to external system requirements, and use a sample request to compare the returned fields.