What this category's data looks like
This category's data includes notifications, child observation records, parent requests, and commitment responses. When these materials enter the HTTP interface and external systems, notifications enter the request body awaiting delivery confirmation, observation records and parent requests serve as variable sources for field population, and commitment responses must be processed by the external system as agreed. The materials are generated by class teachers and parents during communication, and the update rhythm changes with daily activities and parent feedback. In terms of field characteristics, notifications contain a title, body, and receiving scope; observation records contain time, scenario, and behavior description; parent requests contain category and expected response time. Together these materials form the externally available entry point and authorization scope; visitor identity and visible scope must match, and unauthorized access must not be visible.
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 point and authorization scope are completed by subsequent nodes parsing the response, or by the external system processing it as agreed. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, with variables coming from global variables, system variables, or upstream node outputs.
| Object | Check | Verification action |
|---|---|---|
| Request address and path parameters | Placeholder variables can resolve to actual values and match the visible scope of parents or superiors | View the fully rendered address in the request preview and verify the source of variables |
| Request headers | Authentication information is passed in as required by the external system; unauthorized identities must not be visible | Verify the Authorization name and value source, and confirm consistency with the visitor identity |
| Request body | Fields match the external interface agreement; commitment items and response time, child behavior description, parent request category, and notification delivery all fall into the corresponding fields | Compare the return using a sample request and check whether fields in responseData are complete |
| Variable sources | Every placeholder can be traced to a specific origin; observation records and parent requests are not confused | Verify the source of each placeholder in the variable panel and confirm there are no empty fields |
Three common errors
- Symptom: commitment not responded to. Cause: the request body does not include the response time field, so the external system cannot trigger the receipt as agreed.
- Symptom: wording does not match the observation record. Cause: the variable source points to the wrong node, and the notification body and observation record fields are mixed up.
- Symptom: feedback not categorized. Cause: the parent request category field is missing from the request body, so subsequent nodes cannot parse the response and assign it to the corresponding category.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that responseData and Authorization values are correct.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the request preview, verify the fully rendered address and path parameters, and confirm that each placeholder variable can be traced to a global variable, system variable, or upstream node output.
- Compare the return using a sample request, check the request header names and value sources, and confirm that the authentication information matches the external interface agreement.