What this category's data looks like
For district and county teaching research activities and lesson observation and evaluation materials, there are commonly three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. The sources are teaching research departments and school submissions, and the update rhythm advances by activity batch, with each batch containing notices, records, minutes, and receipts. Field characteristics center on activity name, instructor, class, time, location, participants, observation dimensions, evaluation points, signatures, and receipts. When materials enter workflow orchestration, the notice assumes the role of initiation and notification, the lesson observation record assumes the role of process documentation, the lesson evaluation minutes assume the role of conclusions and improvements, and the handover record assumes the role of stage sign-off. The fields of the four types of materials must be consistent; the name, quantity, and date of the same record in the notice and minutes should be alignable; only when versions and dates are synchronized and signatures and receipts are complete can it enter the next stage for sign-off.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Draft materials and handover records that can be issued" 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 |
|---|---|---|
| Teaching research activity notice | Whether the activity name, instructor, class, time, location, participants, signatures, and receipts are complete, and whether the name, quantity, and date are consistent with the lesson observation record and lesson evaluation minutes | Check the options and branch connections one by one in the node, confirm that the notice fields align with subsequent materials, and when signatures or receipts are missing, block it via the branch |
| Lesson observation record | Whether the observation dimensions, process records, time, and instructor are consistent with the notice, whether versions and dates are synchronized, and whether signatures are missing | Reference the selection result variable in subsequent nodes and run a trial once, checking that the name, quantity, and date in the record are consistent with the notice and minutes |
| Lesson evaluation minutes | Whether the evaluation points, conclusions, improvement items, and participant signatures are complete, and whether the name, quantity, and date match the notice and lesson observation record | Trigger the user selection node once, view the node status in the run record, and confirm that the minutes fields are consistent with the handover record |
| Handover record | Whether the responsible person, handover time, version, and sign-off status are clear, and whether receipts are complete | Check the options and branch connections in the node, confirm that the handover record fields are complete, and then hand it to the next stage for sign-off |
Three common errors
- Symptom: The name, quantity, and date of the same record in the notice and lesson evaluation minutes do not match. Cause: During material drafting, checks were not performed according to unified fields, and during the handover stage, item-by-item comparison was not performed.
- Symptom: The versions of the lesson observation record and lesson evaluation minutes are not synchronized, and the dates are inconsistent. Cause: The version number was not updated after modification, and the old draft was used when the branch continued execution.
- Symptom: The notice or minutes lack signatures or receipts, and the responsible person in the handover record is blank. Cause: The sign-off stage did not validate fields, and missing items were not blocked.
How to verify the setup
Acceptance of this feature: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that options correspond to branches, that the selection result variable has been passed to subsequent nodes, and check variables, nodeId, and the node status in the run record.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and record
nodeId. - Reference the selection result variable in subsequent nodes and run a trial once, check whether
variableshas been passed in, and confirm that the handover record fields are complete.