What this category's data looks like
In modern apprenticeship and order class management, three types of materials—school-enterprise cooperation agreements, order class training plans, and mentor apprenticeship records—play different roles: school-enterprise cooperation agreements define the cooperation period and responsibilities; order class training plans specify courses, number of participants, dates, and rotation arrangements; mentor apprenticeship records log the content, quantity, and signatures of each apprenticeship session. Materials are mostly updated by academic year or semester, parallel versions are common, and fields include name, quantity, date, signature, and receipt. When entering workflow orchestration, the three types of materials serve respectively as exception comparison sources, training benchmarks, and process evidence; the exception list and review conclusions must be traceable back to specific material pages and fields.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution along 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 agreement name, cooperation period, and signature receipt are consistent with the order class training plan | At the user selection node, check the options and branch connections, compare the name, date, and signature of the agreement and training plan item by item, and use nodeId to locate the node |
| Order class training plan | Whether the courses, number of participants, and rotation dates match the mentor apprenticeship records, and whether the versions are synchronized | Trigger an interaction state, view the node status in the run records, and use variables to check whether the selection result variable has been passed to subsequent nodes |
| Mentor apprenticeship record | Whether the name, quantity, date, and signature of each apprenticeship session can be traced back to the source material | At a subsequent node, reference the selection result variable and run a trial, then check the fields of the apprenticeship record against the training plan and agreement |
| Exception list and review conclusions | Whether each item indicates the source of the original record, the reviewer's signature, and the disposition destination | Create an exception record and trace it along the branch direction to the source material page and field |
Three common errors
- Symptom: The name, quantity, and date of the same apprenticeship record do not match between the training plan and the mentor apprenticeship record. Cause: The two materials are maintained separately, lacking cross-comparison and unified naming.
- Symptom: The training plan has been updated, but the mentor apprenticeship record is still registered according to the old version. Cause: Versions are not synchronized, and updates do not trigger review and receipt.
- Symptom: The exception list lacks signatures or receipts and cannot be handed over to the responsible person for disposition. Cause: The review step leaves no trace, and the signature and receipt fields are not included in the check.
How to verify the setup
Acceptance of this feature: Run trials for each option one by one, check the branch directions and interaction states in the run records, confirm that the selection result variable has been passed to subsequent nodes, and use nodeId to locate nodes and variables to reference variables.
Business test: Create an exception record, see whether it can be traced back to the source material, and check whether the exception list and review conclusions are supported by original records and the reviewer's signature.
- At the user selection node, check the options and branch connections one by one, trigger an interaction state, and view the node status in the run records.
- At a subsequent node, reference the selection result variable and run a trial, then check whether the exception list and review conclusions can point back to specific fields in the school-enterprise cooperation agreement, order class training plan, and mentor apprenticeship record.