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 come from the school and enterprise signing, and are updated with the cooperation cycle; fields include cooperation name, number of people, start and end dates, signatures and receipts. Order class training plans come from the teaching management department and are revised by semester or academic year; fields include course name, number of class hours, class start date, and approval signature. Master-apprentice mentoring records come from the mentoring process and are reported weekly or monthly; fields include apprentice name, position name, mentoring duration, and master's signature. When these three types of materials enter workflow orchestration, the school-enterprise cooperation agreement serves as the constraint source, the order class training plan serves as the execution basis, and the master-apprentice mentoring records serve as process evidence; each undertakes the role of version comparison and reference synchronization, forming a version ledger and change records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an 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 |
|---|---|---|
| School-enterprise cooperation agreement | Whether the cooperation name, number of people, start and end dates, signatures and receipts are consistent with the order class training plan | Check the options and branch connections one by one in the user selection node, and use variables and nodeId to record the branch direction |
| Order class training plan | Whether the course name, number of class hours, class start date, and approval signature are aligned with the master-apprentice mentoring records | Trigger one interaction, check the node status in the run records, and verify whether the selection result variable has been passed to subsequent nodes |
| Master-apprentice mentoring records | Whether the apprentice name, position name, mentoring duration, and master's signature match the training plan and cooperation agreement | Reference the variable corresponding to nodeId in subsequent nodes and run a test to confirm that the reference is synchronously updated |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, run a test and check whether the version number and references are synchronously updated |
Three common errors
- Symptom: The name, number of people, and dates of the same record do not match between the school-enterprise cooperation agreement and the order class training plan. Cause: The two materials are updated separately, without field comparison and reference synchronization.
- Symptom: The version is not synchronized, and the old training plan is still referenced by subsequent nodes. Cause: After the change, the branch rerun was not triggered, and the interaction status was not refreshed.
- Symptom: The master-apprentice mentoring record lacks the master's signature or receipt. Cause: The reporting step did not validate the signature field, and the material was not intercepted when entering the workflow.
How to verify the setup
This feature acceptance: run tests on each option one by one, check the branch direction and interaction status 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 variables and nodeId references are correct.
Business test: change one piece of content and see whether the version number and references are synchronously updated
- Check the options and branch connections one by one in the user selection node, and trigger one interaction to view the node status
- Reference the selection result variable in subsequent nodes and run a test to check the version ledger and change records