What this category's data looks like
Materials in the course selection, scheduling, and classroom resource scheduling category usually include three types: course offering plans, scheduling tables, and course selection rules. Course offering plans indicate the course name, number of classes, start and end dates, and approval signature; scheduling tables record the week, period, classroom number, and instructor; course selection rules specify the selectable scope, priority, and effective version. These materials are generated by the academic affairs department by semester, and the update rhythm is concentrated before course selection opens and during the schedule adjustment window. The field characteristics are multi-table cross-referencing, dense dates, and the coexistence of signatures and receipts. When entering the workflow orchestration function, the course offering plan serves as the input source for branch judgment, the scheduling table provides classroom and time slot constraints, and the course selection rules determine the visible scope and authorization boundary. The three types of materials play different roles in the nodes: plans and rules are used to generate options, the scheduling table is used to verify conflicts, and the final external entry point and authorization scope are completed by subsequent nodes continuing execution according to the branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branch), outputting the branch direction and interaction status records. "The externally available entry point and authorization scope" is then completed by subsequent nodes continuing execution according to the branch. When triggered, the conversation enters the interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Check whether the course name, number of classes, start and end dates, and signature are consistent with the scheduling table | Compare fields and dates item by item, check whether signatures or receipts are complete, and confirm that the version number is synchronized |
| Scheduling table | Check whether the classroom number, week and period, and instructor correspond to the course offering plan | Spot-check the name, quantity, and dates of the same record in both materials, and mark inconsistent items |
| Course selection rules | Check whether the selectable scope, priority, and effective version match the authorization scope of the external entry point | Check the options and branch connections one by one in the node, and reference variables to run a trial once |
| User selection node | Check the options and branch connections, interaction status records, and selection result variable passing | Trigger once, view the node status in the run record, and confirm that nodeId corresponds to the branch direction |
Three common errors
- Symptom: The number of classes for the same course does not match between the course offering plan and the scheduling table. Cause: The two materials are maintained separately, versions are not synchronized, and there is no unified receipt.
- Symptom: The dates in the course selection rules are inconsistent with the start and end dates in the course offering plan. Cause: After an update during the schedule adjustment window, only one material was changed and the other was not synchronized.
- Symptom: The visible scope of the external entry point exceeds the authorization setting. Cause: The option branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
How to verify the setup
Acceptance for this function: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm the correspondence between variables and nodeId.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and view the node status in the run record and the passing of the selection result variable.