What this category's data looks like
This category's data looks like this: Materials for undergraduate program setup and dynamic adjustment include three types: program setup application forms, talent cultivation plans, and expert review opinions. Application forms come from departmental applications; talent cultivation plans are updated along with cultivation objectives and the curriculum system; expert review opinions are formed during the review stage. The three types of materials play different roles when entering the workflow: application forms provide the program name, code, degree-granting category, and application date; talent cultivation plans provide course modules, credits and class hours, and the length of study; expert review opinions provide review conclusions, the list of experts, and signed receipts. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures, and versions change with revisions to the talent cultivation plan and rounds of review. The update rhythm advances according to application batches and review cycles. Each adjustment must synchronize the same record across the three types of materials to avoid names, quantities, and dates not matching between two materials, or versions not being synchronized, or missing signatures and receipts.
Configuration and implementation checks
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 continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Program setup application form | Whether the name, code, degree-granting category, application date, and signature are complete, and whether they align item by item with the talent cultivation plan and expert review opinions | Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run records, and reference the selection result variable in a subsequent node for a trial run |
| Talent cultivation plan | Whether the quantities and dates of course modules, credits and class hours, and length of study are consistent with the application form, and whether the version is synchronized | Compare names, quantities, and dates item by item against the application form, check the version number and revision records, and confirm there are no missing signatures or receipts |
| Expert review opinions | Whether the review conclusions, list of experts, signatures, and receipt dates are consistent with the application form and talent cultivation plan | Check the signature page and receipt dates, and verify whether the names, quantities, and dates of the same record match across the two materials |
| User selection node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once to view the run records, and reference this variable in a subsequent node for a trial run |
Three common errors
- Symptom: after selecting an option, it still follows the default branch. Cause: the options and branch connections were not checked item by item, and the branch direction is inconsistent with the interaction state record.
- Symptom: the name, quantity, and date of the same record do not match between the application form and the talent cultivation plan. Cause: the version was not synchronized, and the other material was not backfilled after revision.
- Symptom: the process stops after the interaction is completed. Cause: the selection result variable was not passed to subsequent nodes, or the expert review opinions lack signatures and receipts, causing missing items in the handover form check.
How to verify the setup
How to verify the setup: Functional acceptance: run trials for each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes; if necessary, use variables and nodeId to locate it.
Business testing: check item by item once according to the handover form, see which record is missing, and focus on checking whether the names, quantities, dates, and signatures of the program setup application form, talent cultivation plan, and expert review opinions are consistent.
- Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run records, and record the correspondence between
nodeIdandvariables. - Check the names, quantities, dates, and signatures of the three types of materials item by item against the handover form, confirm that versions are synchronized and there are no missing receipts, and then hand over to operations or the next shift.