What this category's data looks like
This page addresses the kindergarten home-school co-education communication scenario, and the materials come from daily class records, parent request registrations, notification delivery receipts, and commitment item ledgers. When these materials enter the exception tracing and manual review function, each plays a different role: daily records provide the original basis for descriptions of children's performance, request registrations are used to classify parent requests, delivery receipts confirm notification delivery status, and the commitment ledger locks down commitment items and response times. The materials are updated daily or weekly, and the fields include timestamps, class identifiers, item types, description text, response status, and reviewer signature fields. Exception tracing requires that every exception can be traced back to the source material, and review conclusions must be supported by original records and signed by the reviewer, and finally handed over to the person in charge for handling.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The HTTP node sends a request to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. The 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 correspond to the commitment item and response time fields | View the fully rendered address in the request preview and check the source of each placeholder in variables |
| Request headers | Authentication information is passed in according to the external system's requirements, and the source of the Authorization value is traceable | Check the request header names and value sources, and confirm they are consistent with the external interface agreement |
| Request body | The fields are consistent with the external interface agreement and cover the description of children's performance and the classification of parent requests | Use a sample request to compare the response and check whether responseData contains the expected fields |
| Variable sources | Every placeholder can be traced to a specific origin, and the notification delivery status field is traceable | Check the source of each placeholder in the variables panel and confirm there are no empty field references |
Three common errors
- Symptom: A commitment has not been responded to but does not enter the exception list. Cause: The commitment item and response time are not passed in as request body fields, so the external system cannot compare them.
- Symptom: A statement that does not match the observation record still passes review. Cause: The request body only passes the description text and does not carry the original record identifier, so subsequent nodes cannot trace it back.
- Symptom: Feedback is not categorized, resulting in a missing review conclusion. Cause: The parent request classification field is not agreed upon in the request headers or request body, and the returned fields have no classification value.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that Authorization, variables, and responseData all appear as agreed.
Business test: create an exception record and see whether it can be traced back to the source material
- In the request preview, check whether the fully rendered address and path parameter placeholders are resolved into actual values
- In the variables panel, check the source of each placeholder and confirm that the request header authentication information and request body field sources are traceable