What this category's data looks like
This category's data is concentrated in three types of materials: class schedules, attendance deduction records, and schedule change requests. Class schedules are generated by academic affairs staff based on class and teacher scheduling; attendance deduction records are filled in by the teaching instructor after class according to actual attendance and class hours; schedule change requests are initiated by the instructor or academic affairs staff before the change. Material sources are scattered across scheduling tables, roll-call sheets, and schedule change forms. The update rhythm is: scheduling is set first, schedule changes follow changes, and attendance deduction is recorded as classes are held. It often occurs that the course name, number of class hours, and teaching date for the same class are inconsistent across two materials. When entering workflow orchestration, the class schedule serves as the baseline material, while attendance deduction records and schedule change requests serve as materials to be verified. Together, the three determine whether the issuable draft and handover record can have complete fields, clear responsible parties, and consistent versions and dates, and be handed to the next stage for sign-off.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The issuable material draft and handover record 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 state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Category verification dimensions: whether fields, dates, and signatures are complete; whether the course name, number of class hours, and teaching date are consistent across the three materials | Check the options and branch connections one by one in the node, confirm that the class schedule fields align item by item with the schedule change request and attendance deduction record, and route to the interception branch when items are missing or dates conflict |
| Attendance deduction record | Category verification dimensions: whether fields, dates, and signatures are complete; whether a receipt and responsible party signature are attached | Trigger the node once, view the node status in the run record, verify that the name, quantity, and date of the attendance deduction record are consistent with the class schedule, and route to the return branch when signatures or receipts are missing |
| Schedule change request | Category verification dimensions: whether fields, dates, and signatures are complete; whether the version and date are synchronized | Reference the selection result variable in a subsequent node and run a test once, verify that the version number of the schedule change request is synchronized with the class schedule and attendance deduction record, and route to the re-review branch when the version is not synchronized |
Three common errors
- Symptom: The course name, number of class hours, and teaching date for the same class do not match between the class schedule and the attendance deduction record. Cause: The two materials are filled in by different stages, and fields were not compared item by item before handover.
- Symptom: The schedule change request has been updated, but the class schedule and attendance deduction record remain on the old version, with inconsistent version and date. Cause: The version was not synchronized, and the version number and effective date were not checked during handover.
- Symptom: The attendance deduction record lacks the teaching instructor's signature or the next stage's receipt, so the handover record cannot be closed. Cause: Signatures and receipts were not included in the verification items, and missing items were not intercepted.
How to verify the setup
Feature acceptance: run a test for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and check that variables, nodeId, and branch connections are consistent.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are intercepted.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and that no default branch is mistakenly taken.
- Reference the selection result variable in a subsequent node and run a test once, check that
variablesandnodeIdare referenced correctly, and confirm that the process continues downward after the interaction is completed.