What this category's data looks like
Materials for the course selection, scheduling, and classroom resource dispatch category come from three sources: course offering plans, scheduling tables, and course selection rules. The update cadence changes with semester batches and schedule adjustment receipts. Course offering plans provide course and teaching class fields; scheduling tables provide time, classroom, and instructor fields; course selection rules provide capacity, priority, and constraint fields. When materials enter workflow orchestration, course offering plans serve as the branching basis, scheduling tables serve as resource occupancy records, and course selection rules serve as the source of options for user selection nodes. Each of the three types of materials handles field preparation before entering the interaction state. After the interaction is complete, subsequent nodes continue execution according to the branch, forming a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution according to the branch. When a 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 | Course name, number of teaching classes, and course start date are consistent item by item across the three materials, and signatures and receipts are complete | Check options and branch connections one by one in the node, and verify whether the course offering plan fields match the scheduling table and course selection rules |
| Scheduling table | Time, classroom, and instructor fields are consistent with the course offering plan dates, the version number is synchronized, and no signatures are missing | Trigger a user selection node once, view the node status in the run records, and verify whether the scheduling table version is synchronized |
| Course selection rules | Capacity, priority, and constraint fields are consistent with the scheduling table quantities, and receipts are complete | Reference the selection result variable in a subsequent node and run a trial once, and verify whether the course selection rule fields are consistent with the course offering plan |
| User selection node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | Check the variables and nodeId references in the node, and after a trial run, view the branch direction and interaction state records |
Three common errors
- Symptom: The name, quantity, or date of the same course does not match across two materials. Cause: The course offering plan and scheduling table were not updated synchronously according to the same batch.
- Symptom: The scheduling table version is not synchronized, and the process stops after the interaction is complete. Cause: The version number was not updated with the schedule adjustment receipt, and the branching basis is outdated.
- Symptom: The course selection rules are missing signatures or receipts, and after selecting an option, the default branch is still taken. Cause: The receipts were not archived, and the options and branch connections were not checked.
How to verify the setup
Acceptance for this feature: Run trials for each option one by one, check the branch direction and interaction state in the run records, and verify whether the variables and nodeId references take effect.
Business test: Check item by item once according to the handover form, see which record is missing, and confirm that the version, connection, and task record are consistent.
- Check options and branch connections one by one in the node, confirm that each option corresponds to one branch, and record the
nodeIdandvariablesreference locations. - Trigger a user selection node once, view the node status and branch direction in the run records, and check whether the version, connection, and task record in the handover form are complete.