What this category's data looks like
The materials for exception tracing and manual review of kindergarten play activity organization come from observation records, area plans, material placement lists, activity objective tables, and reflection-to-next-week plan tables. Observation records are generated in real time by activity session, area plans are updated weekly, material placement quantities change with area adjustments, and activity objectives are set at the beginning of the semester and allow minor adjustments. When these materials enter the HTTP interface and external systems, their roles differ: observation records and area plans serve as comparison sources, material placement quantities serve as verification items, and activity objectives and reflection-to-next-week plans serve as support for review conclusions. Field characteristics include activity number, area name, material name and quantity, observation time, objective entries, and reviewer signature field. Exception tracing requires that each exception can be traced back to the source material, and review conclusions require original records and signatures before being handed to the person in charge for handling.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process. 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 from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | Whether the observed area activity corresponds to the area plan for the current week | Take one observation record, compare its activity number with the area name and planned week in the area plan, and verify the placeholder source in the variables panel |
| Material placement quantities | Whether the quantities in the list match the actual on-site placement | Use a sample request to compare the material names and quantities in the returned fields, and check whether the request body fields match the external interface agreement |
| Activity objective achievement | Whether the behavioral performance in the observation record matches the activity objective entries | View the fully rendered address in the request preview, verify the source of the objective entry fields, and compare the returned responseData |
| Reflection-to-next-week plan | Whether the reflection content has been transferred into the next week's plan and updated | Verify the request header names and value sources, confirm that Authorization is passed in as required by the external system, and check the plan update fields |
Three common errors
- Symptom: The material quantities in the exception list do not match the on-site quantities. Cause: The material placement quantities were not updated with area adjustments, and the list still uses old values, causing a mismatch with the source material during tracing.
- Symptom: The review conclusion shows the objective was achieved, but the observation record has no corresponding behavior. Cause: The activity objective and observation record are not associated by the same activity number, so the objective and observation do not match.
- Symptom: The next week's plan still uses the old area arrangement. Cause: The reflection content was not transferred into the next week's plan, the plan was not updated, and exception tracing cannot find the plan change record.
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; at the same time, verify the source of each placeholder in variables, and confirm that Authorization and responseData values are correct.
Business test: create an exception record, see whether it can be traced back to the source material, and confirm that the reviewer signature field and the person-in-charge handling destination are complete.
- In the variables panel, verify the source of each placeholder and confirm that the variables in path parameters, request body, and request headers can all be resolved into actual values.
- Use a sample request to compare the returned fields with the external interface agreement, and check whether the request header names and value sources meet the external system requirements.