What this category's data looks like
The revision of undergraduate programs involves three types of materials: program plans, course syllabi, and credit structure tables. The sources are the academic affairs system and revision drafts submitted by departments, with updates concentrated on a semester or annual basis. Field characteristics include course name, credit count, course start date, signature field, and receipt status. The program plan serves as the master outline, the course syllabus serves as the course-level description, and the credit structure table serves as the quantitative summary. When entering the workflow, the three respectively assume the roles of main document, sub-document, and verification table, and reference relationships need to be established in the version ledger to ensure the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Program plan | Whether the name, date, and signature are consistent with the course syllabus and credit structure table | Check the options and branch connections one by one in the node, and check whether variables are passed to subsequent nodes |
| Course syllabus | Whether the course name, credit count, and course start date match the program plan and credit structure table | Trigger a user selection once, and check the nodeId and node status in the run record |
| Credit structure table | Whether the credit total, date, and signature receipt are synchronized with the program plan and course syllabus | Reference variables in subsequent nodes and run a test once to confirm the branch direction |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously |
Three common errors
- Symptom: The same course name is written differently in the program plan and the course syllabus. Cause: Field conventions were not unified during revision, and the version ledger did not establish reference synchronization.
- Symptom: The credit structure table has been updated, but the program plan still shows the old version. Cause: The version was not synchronized, the old version was not marked invalid, and the reference relationships were not refreshed with the changes.
- Symptom: The course syllabus lacks a signature or receipt. Cause: The revision process was not completed, and the signature field and receipt status were not verified when the materials entered the workflow.
How to verify the setup
Acceptance for this feature: Run tests option by option, check the branch direction and interaction status in the run record, and confirm that variables, nodeId, and option branches correspond.
Business test: Change one piece of content and see whether the version number and references are updated synchronously
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch
- Reference the selection result variable in subsequent nodes and run a test once to confirm the branch direction and interaction status record