What this category's data looks like
School moral education and homeroom teacher work involves three types of materials: themed class meeting plans, student comprehensive quality records, and home visit records. Themed class meeting plans include activity objectives, procedures, dates, and the homeroom teacher's signature; student comprehensive quality records include evaluation dimensions, semester dates, and multi-party signatures; home visit records include home visit time, student performance, parent receipt, and teacher signature. The material sources are grade groups, homeroom teachers, and the moral education office, and the update rhythm runs in parallel by semester and by month: class meeting plans iterate by week, comprehensive quality records are archived by semester, and home visit records are supplemented in real time as events occur. When entering workflow orchestration, the three types of materials each play different roles: class meeting plans serve as reusable templates participating in branch judgment, comprehensive quality records serve as a data source for reference synchronization, and home visit records enter the version ledger as receipt vouchers. Field characteristics are concentrated in four categories: name, quantity, date, and signature. During version changes, it is necessary to ensure that the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "version ledger and change records" 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 status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Themed class meeting plan | Whether the name, date, and signature are consistent with the current version | Check the options and branch connections one by one in the node, and confirm that the plan reference points to the unique current version |
| Student comprehensive quality record | Whether the name, quantity, and date of the same record match across the two materials | Reference the selection result variable in a subsequent node and run a trial, then check whether the record reference is synchronized |
| Home visit record | Whether the receipt and signature are complete, and whether the old version is traceable | Trigger an interaction once, and view the node status and branch direction in the run records |
| User selection node | Each option corresponds to one branch, and the selection result has been passed to subsequent nodes | Check the options and branch connections in the node, and reference variables and nodeId in a subsequent node for a trial run |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match across the two materials. Cause: The version was not synchronized, the reference still points to old-version content, and it was not updated according to the principle that the current version is unique.
- Phenomenon: After selecting an option, it still follows the default branch. Cause: The options and branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
- Phenomenon: The home visit record lacks a signature or receipt. Cause: After the interaction is completed, the process stops, subsequent nodes do not continue execution according to the branch, and the receipt is not archived into the version ledger.
How to verify the setup
This feature acceptance: Run a trial for each option one by one, and check the branch direction and interaction status in the run records; reference variables and nodeId in subsequent nodes to confirm that the selection result has been passed.
Business test: Change one piece of content and see whether the version number and references are updated synchronously; check whether the name, quantity, date, and signature of the themed class meeting plan, student comprehensive quality record, and home visit record are consistent.
- Check the options and branch connections one by one in the node, trigger an interaction once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction is synchronized with the version ledger and change records.