What this category's data looks like
This category covers the drafting of materials and the handover of responsibilities for undergraduate program establishment and dynamic adjustment, involving three types of materials: program establishment application forms, talent cultivation plans, and expert review opinions. Application forms come from college submissions and include the program name, code, length of study, and degree-granting category; cultivation plans come from the teaching committee and include the curriculum system, credit structure, and practical components; review opinions come from external experts and include the review date, expert signatures, and conclusion opinions. The three types of materials are updated on an academic-year cycle, with drafting concentrated during the application season and handover concentrated during the review season. When entering the workflow, the application form serves as the master record, while the cultivation plan and review opinions serve as attachments and supporting evidence; the fields of the three must interlock with one another in terms of name, quantity, date, signature, and version.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The material drafts and handover records that can be issued are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction 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 establishment application form | Fields complete, responsible person clear, version and date consistent | Verify the program name, code, length of study, and degree category; check the signature field and version number; check options and branch connections one by one in the node, and confirm that nodeId corresponds to the branch |
| Talent cultivation plan | Name, quantity, and date consistent with the same record as the application form | Compare whether the number of courses and total credits match those filled in the application form; check whether the version is synchronized; reference variables in subsequent nodes and run a trial once |
| Expert review opinions | Signatures and receipts complete, review date traceable | Verify expert signatures, review date, and conclusion opinions; check whether receipts are attached; trigger a user selection node once and view the node status in the run record |
| Handover record | Responsible person clear, receipt status checkable | Verify the handover person and receipt person fields; check whether version and date are consistent; confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: The name and course quantity of the same program do not match between the application form and the cultivation plan. Cause: The two materials were drafted separately, were not backfilled from the master record, and the fields were not cross-checked.
- Symptom: The expert review opinions have been updated, but the application form still references the old version. Cause: The version was not synchronized, the version number and date were not checked during handover, and the old draft continued to circulate.
- Symptom: The handover record lacks a signature or receipt, and the next step cannot be signed for. Cause: The responsible person field was left blank, the receipt node did not enforce a receipt, and the process could still continue.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction state in the run record, and confirm that nodeId and variables are correctly referenced in subsequent nodes.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection node once, and check whether the node status in the run record and the selection result variable have been passed to subsequent nodes.