What this category's data looks like
This page addresses the category of course selection, scheduling, and classroom resource allocation. Material sources include course offering plans, scheduling tables, course selection rules, classroom resource lists, handover records, and receipts. The update cadence changes with the semester stage: course offering plans are revised by round, scheduling tables are adjusted multiple times before and after course selection, course selection rules are updated with batch instructions, and classroom resource lists are maintained according to occupancy and release status. Field characteristics center on course name, course code, class size, week number, period, classroom number, capacity, course selection restrictions, version number, effective date, responsible person, and signature field. When materials enter workflow orchestration, the course offering plan provides the basis for courses and class sizes, the scheduling table provides the basis for time and classroom occupancy, the course selection rules provide admission and capacity constraints, and the handover records and receipts are used to confirm the transfer of responsibility. Each material plays a different role in the nodes: some serve as the basis for branch decisions, and some serve as input for subsequent nodes to continue execution. They do not replace manual selection, nor do they directly produce a signable final product.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The signable material drafts and handover records are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an 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 | Course name, course code, class size, version number, and effective date are consistent in the draft and handover record, and the responsible person and signature field are complete | Check the options and branch connections one by one in the node, confirm which branch the course offering plan corresponds to when used as the basis for branching, and view the node status in the run record |
| Scheduling table | Week number, period, classroom number, capacity, and date are consistent in both materials; if the version is not synchronized, it must not enter handover | Reference the selection result variable variables in a subsequent node and run a trial once, checking whether the scheduling table fields match the branch direction |
| Course selection rules | Course selection restrictions, capacity upper limit, effective date, and signature receipt are complete; the name and quantity of the same record must not conflict between different materials | Check the nodeId of the branch corresponding to the course selection rules and the run record, and confirm that the selection result has been passed to the subsequent node |
| Handover records and receipts | Responsible person, signature, receipt, version, and date are complete; if any item is missing, the node blocks it and returns to the interaction state | Draft one according to the template and complete one handover, check whether missing items are blocked, and verify the interaction status record |
Three common errors
- Phenomenon: The name, class size, or date of the same course does not match between the two materials. Cause: The course offering plan and scheduling table are revised separately, and field comparison and version synchronization were not done before handover.
- Phenomenon: The material has been circulated but the signature or receipt is missing. Cause: The handover record did not make the responsible person and signature field mandatory fields, and the node did not block the missing items.
- Phenomenon: A certain option was selected but the default branch was still followed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not correctly referenced in the subsequent node.
How to verify the setup
This function acceptance: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that the selection result variable has been passed to the subsequent node and that the nodeId corresponds to the correct branch.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, trigger once, and then view the node status and branch direction in the run record.
- Reference the selection result variable
variablesin a subsequent node and run a trial once, checking the fields, dates, and signatures of the course offering plan, scheduling table, course selection rules, and handover record.