What this category's data looks like
Undergraduate program revision involves three types of materials: program plans, course syllabi, and credit structure tables. Program plans come from the academic affairs management department and are updated according to the annual revision cycle; their fields include major name, curriculum system, total credits, and signature fields. Course syllabi come from the respective course-offering units and are updated as courses are adjusted; their fields include course name, class hours, credits, and the signature of the person who wrote them. Credit structure tables come from academic affairs consolidation and are synchronized with the finalized program plan; their fields include course modules, credit amounts, and review signatures. After these three types of materials enter scheduled tasks and automation, the trigger configuration is responsible for starting them according to revision milestones, and the tool node is responsible for reading the materials and outputting trigger records and execution results; the version ledger and change records are completed by business processing executing according to the records or rerunning, ensuring that the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This part is executed by the trigger configuration and the tool node (scheduling capability is not in the tool introduction), outputting trigger records and execution results. The "version ledger and change records" are then completed by business processing executing according to the records or rerunning. Whether the tool is called is decided by the model based on the tool introduction; when the model does not need to summarize again, a tool call termination node can be connected at the end of the tool to end this call.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Major name, curriculum system, total credits, date, and signature are unique and traceable in the version ledger | Check the introduction fields and process connections, confirm that the trigger has been connected to the corresponding tool node, and view the trigger records and execution results |
| Course syllabus | Course name, class hours, credits, and the signature of the person who wrote it are consistent with the program plan, and old versions are traceable | Check the introduction fields and where the termination node is connected, and confirm that when no summary is needed it has been connected at the end of the tool |
| Credit structure table | Course modules, credit amounts, and review signatures match the program plan and course syllabi | View the trigger records and execution results, confirm that execution occurs on time and only once, and that references are updated synchronously |
| Version ledger and change records | The current version is unique, old versions are traceable, references are synchronized, and change traces are complete | Change one piece of content and see whether the version number and references are updated synchronously; when signatures or receipts are missing, rerun |
Three common errors
- Symptom: The course name and credit amount for the same record do not match between the program plan and the course syllabus. Cause: The materials are maintained separately, versions are not synchronized, and references are not updated when one piece of content is changed.
- Symptom: An old version of the program plan is still referenced, and the current version is not unique. Cause: The version ledger was not updated according to the trigger records, the old version was not marked as traceable, and reference synchronization is missing.
- Symptom: The credit structure table is missing signatures or receipts, and the revision milestone has passed. Cause: After the scheduled task executes on time, business processing did not rerun according to the records, and signature receipts were not archived.
How to verify the setup
Acceptance for this feature: look at the trigger records and execution time, and confirm that execution occurs on time and only once.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the process connections and trigger records, confirm that the trigger has been connected to the corresponding tool node, and that the tool introduction clearly states when it should execute.
- Check where the termination node is connected, and confirm that when no summary is needed it has been connected at the end of the tool, avoiding the model summarizing it again after execution.