What this category's data looks like
Materials for undergraduate program setup and dynamic adjustment include program setup application forms, talent training plans, and expert review opinions. The sources are submissions from academic affairs and colleges, and the update cadence advances with the application season and annual adjustment milestones. When the three types of materials enter the workflow, their roles differ: the application form carries the setup rationale and conditions, the plan carries the course and credit structure, and the review opinions carry the expert conclusions and signature receipts. Field characteristics center on program name, code, length of study, degree, enrollment number, number of courses, total credits, review date, and signature field. For the same record, the name, quantities, and dates in the application form and the plan must be aligned item by item, and the version number and reference location must be maintained in sync.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the 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 setup application form | Whether the fields, dates, and signatures are consistent with the talent training plan | Check the program name, code, length of study, degree, and enrollment number item by item, compare the dates and signature fields of the two materials, and record discrepancies |
| Talent training plan | Whether the number of courses, total credits, and review date match the application form | Extract the course and credit fields, compare them item by item with the application form, check whether the version number is in sync, and verify the signatures and receipts of the expert review opinions |
| Expert review opinions | Whether the signatures and receipts are complete, and whether the dates are consistent with the plan | Check the expert list, review date, and signature field, confirm the receipts are complete, and check whether the plan version referenced by the opinions is the current version |
| User selection node | Whether each option corresponds to one branch, and whether the interaction state is recorded | Check the options and branch connections one by one in the node, trigger it once to view the node state in the run records, reference variables in subsequent nodes and do a trial run, and check the branch direction corresponding to nodeId |
Three common errors
- Symptom: the name, enrollment number, and date of the same program do not match between the application form and the plan. Cause: the two materials were modified separately, without field-level comparison and version synchronization.
- Symptom: the plan has been updated, but the review opinions still reference the old version, and the reference was not synchronized. Cause: the version number was not updated with content changes, and the reference location does not point back to the current version.
- Symptom: the review opinions lack signatures or receipts, and the materials are returned. Cause: the signature field and receipt completeness were not checked at submission, and the branch direction was not checked after the interaction was completed.
How to verify the setup
Feature acceptance: run trial runs option by option, check the branch direction and interaction state in the run records, reference variables in subsequent nodes, and check the branch corresponding to nodeId.
Business test: change one piece of content, see whether the version number and reference are updated in sync, and confirm that the current version is unique, old versions are traceable, and references are synchronized.
- Check the options and branch connections one by one, trigger it once to view the node state in the run records, and confirm that the interaction state is recorded and the selection result variable has been passed to subsequent nodes.
- Change one program name or enrollment number, check whether the version number and reference location are updated in sync, and verify whether the signatures and receipts are complete.