What this category's data looks like
Graduate training process management involves three types of materials: training plans, proposal reports, and mid-term assessment forms. The sources are mentor submissions, college academic affairs entries, and system archiving. The update rhythm advances according to semester nodes. Field characteristics include name, student ID, course name, credit count, proposal date, mid-term date, signature field, and receipt field. Training plans are usually formed before proposal reports; proposal reports are added after the topic is determined; mid-term assessment forms are backfilled after the assessment is completed. When the three types of materials enter this function, each participates as an independent comparison object in field verification. The training plan serves as the baseline for courses and credits, the proposal report serves as the baseline for topic selection and dates, and the mid-term assessment form serves as the baseline for assessment conclusions and signatures. If any field shows a difference in name, quantity, or date between two materials, it enters the discrepancy list.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 | Course name, credit count, study date, and signature field are compared item by item across the three types of materials | Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch |
| Proposal report | Whether the topic name, proposal date, and mentor signature are consistent between the two materials | Trigger once, view the node status in the run record, and confirm that the interaction state is recorded |
| Mid-term assessment form | Whether the assessment conclusion, mid-term date, and receipt field are synchronized with the training plan and proposal report | Reference variables in subsequent nodes and run a trial once to confirm that the selection result variable has been passed to subsequent nodes |
| Workflow node | Whether the branch direction and interaction state record correspond to the options | Check the values of nodeId and variables in the run record, and confirm that the branch did not take the default path |
Three common errors
- Symptom: The course name, credit count, and date of the same record do not match between the training plan and the proposal report. Cause: The two materials are entered in different stages, and the fields have not undergone same-source verification.
- Symptom: The version of the mid-term assessment form is not synchronized; the old version lacks a signature field or the receipt is not attached. Cause: After the material is updated, the comparison is not retriggered, and the discrepancy list remains at the previous version.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, or the same session repeatedly enters the interaction.
How to verify the setup
Acceptance of this function: Run a trial for each option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and check the values of variables and nodeId in the record.
Business test: Use a real record to find fields inconsistent with the ledger, compare the training plan, proposal report, and mid-term assessment form field by field, and list fields with mismatched names, quantities, or dates in the discrepancy list.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and record the reference locations of
nodeIdandvariables. - Trigger the user selection node once, view the node status in the run record, and confirm that the interaction state is recorded and the selection result variable has been passed to subsequent nodes.