What this category's data looks like
Materials for modern apprenticeship and order class management mainly come from three types: school-enterprise cooperation agreements, order class training plans, and master-apprentice mentoring records. School-enterprise cooperation agreements specify positions and headcount, training plans list courses and rotation nodes, and master-apprentice mentoring records register mentoring content and signatures on a weekly basis. Materials are summarized by week and consolidated into monthly reports at month-end, with fields including name, quantity, date, signature, and receipt. When entering workflow orchestration, the agreement serves as the source of the order class definition, the training plan serves as the source of progress nodes, and the mentoring records serve as the source of weekly records; together the three support the verification of the progress table and the statistical definition statement.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "progress table and statistical definition statement" is continued and completed by subsequent nodes according to the branches. When a node is triggered, the conversation enters an interaction state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Whether the order class name, headcount, date, and signature in the agreement are consistent with the training plan | Check the options and branch connections one by one in the node, reference variables to record the agreement definition, and verify the signature and receipt |
| Order class training plan | Whether the rotation nodes, course names, and dates in the plan match the master-apprentice mentoring records | Trigger a user selection node once, check the node status in the run records, and use nodeId to locate the branch direction |
| Master-apprentice mentoring records | Whether the name, quantity, date, and master's signature in the mentoring records are consistent with the weekly record totals | Reference the selection result variable in a subsequent node and run a trial once, and check whether the record count and statistical count match |
| Progress table and statistical definition statement | Whether the header states the statistical definition and exceptions, and whether the totals are consistent with the weekly record verification | Use the weekly records to verify the totals, check whether the definition and exceptions are clearly stated, and confirm the branch direction and interaction state records |
Three common errors
- Symptom: The name and quantity of the same mentoring record do not match between the agreement and the training plan. Cause: The two materials are maintained separately and are not updated in sync under a unified definition.
- Symptom: The training plan version is not synchronized, and the rotation node dates are inconsistent with the mentoring record dates. Cause: After the plan was revised, it was not written back to the progress table, and the branch still executes according to the old version.
- Symptom: Mentoring records lack the master's signature or receipt, yet the statistical totals still include them. Cause: When weekly records were collected, the signature and receipt fields were not checked one by one.
How to verify the setup
This feature's acceptance: run trials option by option, check the branch direction and interaction state in the run records, and confirm that variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: use one week's records to verify the totals, see whether the definition and exceptions are clearly stated, and confirm that the record count and statistical count match and that the definition is written in the header.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction and interaction state records are correct.