What this category's data looks like
This page focuses on graduate training process management materials, covering three core document types: training plans, proposal reports, and mid-term assessment forms. The material sources are supervisor submissions, college archiving, and system circulation records; the update cadence advances with semester milestones, and fields include course name, credit count, assessment date, and signature field. The training plan is used to define the training direction and course structure, the proposal report carries the topic basis and argumentation process, and the mid-term assessment form records stage results and review comments. When these three material types enter the Q&A intake and missing-item follow-up function, each plays a different role: the training plan serves as the baseline reference, the proposal report serves as process evidence, and the mid-term assessment form serves as the stage conclusion. Intake records need to cross-compare the same record across the three materials, identify whether the name, quantity, and date are consistent, check version synchronization status and signature receipt completeness, and provide a basis for subsequent follow-up questions and supplementary items.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. "Intake records and supplementary question items" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters the interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Whether the course name, credit count, date, and signature field are complete, and whether the same record is consistent with other materials | Check the options and branch connections one by one in the node, trigger one run to view the node status in the run records, reference variables in subsequent nodes and do a trial run |
| Proposal report | Whether the topic name, argumentation date, supervisor signature, and receipt are complete, and whether the version is synchronized | Check the branch direction corresponding to nodeId, check whether the interaction status is recorded, and confirm that the selection result variable has been passed to subsequent nodes |
| Mid-term assessment form | Whether the assessment date, review comments, signature field, and receipt are missing, and whether the name, quantity, and date of the same record in the two materials do not match | Trigger one interaction, check whether variables take effect in subsequent nodes, and check whether the options and branches correspond one to one |
| Intake record | Whether missing items are identified and followed up, and whether answers have material evidence | Check the branch direction and interaction status in the run records, and confirm that subsequent nodes continue execution according to the branch |
Three common errors
- Symptom: The course name and quantity of the same record do not match between the training plan and the proposal report. Cause: The versions of the two materials are not synchronized, and the update cadence is inconsistent, causing field cross-comparison to fail.
- Symptom: The mid-term assessment form lacks a supervisor signature or receipt, but the intake record still enters the follow-up step. Cause: The signature field and receipt are not included in the scope of missing-item identification, and the material completeness judgment is omitted.
- 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, and the interaction status record was not correctly passed to subsequent nodes.
How to verify the setup
This function's acceptance: run trials for each option one by one, and check the branch direction and interaction status in the run records; check whether variables take effect in subsequent nodes, whether the connection corresponding to nodeId is consistent with the option, and confirm that the selection result variable has been passed.
Business test: submit a question missing key information, and see whether it first asks a follow-up question before answering.
- Check the options and branch connections one by one in the node, and after triggering one interaction, view the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes and do a trial run, confirm that the branch corresponding to
variablesandnodeIdcontinues execution, and that the intake record and supplementary question items are completed by subsequent nodes.