What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials include three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices usually contain the activity theme, time and location, participation scope, agenda, and a reply slip, with an update cadence of being issued one week before the activity and confirmed one day before the activity; lesson observation records contain the instructor, class, topic, observation dimensions, timeline, and signature field, and are filled in during class and summarized on the same day; lesson evaluation minutes contain speakers, viewpoints, improvement suggestions, conclusions, and signature fields, and are finalized within two days after the activity. When the materials enter workflow orchestration, the notice serves as the initiation credential and branching basis, the lesson observation record serves as process evidence, and the lesson evaluation minutes serve as the source of conclusions and replies; together, the three support a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "handover-ready deployment state and operation records" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The activity name, date, and participation scope in the notice must be aligned item by item with the lesson observation record and lesson evaluation minutes, and the reply slip and signature field must not be left blank | Check the notice and the two materials item by item against the handover checklist, verify whether the names, quantities, dates, and signatures and replies are consistent, and check in the run records whether the variables references point to the same activity |
| Lesson observation record | The instructor, class, topic, observation dimensions, and timeline must correspond to the notice agenda and the conclusions of the lesson evaluation minutes, and the signature field must be complete | Reference the selection result variable corresponding to nodeId in a subsequent node and run a trial once, and verify whether the lesson observation record fields have the same names, quantities, and dates as the notice and minutes |
| Lesson evaluation minutes | The speakers, viewpoints, improvement suggestions, conclusions, and signature field must be consistent with the notice and lesson observation record, and the reply must be traceable | Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and verify whether the minutes date and signatures are complete |
| Deployment state and operation records | The version, connection, and task records must be consistent, and the branch directions and interaction state records must be traceable | Check once item by item against the handover checklist, see which record is missing, and check variables, nodeId, and branch directions in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same activity do not match across the two materials. Cause: The notice and lesson observation record are filled in separately, lacking unified field verification and signature replies.
- Symptom: The version is not synchronized, and the old notice is still referenced. Cause: After the materials were updated, they were not synchronized to the workflow branch, and the run records still point to the old version.
- Symptom: The lesson evaluation minutes lack a signature or reply. Cause: After the activity, no item-by-item check was performed against the handover checklist, and the signature field and reply slip were not completed before moving to the next shift.
How to verify the setup
This feature's acceptance: run trials option by option, check the branch directions and interaction states in the run records, and confirm that each option corresponds to the correct branch connection and that the selection result variable has been passed to subsequent nodes.
Business test: check once item by item against the handover checklist, see which record is missing, and verify whether the version, connection, and task records are consistent.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference
variablesandnodeIdin a subsequent node and run a trial once, and verify the branch directions and interaction state records.