What this category's data looks like
Kindergarten play activity organization involves observation records, area plans, material placement lists, activity reflections, and next week's plans. Observation records are generated by activity session, area plans are updated weekly, material placement lists change with area adjustments, and reflection-to-next-week-plan is completed on weekends. These materials play different roles when entering the workflow: observation records and area plans serve as the basis for verification, material placement lists provide quantity benchmarks, activity goal achievement is used to compare observations with plans, and reflection-to-next-week-plan serves as the downstream recipient for discrepancy write-back. Field characteristics are concentrated in three categories: name, quantity, and date. The same object must remain consistent across two materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The discrepancy list is completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes the selection, the branch corresponding to the selected option continues execution.
| Object | Check | Verification action |
|---|---|---|
| Observation records correspond to area plans | The name and date of the same activity are consistent in the observation records and area plans | Compare the name and date fields one by one, reference variables in subsequent nodes, and run a trial once |
| Material placement quantity | The material quantities in the placement list and area plans are consistent | Check quantities item by item by area, and view the branch direction corresponding to nodeId in the run records |
| Activity goal achievement | The goals in the observation records are consistent with the area plan goals | Compare the goal fields, trigger a user selection node once, and view the interaction state |
| Reflection-to-next-week-plan | The reflection content has been transferred to next week's plan and the plan has been updated | Check the plan date and reflection date, and confirm the branch direction and state records |
Three common errors
- Phenomenon: The material placement quantity is less than required by the area plan. Cause: The material list was not updated synchronously with area adjustments, and only names were checked without comparing quantities during verification.
- Phenomenon: The goals in the observation records are inconsistent with the area plan goals. Cause: The plan was written first and not revised based on actual observations, and the two materials were maintained independently.
- Phenomenon: The reflection content was not transferred to next week's plan, and the plan remains the old version. Cause: Reflection and plan updates belong to different nodes, and the branch did not reach the write-back step.
How to verify the setup
This feature acceptance: Run trials option by option, check the branch directions and interaction states in the run records, confirm that options correspond one-to-one with branches, and that the selection result variable has been passed to subsequent nodes.
Business test: Use one real record to find fields inconsistent with the ledger, and verify the name, quantity, and date of that field in the observation records, area plans, and material lists.
- Check the options and branch connections one by one in the node, trigger once, and view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the branch direction and interaction state records are correct.