What this category's data looks like
Modern apprenticeship and order class management materials include school-enterprise cooperation agreements, order class training plans, and master apprenticeship records. School-enterprise cooperation agreements specify the cooperation period and rights and responsibilities, order class training plans state the courses and rotation arrangements, and master apprenticeship records register the apprenticeship content and evaluations one by one. The materials come from academic affairs, secondary colleges, and training bases, and are updated by semester or training cycle. The field characteristics are multiple entities, multiple dates, and multiple signatures: agreements contain signing dates and seals from both parties, plans contain version numbers and approval signatures, and apprenticeship records contain apprenticeship dates, master signatures, and student confirmations. When entering workflow orchestration, agreements and plans serve as branching bases, while apprenticeship records serve as process evidence, each with a different role.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The handover-ready deployment status and operation records are continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Whether the signing date and signatures from both parties are complete, and whether the agreement version number and training plan version number are synchronized | Check the options and branch connections one by one in the user selection node, and check whether the agreement version and plan version are consistent |
| Order class training plan | Whether the course names, quantities, and dates in the training plan match the master apprenticeship records | Reference the selection result variable variables in subsequent nodes and run a trial, then check the branch direction in the run records |
| Master apprenticeship record | Whether the apprenticeship date, master signature, and student receipt are missing items, and whether the names and quantities are consistent with the plan | Trigger a user selection node once, and view the node status and nodeId in the run records |
| Deployment status and operation records | Whether the version, connection, and task records are consistent | Check item by item once according to the handover form, and see which record is missing |
Three common errors
- Phenomenon: The same apprenticeship record has inconsistent names, quantities, and dates in the training plan and apprenticeship record. Cause: The two materials are updated separately, and no field-level comparison is performed.
- Phenomenon: The agreement version is not synchronized to the training plan, and the branch still follows the old version. Cause: The version number is not written into the node check items when the materials are updated.
- Phenomenon: The apprenticeship record lacks a master signature or student receipt, and it cannot be confirmed during handover. Cause: The receipt is not included in the node branch judgment and records.
How to verify the setup
Acceptance of this function: Run trials on each option one by one, check the branch direction and interaction status in the run records, confirm that the selection result variable variables has been passed to subsequent nodes, and record nodeId.
Business test: Check item by item once according to the handover form, see which record is missing, and confirm that the version, connection, and task records are consistent.
- 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
variablesin subsequent nodes and run a trial once, confirming that the process continues downward after the interaction is completed.