What this category's data looks like
Modern apprenticeship and order class management materials mainly consist of school-enterprise cooperation agreements, order class training plans, and master-apprentice records. They come from the academic affairs and production departments of both the school and the enterprise, and are updated by semester or training cycle. The school-enterprise cooperation agreement contains the cooperation period, number of positions, signatures, and dates; the order class training plan contains course modules, rotation arrangements, assessment methods, and version number; the master-apprentice records contain the mentoring master, apprentice list, mentoring start and end dates, and signed receipts. When the materials enter the question acceptance and missing-item follow-up function, the school-enterprise cooperation agreement serves as the basis for qualifications and duration, the order class training plan serves as the basis for the training process, and the master-apprentice records serve as the basis for execution traces. The three materials need to be cross-checked on names, quantities, and dates. It is common for the same record to have inconsistent names, quantities, or dates across two materials, for versions not to be synchronized, and for signatures or receipts to be missing. Acceptance records and follow-up questions to be completed are generated accordingly. Missing items are identified and followed up on, and answers must have material basis.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "acceptance records and follow-up questions to be completed" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the interaction 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 |
|---|---|---|
| School-enterprise cooperation agreement | Whether the cooperation period, number of positions, signatures, and dates are consistent with the order class training plan | Check the agreement number, signing date, number of positions, and signature page, verify the options and branch connections one by one in the node, and record nodeId |
| Order class training plan | Whether the course modules, rotation arrangements, version number, and dates correspond to the master-apprentice records | Check the plan version number, rotation start and end dates, and the apprentice list in the master-apprentice records, and view the node status in the run records |
| Master-apprentice records | Whether the mentoring master, apprentice list, mentoring start and end dates, and signed receipts are complete | Check the mentoring start and end dates, master's signature, and apprentice receipts, reference variables in subsequent nodes, and run a trial once |
| User selection node | Whether options and branches correspond one-to-one, and whether the interaction state is recorded | Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records |
Three common errors
- Phenomenon: The same apprentice's name is written differently in the order class training plan and the master-apprentice records, and the quantities and dates do not match. Cause: The two materials are maintained separately by different departments, and no cross-check has been done.
- Phenomenon: The version of the order class training plan is not synchronized, and the old rotation arrangement is still referenced. Cause: The version number and update date are not recorded synchronously as the materials circulate.
- Phenomenon: The school-enterprise cooperation agreement lacks signatures or the master-apprentice records lack receipts, yet answering still proceeds during acceptance. Cause: Missing items are not followed up on first, and the existing content is directly used to continue.
How to verify the setup
Run trials option by option, check the branch directions and interaction state in the run records, confirm that options and branches correspond one-to-one, that the interaction state is recorded, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are referenced in subsequent nodes for verification.
Business test: Submit a question missing key information, see whether it follows up before answering, whether missing items are identified and followed up on, and whether the answer has material basis.
- Check the options and branch connections one by one in the user selection node, and trigger once to view the node status in the run records
- Reference the selection result variable in subsequent nodes and run a trial once, checking the branch directions and interaction state records