What this category's data looks like
The core materials for the course selection, scheduling, and classroom resource allocation category include three types: the course offering plan, the scheduling table, and the course selection rules. The course offering plan is published by the academic affairs department per semester, with fields including course name, course code, credits, instructor, and planned offering time; the scheduling table is generated by the scheduling system per week, with fields including course, classroom, period, week, and class; the course selection rules are maintained by the course selection system, with fields including selection batch, capacity, priority, and withdrawal/change rules. The three types of materials update at different rhythms: the course offering plan is finalized before the semester, the scheduling table is fine-tuned weekly, and the course selection rules are revised on a rolling basis by batch. When entering the exception tracing and manual review workflow, the course offering plan serves as the source basis, the scheduling table serves as the execution record, and the course selection rules serve as the constraint conditions; together, the three support the generation of the exception list and review conclusions.
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 according to the branch. When the 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 |
|---|---|---|
| Course offering plan | Whether the course name, course code, credits, instructor, planned offering time, and signature field are complete, and whether they match the scheduling table field by field | Retrieve the original course offering plan, check the course name, code, instructor, date, and signature field, and confirm consistency with the same record in the scheduling table |
| Scheduling table | Whether the course, classroom, period, week, and class correspond item by item with the course offering plan and course selection rules, and whether the version number is in sync | Compare the course, classroom, and week fields of the scheduling table and the course offering plan, and check the version marker and signature receipt |
| Course selection rules | Whether the selection batch, capacity, priority, and withdrawal/change rules are consistent with the scheduling table capacity and course offering plan credits, and whether signatures are missing | Check the course selection rules against the scheduling table capacity and course offering plan credits, and check the rule version and approval signature |
| User selection node | Whether each option corresponds to one branch, whether the interaction state is recorded, and whether the selection result variable is passed to subsequent nodes | In the node, check the options and branch connections one by one, trigger it once to view the node state in the run record, and reference the variable in a subsequent node and do a trial run |
Three common errors
- Symptom: The name, credits, or date of the same course do not match between the course offering plan and the scheduling table. Cause: The two materials are maintained by different steps, and updates were not synchronized after revision.
- Symptom: The scheduling table version and the course selection rules version are inconsistent, causing conflicts between capacity and batch. Cause: The versions were not synchronized, and the old version of the material is still being referenced.
- Symptom: The exception record lacks the reviewer's signature or receipt, making it impossible to trace back to the source material. Cause: The signature step was omitted or the receipt was not archived.
How to verify the setup
Feature acceptance: Do a trial run for each option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and check whether variables are passed and whether the nodeId state is recorded.
Business test: Create an exception record, see whether it can be traced back to the source material, and confirm that the exception is supported by the original record and the reviewer's signature.
- In the user selection node, check the options and branch connections one by one, trigger it once to view the node state in the run record, and confirm that the interaction state is recorded.
- Reference the selection result variable in a subsequent node and do a trial run once, confirm that
variableshave been passed and thenodeIdstate is correct, and that the exception list and review conclusions are completed by subsequent nodes continuing execution according to the branch.