What this category's data looks like
In the context of a technology center, the materials for kindergarten game activity organization mainly consist of observation records, area plans, material placement lists, activity objectives, and reflections converted into next week's plans. Observation records come from teachers' on-site records, area plans come from grade-level weekly plans, material placement lists come from actual classroom arrangement, activity objectives come from curriculum plans, and reflections converted into next week's plans come from teaching research meetings. The update rhythm is daily observations, weekly area plans, material inventory after each activity, and weekly teaching research reflections. Field characteristics include observation subject, area name, material name and quantity, objective items, reflection conclusions, and next week's actions. When these materials enter the workflow orchestration function, observation records and area plans serve as the basis for judging the achievement of activity objectives and plan updates, material placement lists serve as the basis for checking material quantities, and reflections converted into next week's plans serve as input for branch direction.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. "Externally available entry points and authorization scope" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. 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 | Observation records correspond to area plans, and objectives are consistent with observations | Check options and branch connections one by one in the node, and reference variables to see whether observation records and area plans correspond |
| Material placement list | The quantity of materials placed meets what is required by the activity objectives | Trigger once, check the node status in the run records, and verify the quantity of materials placed against the achievement of activity objectives |
| Reflections converted into next week's plans | Reflection conclusions have been converted into next week's plans and the plans have been updated | Reference the selection result variables in subsequent nodes and run a trial once, and check the branch direction when the plans have not been updated |
| Options and branches | Each option corresponds to one branch and the branch direction is consistent with the selection | Check options and branch connections one by one in the node, and record nodeId and interaction status |
Three common errors
- Phenomenon: insufficient materials still follow the pass branch. Cause: the material placement list did not check quantities against the area plan, and the options and branch connections did not cover the insufficient materials case.
- Phenomenon: objectives inconsistent with observations still enter the external entry point. Cause: observation records and area plans do not correspond, and branch judgment did not reference objective items and observation conclusions.
- Phenomenon: plans not updated yet shown as open. Cause: reflections converted into next week's plans were not written back to the area plan, and after interaction is completed the process stops or repeatedly enters interaction.
How to verify the setup
This function acceptance: run trials option by option, check the branch direction and interaction status in the run records, and verify whether the variables and nodeId records are consistent.
Business test: access once with a restricted identity and see whether the visible scope matches the settings.
- Check options and branch connections one by one in the node, and record interaction status and branch direction.
- Reference the selection result variables in subsequent nodes and run a trial, and verify the visible scope under the three cases: insufficient materials, objectives inconsistent with observations, and plans not updated.