What this category's data looks like
Modern apprenticeship and order class management involves three types of materials: school-enterprise cooperation agreements, order class training plans, and master-apprentice mentoring records. School-enterprise cooperation agreements are drafted jointly by the school and the enterprise, including cooperation period, number of positions, training objectives, and signatures and seals; order class training plans are compiled by the teaching team, including course modules, credit hour allocation, rotation arrangements, and assessment methods; master-apprentice mentoring records are filled in weekly by the mentoring master, including apprentice name, position, mentoring content, attendance, and evaluation. Material sources are scattered across academic affairs, enterprise human resources, and workshop teams, and the update rhythm fluctuates with the semester and production cycle. When entering workflow orchestration, the three types of materials respectively assume the roles of basis, plan, and process trace, and must maintain consistency in names, quantities, dates, and signatures during the drafting and handover stages.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Material drafts and handover records that can be issued" are 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 |
|---|---|---|
| School-enterprise cooperation agreement | Whether the cooperation period, number of positions, training objectives, and signatures and seals are complete, and whether they are consistent with the cooperating enterprise name, professional direction, and date in the order class training plan | In the node, check the options and branch connections one by one, trigger once to view the node status in the run record, and reference variables and nodeId to track whether the selection result variable has been passed to subsequent nodes |
| Order class training plan | Whether the course modules, credit hour allocation, rotation arrangements, and assessment methods are complete, and whether they match the apprentice name, position, and mentoring cycle in the master-apprentice mentoring records | In subsequent nodes, reference variables and run a trial once, check whether the plan version number and date are synchronized, and whether missing items are blocked |
| Master-apprentice mentoring record | Whether the apprentice name, position, mentoring content, attendance, evaluation, master signature, and receipt are complete, and whether the name, quantity, and date of the same record are consistent across the two materials | Trigger the user selection node once, view the branch direction and interaction state in the run record, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Phenomenon: The same apprentice name is written differently in the two materials, and the number of mentoring weeks does not match the credit hours in the training plan. Cause: The materials are maintained separately by academic affairs and the enterprise workshop team, lacking unified fields and date verification.
- Phenomenon: The training plan has been updated, but the master-apprentice mentoring record still references the old version, causing date misalignment during handover. Cause: The version was not synchronized, and the handover record was not bound to the plan version number.
- Phenomenon: The school-enterprise cooperation agreement lacks the enterprise seal, and the master-apprentice mentoring record lacks a receipt, so the materials cannot be issued. Cause: The signature and receipt steps were not included in branch verification, and missing items were not blocked.
How to verify the setup
Acceptance of this function: Run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and record variables and nodeId.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- In subsequent nodes, reference the selection result variable and run a trial once, and check whether the fields are complete, the responsible person is clear, and the version and date are consistent.