What this category's data looks like
This page addresses the scenario of course scheduling and class-hour consumption in training institutions. The materials include three types: class schedules, class-hour consumption records, and schedule-change requests. The class schedule is generated by the academic affairs staff when scheduling classes, with fields including course name, class, teacher, classroom, class date and time slot, and signature column; the class-hour consumption record is submitted by the instructor after class, with fields including session, student roster, attendance status, number of class hours, teacher signature, and receipt; the schedule-change request is initiated by the teacher or academic affairs staff, with fields including original session, target date, reason for adjustment, and approval signature. The three types of materials are updated weekly, and schedule-change requests are updated immediately upon approval. When entering the workflow, the class schedule serves as the baseline schedule, the class-hour consumption record serves as the proof of class-hour consumption, and the schedule-change request serves as the basis for changes; together, the three support exception tracing and manual review.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution along the branches. 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 |
|---|---|---|
| Class schedule | Whether the course name, class, teacher, classroom, class date and time slot, and signature column correspond item by item with the class-hour consumption record | Take the same session, compare the name, date, and teacher signature in the class schedule and the class-hour consumption record, and record the discrepancies |
| Class-hour consumption record | Whether the session, student roster, attendance status, number of class hours, teacher signature, and receipt are complete and consistent with the schedule-change request | Pull the class-hour consumption record and schedule-change request by session, check the date, number of class hours, and signature receipt, and mark the missing items |
| Schedule-change request | Whether the original session, target date, reason for adjustment, and approval signature are synchronized with the class schedule changes | Compare the schedule-change request with the class schedule version, confirm the target date and approval signature, and check whether the versions are synchronized |
| User selection node | Whether each option corresponds to one branch, and whether the selection result variable is passed to subsequent nodes | Check the options and branch connections one by one in the node, reference variables in subsequent nodes, and run a trial once |
Three common errors
- Symptom: The course name and date for the same session do not match between the class schedule and the class-hour consumption record. Cause: The two materials are filled in separately by different roles, lacking a unified session number and cross-checking.
- Symptom: The schedule-change request has been approved, but the class schedule still shows the original date, and the class-hour consumption record is submitted under the new session. Cause: The versions are not synchronized, the change was not written back to the class schedule, and subsequent nodes continue execution along the old branch.
- Symptom: The class-hour consumption record lacks the teacher signature or receipt, yet the review conclusion is still advanced. Cause: The manual review did not check the signature column item by item, and the interaction state record was not bound to the material list.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId in subsequent nodes to run once more.
Business test: Create an exception record, see whether the source material can be traced, check the fields, dates, and signatures of the class schedule, class-hour consumption record, and schedule-change request, and confirm that the exception is supported by the original records and signed by the reviewer.
- Check the options and branch connections one by one in the user selection node, trigger it once, then view the node status in the run records to confirm that the interaction state is recorded and the selection result variable has been passed to subsequent nodes.
- Take an exception record, trace back the class schedule, class-hour consumption record, and schedule-change request by session, check the names, quantities, dates, and signatures, write the discrepancies into the exception list, and hand it over to the person in charge for handling.