What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials include three categories: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices contain the activity name, time, location, scope of participation, and receipt requirements; lesson observation records contain the instructor, class, topic, observation dimensions, and signature; lesson evaluation minutes contain review points, improvement suggestions, signatures, and version. Materials are updated by activity batch, and the same activity often has multiple notices, multiple records, and multiple minutes in parallel. When entering the workflow, notices serve as the entry point and define the authorization scope, while lesson observation records and lesson evaluation minutes serve to verify the visible scope. The three are characterized by fields such as name, quantity, date, signature, and receipt, for subsequent nodes to continue execution along branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution along branches.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Whether the name, quantity, date, and receipt are consistent with the authorization scope | Check options and branch connections one by one in the node, and record the visible scope corresponding to the notice |
| Lesson observation record | Whether the instructor, class, topic, date, and signature match another material | Reference the selection result variable in a subsequent node and run a trial once to check the visible scope of the record |
| Lesson evaluation minutes | Whether the review points, improvement suggestions, signatures, and version are synchronized | Trigger a user selection node once and check the node status and branch direction in the run record |
| User selection node | Whether each option corresponds to one branch and is passed to subsequent nodes | Check the options and branch connections, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same lesson observation record do not match across two materials. Cause: Notices and records are maintained separately, and fields are not aligned by the same activity batch.
- Symptom: The version of the lesson evaluation minutes is not synchronized, and the external entry point still displays the old version. Cause: After the version update, the branch was not re-run, and the visible scope continued to use the previous settings.
- Symptom: The lesson observation record or lesson evaluation minutes lack a signature or receipt. Cause: When the materials entered the workflow, signatures and receipts were not used as conditions for determining the visible scope.
How to verify the setup
Acceptance for this feature: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and verify that the selection result variable referenced by subsequent nodes is consistent with the variables and nodeId records.
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 confirm that each option corresponds to one branch.
- Trigger a user selection node once and check the node status and branch direction in the run record.