What this category's data looks like
This page addresses progress records and statistical reconciliation for school safety hazard inspections and campus incident reporting, involving three types of materials: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled in weekly or per inspection, with fields including inspection date, inspector, hazard description, and rectification deadline; hazard rectification ledgers are registered item by item by hazard number, with fields including rectification responsible person, rectification measures, completion date, and re-inspection signature; emergency incident reports are documented separately by incident occurrence time, with fields including incident course, handling measures, reporter, and receipt acknowledgment. The three types of materials are produced by different positions at different points in time, and when they enter the progress table they respectively assume the roles of inspection coverage, rectification progress, and incident closure. The update rhythm is daily filing, weekly summary, and monthly reconciliation; material names, quantities, dates, and signatures must remain consistent between the progress table and the statistical scope description.
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 by an external system according to the agreement to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection date, inspector, and hazard description are consistent between the progress table and the statistical scope description, and the signature column is not missing | Bring the checklist fields into the request body, use variables as placeholders, and compare the returned fields with the header scope |
| Hazard rectification ledger | Hazard number, rectification completion date, and re-inspection signature match between the two materials | Pass Authorization in the request headers as required by the external system, and check the ledger number against the number of returned records |
| Emergency incident report | Incident name, occurrence date, and receipt acknowledgment are consistent across the three materials, and versions are synchronized | Use variables in the path parameters to bring in the incident number, and check the returned responseData against the report receipt |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between the safety inspection checklist and the rectification ledger. Cause: The two are entered separately, without using the hazard number as a common key for reconciliation.
- Symptom: The version of the emergency incident report is not synchronized, and the progress table references an old draft. Cause: After the report was revised, it was not written back to the statistical scope description, and material versions were kept separately.
- Symptom: The safety inspection checklist lacks the inspector's signature, and the rectification ledger lacks the re-inspection receipt. Cause: Signatures and receipts are added at the end of the process, and are not synchronized into the progress table along with the records.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the results against one sample; in the variables panel, check the value sources of variables and responseData.
Business test: use one week of records to reconcile the totals, see whether the scope and exceptions are clearly stated, and confirm that the record counts and statistical counts of the three types of materials—safety inspection checklists, hazard rectification ledgers, and emergency incident reports—are consistent.
- In the request preview, check the rendered complete address, request header names, and request body fields, and confirm that each placeholder variable can be traced to a global variable, system variable, or upstream node output.
- Use one sample request to compare the returned fields with the progress table headers, record exceptional cases, and submit them with the weekly or monthly report.