What this category's data looks like
For school safety hazard inspections and campus incident reporting, materials fall into three categories: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled out weekly or monthly by duty personnel and include inspection items, locations, dates, and signatures; hazard rectification ledgers are registered entry by entry by hazard number and include rectification responsible persons, deadlines, acceptance results, and receipts; emergency incident reports are collected by incident number and include time, location, involved personnel, handling process, and signatures. The three types of materials share hazard numbers, dates, and signature fields, but names, quantities, and dates often do not match between two materials. When materials enter the HTTP interface, safety inspection checklists provide inspection items and dates, hazard rectification ledgers provide numbers and rectification status, and emergency incident reports provide incident numbers and handling fields, each serving as the source of request body or path parameters, to be processed by external systems as agreed.
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 version ledger and change records are parsed from the response by subsequent nodes, or the external system continues processing as agreed. The HTTP module sends requests to the target address, and variables can be used as placeholders in three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection items, locations, dates, and signature fields correspond item by item in the request body fields, and dates and signatures are not missing | Take a sample request, compare the request body fields with the original safety inspection checklist, and verify the sources of dates and signatures |
| Hazard rectification ledger | Hazard numbers, rectification deadlines, acceptance results, and receipts are traceable in the returned fields, and numbers and names are consistent between the two materials | Use a sample request to compare the response, and verify whether the hazard number matches the original hazard rectification ledger in name, quantity, and date |
| Emergency incident report | Incident number, time, involved personnel, and handling process are parseable in path parameters and request body | View the rendered complete address in the request preview, and verify the path parameter values against the original report |
| Request header | Authentication information is passed in as required by the external system, and the source of the Authorization value is traceable | Verify the request header names and value sources, and check the origin of each placeholder in the variables panel |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between two materials. Cause: The safety inspection checklist and hazard rectification ledger are maintained separately, without unified reference by hazard number.
- Symptom: After changing content in one place, the version number and references are not updated synchronously. Cause: The version ledger and change records are not maintained together with changes to request body fields, and the old version cannot be traced.
- Symptom: The emergency incident report lacks a signature or receipt. Cause: The report fields are not fully passed in the request body, and subsequent nodes cannot fill in the signature field when parsing the response.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample; at the same time, verify the sources and values of the three placeholders variables, responseData, and Authorization.
Business test: change content in one place, see whether the version number and references are updated synchronously, and verify that the current version is unique, the old version is traceable, and references are synchronized.
- In the variables panel, verify the source of each placeholder and confirm that variables in path parameters, request body, and request headers can all be resolved into actual values.
- Take a sample request to compare the response, and verify whether the fields, dates, and signature fields of the safety inspection checklist, hazard rectification ledger, and emergency incident report are consistent.