What this category's data looks like
Graduate training process management involves materials such as training plans, proposal reports, and mid-term assessment forms. Their sources are scattered across supervisors, schools, and the academic affairs system, and their update cadence follows semester milestones and review schedules. The training plan contains course credits and research direction fields, the proposal report contains the basis for topic selection and time arrangements, and the mid-term assessment form contains progress descriptions and signature fields. When the materials enter workflow orchestration, the training plan serves as the baseline version, while the proposal report and mid-term assessment form serve as process versions; the three must remain consistent in name, quantity, and date. The version ledger and change records must record the fields and time of each modification, old versions must be traceable, and references must be updated synchronously.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Whether fields, dates, and signatures are consistent with the proposal report and mid-term assessment form | In the user selection node, check options and branch connections one by one, and inspect the passing of references variables and nodeId |
| Proposal report | Whether the name, quantity, and date of the same record do not match across the two materials | Trigger a user selection node once, and view the node status and branch direction in the run record |
| Mid-term assessment form | Version not synchronized, missing signature, or missing receipt | Reference the selection result variable in a subsequent node and run a trial once to verify reference synchronization |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | Change one piece of content and see whether the version number and references are updated synchronously |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the training plan and the proposal report. Cause: Material sources are scattered, and fields and dates were not uniformly checked in the user selection node.
- Symptom: The version of the mid-term assessment form is not synchronized, and the old version is still referenced. Cause: The workflow branch did not update references according to the selection result, and the version ledger did not record the change.
- Symptom: The proposal report or mid-term assessment form is missing a signature or receipt. Cause: The interaction status record did not trigger subsequent nodes to complete the signature process, and the branch direction did not cover the receipt.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction status in the run record, and confirm that variables and nodeId are passed correctly.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the user selection node, check options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger a node once, view the node status in the run record, and confirm that after the interaction is completed, execution continues along the branch corresponding to the selected option.