What this category's data looks like
This page addresses the kindergarten game activity organization scenario. The material sources are class observation records, area activity plans, material placement lists, activity objective tables, and reflection logs, with an update cadence rolling by daily observation, weekly planning, and monthly reflection. When entering the question acceptance and missing-item follow-up feature, the correspondence between observation records and area plans serves as the basis for judgment, the material placement quantity serves as the object of missing-item identification, the achievement of activity objectives serves as the direction for follow-up questions, and the transfer of reflections into next week's plan serves as the item to be completed. In the process, each material respectively serves as the basis, the field to be completed, and the trigger point for follow-up questions, jointly supporting the formation of the acceptance record and the follow-up question items.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "acceptance record and follow-up question items" are then 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, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Correspondence between observation records and area plans | Determine whether the two are consistent; if inconsistent, ask about the points of difference | Check the options and branch connections one by one in the node, and check whether the variables reference points to the corresponding plan field |
| Material placement quantity | Determine whether it meets the quantity required for the activity; if insufficient, ask about the replenishment plan | Trigger one interaction, view the node status in the run record, and check the branch direction corresponding to nodeId |
| Achievement of activity objectives | Determine whether the objectives match the observations; if not, ask about the basis for adjustment | Reference the selection result variable in a subsequent node and run a trial once to confirm that the follow-up content has a material basis |
| Transfer of reflections into next week's plan | Determine whether the plan has been updated; if not, ask about the update node | Check whether the reflection field passed by variables enters the subsequent node, and check whether the branch connections cover the update path |
Three common errors
- Symptom: The material placement quantity is insufficient, yet the process directly enters the undertaking step. Cause: Missing-item identification does not cover the material list, and the follow-up branch is not triggered.
- Symptom: The activity objectives do not match the observation records, yet the process still proceeds according to the original plan. Cause: The objective achievement judgment is not compared with the observation fields, and the basis for follow-up questions is missing.
- Symptom: The reflection content is not transferred into next week's plan, and the plan is not updated. Cause: The reflection-to-plan branch is not connected, and the process stops after the interaction is completed.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction states in the run record, and confirm the correspondence among variables, nodeId, and the options.
Business test: submit a question that lacks key information and see whether it asks follow-up questions before answering.
- Check the options and branch connections one by one in the node, check whether the
variablesreference points to the corresponding material field, and confirm the branch direction and interaction state record. - Trigger one interaction, view the node status in the run record, check the branch corresponding to
nodeId, and confirm that the selection result variable has been passed to the subsequent node and run a trial once.