What this category's data looks like
This page focuses on multilingual materials and terminology handling materials under the course selection, scheduling, and classroom resource dispatch category. Sources include three base drafts—the course offering plan, the scheduling table, and the course selection rules—as well as the terminology comparison draft, historical version receipts, and signature pages. The update cadence advances by semester rounds; each round first has the teaching management side issue the course offering plan, then generates the scheduling table, and finally attaches the course selection rules description. Field characteristics center on course name, course code, classroom number, week number, period, capacity, course selection priority, effective date, and signature field. When entering workflow orchestration, the course offering plan serves as the baseline field source, the scheduling table serves as the time and space constraint role, the course selection rules serve as the admission and priority role, the terminology comparison draft serves as the cross-language back-reference role, and the receipts and signature pages serve as the version confirmation role. Multilingual materials are split into branches to be selected within the node, for subsequent nodes to continue processing by branch.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction state record. "Unified terminology table and comparison draft" is completed by subsequent nodes continuing execution by 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 chosen option.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Check whether the course name, course code, effective date, and signature field are consistent with the scheduling table | Compare the course offering plan and the scheduling table field by field, check whether the name, code, and date of the same course match across the two materials, and confirm whether the signature or receipt exists |
| Scheduling table | Check whether the classroom number, week number, period, and capacity are consistent with the course selection rules description | Check the classroom, time, and capacity fields in the scheduling table and the course selection rules description one by one, and check whether the quantity and date of the same record fail to match across the two materials |
| Course selection rules | Check whether the course selection priority, admission conditions, and version number are in sync with the course offering plan | Extract three rules, back-reference the course code and effective date in the course offering plan, and check for unsynchronized versions and missing receipts |
| Terminology comparison draft | Check whether the same term is written consistently throughout and whether the translated name can back-reference the original text | Trial-run each option within the node, check variables, nodeId, and the branch direction, and confirm that the interaction state record and the selection result variable have been passed to subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same course fail to match across the two materials. Cause: The course offering plan and the scheduling table each maintain their own fields, without field-by-field comparison.
- Symptom: The course selection rules version is not synchronized, and the old priority is still referenced. Cause: The version number and effective date were not updated along with the course offering plan, and the receipt is missing.
- Symptom: After the interaction completes, the process stalls, or a certain option is selected but the default branch is still taken. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
This feature's acceptance: trial-run each option one by one, and check the branch direction and interaction state in the run record; reference variables and nodeId in subsequent nodes to confirm that the selection result variable has been passed.
Business test: sample three terms to check whether they are written consistently throughout, and confirm that the translated names can back-reference the original text.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- Reference
variablesin a subsequent node and trial-run once to confirm that the same session does not repeatedly enter the interaction.