What this category's data looks like
Graduate training process management materials include training plans, proposal reports, and mid-term assessment forms. Their sources are supervisor submissions, college archiving, and academic affairs system exports, and the update cadence is concentrated at the beginning of each semester and at assessment milestones. The training plan contains course names, credits, start and end dates, and supervisor signatures; the proposal report contains the title, proposal date, and review panel signatures; the mid-term assessment form contains the assessment conclusion, assessment date, and supervisor and college seals. After these three types of materials enter the workflow, the training plan serves as the baseline field source, while the proposal report and mid-term assessment form serve as the objects to be compared, respectively taking on the cross-verification roles for course names, counts, dates, and signatures. Exception records must be traced back to the corresponding original materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusion" is completed by subsequent nodes continuing execution along the branch. 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 |
|---|---|---|
| Training plan | Whether course names, credits, start and end dates, and supervisor signature are consistent with the proposal report | Check the options and branch connections one by one in the node, use nodeId to locate the material reference, and after a trial run check the node status in the run record |
| Proposal report | Whether the title, proposal date, and review panel signature are consistent with the corresponding fields in the mid-term assessment form | Reference the selection result variable variables in a subsequent node and run a trial once to verify whether the branch direction matches the option |
| Mid-term assessment form | Whether the assessment conclusion, assessment date, and supervisor and college seals are complete | Trigger the user selection node once, check the interaction state and branch connections in the run record, and confirm that missing signatures or receipts follow the exception branch |
| Exception list and review conclusion | Whether the exception is supported by original records and whether the reviewer has signed | Continue execution along the branch in subsequent nodes, and check whether the exception record can be traced to the source material and is accompanied by the reviewer's signature |
Three common errors
- Symptom: The same course name is written differently in the training plan and the proposal report, and the count and start and end dates also do not match. Cause: The two materials were entered by different roles at different times, and the fields were not uniformly mapped.
- Symptom: The mid-term assessment form has been updated to a new version, but the proposal report still references the old course list. Cause: The versions were not synchronized, and the node branch still continues execution based on the old material.
- Symptom: The review conclusion lacks the reviewer's signature or receipt, and the exception record cannot be traced to the source material. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue execution along the branch.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable variables has been passed to subsequent nodes, and use nodeId to check the node connections.
Business test: create an exception record, see whether it can be traced to the source material, and confirm that the exception list and review conclusion are supported by original records and the reviewer's signature.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and check the node status and branch direction in the run record.
- Reference the selection result variable
variablesin a subsequent node and run a trial once to confirm that the exception record can be traced to the source material in the training plan, proposal report, or mid-term assessment form.