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 administrative departments, and their update cadence advances with semesters and milestones. Training plans focus on course and research direction fields; proposal reports contain the basis for topic selection, schedule, and review signatures; mid-term assessment forms record progress, outcomes, and assessment conclusions. When materials enter workflow orchestration, each plays a different role: the training plan provides baseline fields and date baselines, the proposal report and mid-term assessment form serve as objects to be signed off in subsequent steps, and handover records connect responsible persons and versions. Field characteristics include names, student IDs, course names, quantities, dates, signatures, and receipts, and the same record must remain consistent across multiple materials.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. Draftable materials and handover records are completed by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes a selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Course names, quantities, dates, and signatures are complete, and the version is consistent with the proposal report | Check options and branch connections one by one in the node, and inspect whether any training plan fields are missing |
| Proposal report | The basis for topic selection, schedule, review signatures, and receipts are complete, and the dates match the mid-term assessment form | Reference the selection result variable and run a trial once to see whether the proposal report and handover record are synchronized |
| Mid-term assessment form | The assessment conclusion, number of outcomes, responsible person's signature, and date are consistent, and the version is not lagging | Check nodeId and variables in the run record to confirm there are no conflicts in the mid-term assessment form fields |
| Handover record | The responsible person is clear, the version and date are consistent, and the sign-off status of the next stage can be checked | Trigger a handover once, check whether missing items are blocked, and record the branch direction |
Three common errors
- Symptom: The course names and quantities for the same record do not match between the training plan and the proposal report. Cause: Fields were not checked in a unified way, and versions were not synchronized.
- Symptom: The mid-term assessment form is missing a signature or receipt, and the date conflicts with the proposal report. Cause: The handover stage was not completed along the branch, and the responsible person did not confirm.
- Symptom: After selecting a certain option, the default branch is still followed, and the process stops after the interaction is completed. Cause: Options and branch connections were not checked one by one, and the status was not recorded.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that nodeId and variables are passed correctly.
Business test: draft one copy according to the template and complete one handover to see whether missing items are blocked.
- Check options and branch connections one by one in the node to ensure each option corresponds to one branch.
- Trigger one user selection and check whether the node status and selection result variable in the run record have been passed to subsequent nodes.