What this category's data looks like
This page focuses on question acceptance and missing-item follow-up for kindergarten safety protection and emergency drills. The materials come from hazard ledgers, drill plans and sign-in sheets, access control and school bus inspection records, and responsible-person signature pages. The hazard ledger provides hazard items and rectification deadlines, the drill materials provide headcounts and sign-ins, the access control and school bus records provide inspection items, and the signature pages confirm responsibility ownership. Materials are updated weekly, closed-loop status is backfilled after hazard rectification, sign-ins and photos are added after drills, and inspection records are archived by shift. Fields include hazard number, rectification deadline, drill date, expected and actual attendance, inspection item name, and signature status. When materials enter this feature, hazard items are used to determine whether the loop is closed, drill records are used to compare the plan with the actual situation, inspection items are used to identify omissions, and signature pages are used to confirm the responsible person.
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 acceptance record and the completed follow-up questions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process. Variables can be used as placeholders in three places: the request URL, path parameters, request headers, and request body. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Hazard ledger | Whether hazard items and rectification deadlines appear in pairs, and whether unclosed items are marked | Check the rendered URL and request body in the request preview, confirm that the hazard number and deadline fields are non-empty, and compare the returned closed-loop marker |
| Drill sign-in sheet | Whether the drill headcount and sign-ins are consistent, and whether the records match the plan | Use a sample request to compare the response, verify the expected and actual attendance and the sign-in list, and check whether the plan name and drill date correspond |
| Access control and school bus inspection records | Whether inspection items are listed one by one and whether any are missing | Check the request body fields against the external interface agreement, compare the inspection item names and results one by one, and confirm there are no empty fields |
| Responsible-person signature page | Whether the signature status is traceable and the responsible person is clear | Check the source of each placeholder in the variables panel, and confirm that the signature status field value comes from the output of a preceding node |
Three common errors
- Symptom: a hazard item has been registered but still shows as unclosed after the rectification deadline. Cause: the action to backfill the closed-loop status was not triggered, and the material remains in its initial state.
- Symptom: the drill record headcount does not match the sign-in sheet, and the plan name and drill date are misaligned. Cause: sign-in materials are submitted in batches by class and are not bound to the plan number.
- Symptom: access control or school bus inspection items are missing, and empty values appear in the returned fields. Cause: the request body fields are inconsistent with the external interface agreement, and the placeholder variables were not parsed into actual values.
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 a sample; confirm that Authorization is passed in correctly, and that variables and responseData are traceable in the response.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- Check the complete rendered URL and path parameters in the request preview, and confirm that the placeholder variables are parsed into actual values.
- Check the source of each placeholder in the variables panel, and confirm that
Authorization,variables,responseDataare consistent with the external interface agreement.