What this category's data looks like
This category's data covers hazard items and rectification deadlines, drill participant counts and sign-ins, access control and school bus inspection items, responsible person signatures, and other materials. It is usually summarized weekly or monthly by the kindergarten safety officer and, after review by superiors, forms the content of external services. When these materials enter the HTTP interface and external system functions, hazard items and rectification deadlines serve as request body fields, drill participant counts and sign-ins serve as path parameters or request body content, access control and school bus inspection items serve as the basis for the visible scope after request header authentication, and responsible person signatures serve as the confirmation identifier in returned fields. The material sources are the kindergarten's daily inspection records, drill plans and sign-in sheets, and access control and school bus inspection ledgers, and the update cadence changes with safety meetings and drill cycles. Field characteristics include hazard number, rectification deadline, drill participant count, sign-in status, inspection item result, signature status, etc. Authorized access control is required to define the external service scope, ensuring that parents or superiors only see content matching their identity.
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 externally available entry points and authorization scope are handled by subsequent nodes parsing the response, or by the external system continuing according to the agreement. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Request address and path parameters | The placeholder variables can be resolved into actual values, and the drill participant count and sign-in identifier in the path parameters are consistent with the external interface agreement | View the fully rendered address in the request preview, and check whether the path parameters correspond to the kindergarten and drill session |
| Request headers | The authentication information is passed in according to the external system's requirements, and the visible scope matches the visitor's identity | Check the request header names and value sources, and confirm that the token carried in Authorization corresponds to the parent or superior role |
| Request body | The fields are consistent with the external interface agreement, and fields such as hazard items and rectification deadlines, responsible person signatures, etc. are complete | Compare the response using a sample request, and check whether hazards that are not closed-loop or missing inspection items are rejected |
| Variable sources | Every placeholder can be traced to a specific origin, and variables and responseData are traceable | Check the source of each placeholder in the variables panel, and confirm it comes from a global variable, system variable, or the output of a preceding node |
Three common errors
- Symptom: Hazard items and rectification deadlines are missing from the response or not closed-loop. Cause: The request body fields were not passed in according to the agreement, or subsequent nodes did not parse the rectification status in
responseData. - Symptom: Drill records do not match the plan, and the sign-in count is inconsistent with the path parameters. Cause: The path parameter placeholder variable resolved to an old value, or the request header authentication scope was not limited to the corresponding drill session.
- Symptom: Access control and school bus inspection items are missing, and responsible person signatures are not returned. Cause: The request body fields are inconsistent with the external interface agreement, or an incorrect
variablesreference caused empty fields to be submitted.
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, confirming that Authorization, variables, and responseData are all parsed as expected.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the request preview, check the fully rendered address and path parameters, and confirm that the placeholder variables resolve into actual values.
- Check the request header names and value sources, and confirm that the authentication information is passed in according to the external system's requirements.