What this category's data looks like
This category's materials for course selection, scheduling, and classroom resource allocation include three types: course offering plans, scheduling tables, and course selection rules. Course offering plans record course name, course code, credits, offering semester, instructor, and signature; scheduling tables record course name, class, classroom number, class date, period, and signature; course selection rules record course name, selection capacity, selection time, prerequisite conditions, and receipt. The material sources are academic affairs system exports and department submissions, and the update cadence rolls forward by semester and schedule adjustment cycle. When the three types of materials enter workflow orchestration, course offering plans take the role of the baseline version, scheduling tables take the role of resource occupancy and time implementation, and course selection rules take the role of capacity and admission constraints. Field characteristics are concentrated in four types: name, quantity, date, and signature, and version numbers and reference relationships need to be maintained in sync.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction state records. 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. The "version ledger and change records" are completed next by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | The course name, course code, and credits fields in the course offering plan, scheduling table, and course selection rules must be aligned item by item; the name and quantity of the same record in two materials must not conflict | Check the options and branch connections one by one in the node, confirm that the walkthrough branch corresponds to the course offering plan version, and reference variables in a subsequent node to run a trial once |
| Scheduling table | The course name, class, class date, and period in the scheduling table and course offering plan must be consistent, the classroom number must not be occupied repeatedly, and signatures and receipts must be complete | Trigger an interaction once, view the node status in the run record, and check whether the branch corresponding to nodeId points to the scheduling table version |
| Course selection rules | The course name, selection capacity, and selection time in the course selection rules must be synchronized with the course offering plan and scheduling table; if the version is not synchronized or the dates do not match, it is judged inconsistent | Reference variables in a subsequent node and run a trial once to confirm that the selection result variable has been passed to the course selection rules version branch |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized; after changing one piece of content, the version number and references must be updated in sync | Change one piece of content, see whether the version number and references are updated in sync, and check the branch direction and interaction state in the run record |
Three common errors
- Symptom: the name, quantity, and date of the same course do not match in two materials. Cause: the course offering plan and scheduling table are maintained separately, without field alignment and signature/receipt verification.
- Symptom: the version is not synchronized, and the old version is still referenced. Cause: after a change, the version ledger was not updated, subsequent nodes still follow the default branch, and references were not updated with the version number.
- Symptom: the process stops after the interaction is completed, or the same session repeatedly enters the interaction. Cause: the selection result variable was not passed to subsequent nodes, and the branch connections and options were not checked one by one.
How to verify the setup
Feature acceptance: run trials option by option, check the branch direction and interaction state in the run record, confirm that the branch corresponding to nodeId is consistent with the option, and that variables has been passed to subsequent nodes.
Business testing: change one piece of content, see whether the version number and references are updated in sync, and check whether the name, quantity, date, and signature of the course offering plan, scheduling table, and course selection rules are consistent.
- Check the options and branch connections one by one in the node, trigger an interaction once, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the references in the version ledger and change records are updated in sync.