What this category's data looks like
This page addresses the work of exception tracing and manual review for kindergarten play activity organization. The materials come from daily observation records, area activity plans, material placement lists, activity objectives, and reflections transferred to next week's plans, etc. Observation records and area plans must correspond one-to-one, the quantity of materials placed must match the plan, the achievement of activity objectives must be supported by observation evidence, and reflection content should be transferred to next week's plan. The update rhythm is entry after daily activities and summary review weekly. When entering workflow orchestration, observation records serve as the source material for exceptions, area plans serve as the comparison baseline, material lists serve as the basis for quantity verification, and objectives and reflections serve as conclusion support. Each material assumes different roles in the nodes, jointly supporting the generation of the exception list and review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "Exception List and Review Conclusions" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | Whether the two correspond item by item, and whether observation records can point to the original plan entry when the plan is not updated | Check options and branch connections one by one in the node, reference nodeId to locate the record source, and run a trial to see the branch direction |
| Material placement quantity | Whether the actual placed quantity is consistent with the quantity listed in the area plan, and whether insufficient materials can be marked | Reference the selection result variables in subsequent nodes and run a trial, checking whether quantity discrepancies enter the exception branch |
| Activity objective achievement | Whether the objectives match the observation records, and whether items pending review can be generated when they do not match | Trigger an interactive state once, and check the node status and branch direction in the run record |
| Reflections transferred to next week's plan | Whether reflection content is transferred to next week's plan, and whether the original record can be traced when it is not updated | Check options and branch connections one by one in the node, confirming that an unupdated plan goes to the exception branch |
Three common errors
- Phenomenon: The material placement quantity does not match the area plan, yet the observation records show the activity as normal. Cause: Insufficient materials were not marked as an exception, and there was no quantity comparison basis during review.
- Phenomenon: The activity objectives are inconsistent with the observation record content, yet the conclusion is still processed as objective achievement. Cause: No correspondence verification was done between objectives and observations, and the exception branch was not triggered.
- Phenomenon: Reflection content was not transferred to next week's plan, and the plan still uses the old version. Cause: The plan not being updated was not identified, and the source material cannot be found during tracing.
How to verify the setup
This feature acceptance: Run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variables has been passed to subsequent nodes, and that nodeId can locate it.
Business test: Create an exception record and see whether the source material can be traced.
- Check options and branch connections one by one in the node, trigger an interactive state once, and check the node status in the run record
- Reference the selection result
variablesin subsequent nodes and run a trial once, confirming that the branch direction is consistent with the interaction state record