What this category's data looks like
Graduate training process management covers three core types of materials: training plans, proposal reports, and mid-term assessment forms. The training plan includes course credits, supervisor signature, and date; the proposal report includes topic title, review comments, proposal date, and expert group signature; the mid-term assessment form includes assessment conclusion, course grades, assessment date, and supervisor and college seals. The materials come from archived documents for each training stage and are updated at semester or academic year milestones. The same record often shows inconsistencies in names, quantities, and dates because versions are not synchronized or receipts are missing. When entering workflow orchestration, the training plan serves as the starting-point basis, the proposal report provides supporting evidence for process nodes, and the mid-term assessment form serves as a stage conclusion reference back. Together, the three types of materials support basis entries that can be traced back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. Basis entries that can be traced back to the original text are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and records the workflow status. After the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Whether fields, dates, and signatures match the proposal report and mid-term assessment form | In the node, check the options and branch connections one by one, use variables and nodeId to locate the node, and run a trial to view the node status in the run record |
| Proposal report | Whether the topic title, quantity, and date are consistent across the two materials, and whether signatures and receipts are complete | In subsequent nodes, reference the selection result variable and run a trial, then check the branch direction corresponding to the option |
| Mid-term assessment form | Whether the assessment conclusion and course grades are synchronized with the versions of the training plan and proposal report | Trigger the user selection node once and view the interaction status and branch direction in the run record |
| User selection node | Whether each option corresponds to one branch connection | In the node, check the options and branch connections one by one, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match between the training plan and the proposal report. Cause: Materials are archived separately by semester, fields are entered without cross-checking, and versions are not synchronized.
- Phenomenon: The mid-term assessment form lacks the supervisor signature or college receipt. Cause: The assessment process and material archiving are not synchronized, and the signature step is not completed when the version is updated.
- Phenomenon: After selecting an option, the default branch is still followed, or the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
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, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes. Use variables and nodeId to locate the node.
Business test: ask a basis question that spans materials and see whether the answer gives a traceable source, whether the basis comes from this field's materials, whether the version is current, and whether the entry matches the original text.
- In the node, check the options and branch connections one by one, trigger the user selection node once, and view the node status and interaction status in the run record.
- In subsequent nodes, reference the selection result variable and run a trial once, confirm the branch direction and interaction status record, and check the correspondence between this variable and
nodeId.