What this category's data looks like
The materials for undergraduate program revision mainly consist of the program plan, course syllabi, and credit structure table. They come from departmental teaching committees and teaching and research sections, and are updated on a rolling basis by academic year or revision batch. Field characteristics include course name, course code, credits, class hours, semester offered, signature, and date. When entering workflow orchestration, the program plan serves as the master outline and version baseline, the course syllabi serve as the course content and assessment methods, and the credit structure table serves as the credit distribution and ratio verification. The three types of materials form a handover-ready deployment state and operation records during deployment, operations, and application handover. It is necessary to ensure that the version, connections, and task records are consistent, so that operations or the next shift can check item by item according to the handover sheet.
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 the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Program plan | Course name, course code, credits, date, and signature correspond item by item between the program plan and the course syllabi | Check options and branch connections one by one in the node, and reference variables and nodeId to record branch directions |
| Course syllabi | The name, quantity, or date of the same course does not match between the two materials, or the version is not synchronized | Trigger once and check the node status and interaction state in the run records |
| Credit structure table | Credit distribution, number of courses, and signature receipts are complete; missing signatures or receipts need to be supplemented | Reference the selection result variable in subsequent nodes and run a test once, then check the task records |
| Deployment state and operation records | Version, connections, and task records are consistent and can be handed over to operations or the next shift | Check item by item once according to the handover sheet and see which record is missing |
Three common errors
- Phenomenon: The name, credits, or date of the same course do not match between the program plan and the course syllabi. Cause: The two materials are from different revision batches, and field-level comparison and signature confirmation were not performed.
- Phenomenon: The version of the credit structure table is not synchronized, and the number of courses and total credits are inconsistent with the program plan. Cause: After revision, only one place was updated, and the version and receipt were not synchronized by batch.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed correctly.
How to verify the setup
Acceptance of this feature: Run tests for each option one by one, check the branch directions and interaction states in the run records, and confirm that the options and branch connections, variables passing, and nodeId state records are consistent.
Business test: Check item by item once according to the handover sheet, see which record is missing, and confirm that the version, connections, and task records are consistent.
- Check options and branch connections one by one in the node, and record the branch direction corresponding to each option.
- Trigger the user selection node once, check the node status and interaction state in the run records, and confirm that the selection result variable has been passed to subsequent nodes.