What this category's data looks like
Modern apprenticeship and order class management materials mainly consist of three types: school-enterprise cooperation agreements, order class training plans, and master-apprentice records. The agreement provides the cooperation period, positions, number of people, and signature page; the training plan provides courses, rotations, and assessment milestones; the apprenticeship records provide the master, date, work hours, and receipt. Sources are mostly aggregated from academic affairs, secondary colleges, and enterprises, with updates advancing by semester and batch, and old versions often coexisting with newly signed ones. In terms of fields, names, quantities, dates, and signatures are the four categories most prone to misalignment. When entering this function, the agreement and plan serve as searchable basis sources, and the apprenticeship records serve as process evidence; together, the three support basis entries that point back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Basis entries that can point back to the original text" are completed by subsequent nodes continuing execution according to the branch. When triggered, the conversation enters an interactive 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 |
|---|---|---|
| User selection node | Whether each option corresponds to one branch connection | Check the options and branch connections one by one in the node, and verify whether nodeId is consistent with the branch direction |
| Interaction state record | Whether the state is recorded when entering the node | Trigger once, check the node state in the run record, and confirm that the process continues after the interaction is completed |
| Selection result variable | Whether it has been passed to subsequent nodes | Reference variables in subsequent nodes and run a trial once to confirm that the branch direction is consistent with the interaction state record |
| School-enterprise cooperation agreement | Whether the cooperation period, positions, number of people, date, and signature page match the order class training plan | Compare names, quantities, and dates in the agreement and plan one by one, and separately mark entries missing signatures or receipts |
Three common errors
- Phenomenon: The name, quantity, and date of the same master-apprentice record do not match between the agreement and the training plan. Cause: The three parties did not unify the standards during aggregation, and the old version was not synchronously replaced.
- Phenomenon: The version of the order class training plan is not synchronized, and the current version coexists with the archived version. Cause: Updates advance by semester, and the old version was not marked invalid.
- Phenomenon: The agreement or apprenticeship record lacks signatures or receipts. Cause: The signing process was not closed-loop, and receipts were not archived together with the materials.
How to verify the setup
This function's acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that nodeId and variables have the correct direction after being referenced in subsequent nodes.
Business test: ask a basis question spanning materials and see whether the answer provides a traceable source.
- Run trials for each option one by one, and check the branch direction and interaction state record in the run record.
- Reference
variablesin subsequent nodes, and confirm that the selection result variable has been passed and affects the branch.