What this category's data looks like
This page focuses on the district and county teaching research activity and classroom observation and evaluation scenario. Materials come from three categories: teaching research activity notices, classroom observation records, and classroom evaluation minutes. They are updated weekly or by activity batch. Fields include activity name, teaching teacher, class, subject, date, period, number of observers, evaluation key points, signature, and receipt. After the notice enters the workflow, it serves as the baseline source, the classroom observation record serves as the on-site collection item, and the classroom evaluation minutes serve as the conclusion item. The three form a comparison relationship around the same period. During workflow orchestration, the notice provides the expected attendance and actual attendance criteria, the classroom observation record provides the actual period and number of people, and the classroom evaluation minutes provide the evaluation conclusion and signature status. The three are merged by the same object and then enter material verification and discrepancy localization.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The discrepancy list is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state. 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 name, quantity, date, and signature criteria are consistent with the ledger | Compare field by field the activity name, expected attendance, activity date, and signature column in the notice, and check whether the activity identifier recorded in variables comes from the same source as the ledger |
| Classroom observation record | Whether the name, quantity, and date of the same period match the notice | Locate the corresponding branch by nodeId, check the period, actual attendance, and teaching teacher in the classroom observation record against the notice fields, and mark items with inconsistent dates |
| Classroom evaluation minutes | Whether the evaluation conclusion, signature, and receipt are synchronized with the classroom observation record | Check the evaluation date, number of participants, signature, and receipt status in the classroom evaluation minutes, and check whether the version is from the same batch as the classroom observation record |
| Discrepancy list | Whether inconsistent fields are located and submitted to the reviewer for confirmation | List inconsistent items for name, quantity, and date one by one, and write them back to the ledger after the reviewer confirms |
Three common errors
- Phenomenon: The date of the same period does not match between the notice and the classroom observation record. Cause: After the activity is rescheduled, only the notice is updated, while the classroom observation record is still filled in with the original date.
- Phenomenon: The classroom evaluation minutes lack a signature or receipt. Cause: After the evaluation ends, the signature is not added in time, and the receipt is not archived together with the minutes.
- Phenomenon: The name and quantity of the same record do not match between the two materials. Cause: The versions are not synchronized, and the notice and classroom observation record each retain different batches.
How to verify the setup
This function acceptance: Try running each option one by one, check the branch direction and interaction state in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: Use one real record to find fields inconsistent with the ledger, record the discrepancies in name, quantity, and date, and submit them to the reviewer for confirmation.
- In the user selection node, check the options and branch connections one by one, and run once to view the node status in the run record.
- Reference the selection result variable in subsequent nodes and run it to confirm that the branch direction is consistent with the interaction state record.