What this category's data looks like
District and county teaching research activity and classroom observation and evaluation materials mainly consist of teaching research activity notices, classroom observation records, and classroom evaluation minutes. They come from subject teaching researchers and the teaching research groups of each school, and the update cadence advances by activity batch. It is common for the same record to have mismatched names, quantities, and dates across two materials, for versions not to be synchronized, and for signatures or acknowledgments to be missing. When the materials enter workflow orchestration, the notice is responsible for triggering and scope definition, the classroom observation record is responsible for preserving classroom facts, and the classroom evaluation minutes are responsible for conclusions and improvement requirements; the fields, dates, and signatures of the three must correspond one-to-one in the version ledger and change records, old versions must be traceable, references must be synchronized, and the current version must be unique.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When this node is triggered, the conversation enters an interactive state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Whether the activity name, date, participating schools in the notice are consistent with the classroom observation records and classroom evaluation minutes, and whether signatures and acknowledgments are complete | Check the options and branch connections one by one in the node, trigger once, and then view the node status in the run records |
| Classroom observation record | Whether the name, quantity, and date of the same classroom match across the two materials, and whether the versions are synchronized | Reference the selection result variable in a subsequent node and run a trial once, checking the correspondence between variables and nodeId |
| Classroom evaluation minutes | Whether the conclusions and improvement requirements are uniquely updated with the current version, whether old versions are traceable, and whether references are synchronized | After changing one piece of content, rerun the branch, record the branch direction and interaction state, and check the tokens and array item count of the referenced text |
| Version ledger and change records | Whether the current version is unique, old versions are traceable, and references are synchronized, and whether missing signatures or acknowledgments are recorded | Check item by item according to the options and branch connections, confirm that the selection result variable has been passed to subsequent nodes, and run a trial once |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: The materials are maintained separately, versions are not synchronized, and references are not updated with the current version.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
- Symptom: The classroom evaluation minutes lack signatures or acknowledgments, and old versions cannot be traced. Cause: Change records were not retained according to the branch direction, and the same session repeatedly entered the interaction.
How to verify the setup
Acceptance for this feature: run a trial for each option one by one, check the branch direction and interaction state in the run records, and confirm the correspondence between nodeId and variables.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the options and branch connections one by one in the node, trigger once, and then view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, confirming that the tokens and array item count of the referenced text are recorded separately.