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 mentorship records. School-enterprise cooperation agreements include the cooperation period, positions and number of people, and signatures/seals; order class training plans include course modules, rotation arrangements, and assessment milestones; master-apprentice mentorship records include the mentorship period, task lists, and signatures of the master and apprentice. The material sources are three parties: school academic affairs, enterprise human resources, and mentoring masters, and the update rhythm is synchronized by semester and rotation batch. When entering this function, the three types of materials respectively serve as the authorization basis, the basis for dividing the visible scope, and the basis for process traceability, for subsequent nodes to orchestrate the external entry points and authorization scope.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The external entry points and authorization scope are further executed and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters an 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, positions and number of people, and signatures/seals are consistent with the order class training plan | Check the name, quantity, date, and signatures of the agreement and training plan one by one, and check whether the variables references point to the same version |
| Order class training plan | Whether the course modules, rotation arrangements, and assessment milestone dates align with the master-apprentice mentorship records | Compare the task lists and dates of the plan and mentorship records; mark those missing signatures or receipts as pending supplementation |
| Master-apprentice mentorship record | Whether the mentorship period, task list, and signatures of the master and apprentice are complete and version-synchronized | Spot-check records by batch, and verify whether the visible scope of the branch corresponding to nodeId matches the identity |
| User selection node | Each option corresponds to one branch, and the selection result variable has been passed to subsequent nodes | Trial-run each option one by one, and check the node status and branch direction in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the agreement and the training plan. Cause: The two materials are maintained separately, without cross-checking and version synchronization.
- Symptom: The master-apprentice mentorship record is missing signatures or receipts. Cause: After the rotation batch ends, signatures were not collected in time, and receipts were not archived.
- Symptom: After selecting an option, the default branch is still followed. 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 of this function: Trial-run each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the references to variables and nodeId are correct.
Business test: Access once with a restricted identity, and see whether the visible scope matches the setting, and unauthorized content is not visible.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run records.
- Reference the selection result variable in a subsequent node and trial-run once, confirming that the branch direction is consistent with the interaction state record.