What this category's data looks like
This category's data looks like this: Modern apprenticeship and order class management involves three types of core materials: school-enterprise cooperation agreements, order class training plans, and master apprenticeship records. School-enterprise cooperation agreements are signed jointly by the school and the enterprise, with an update cadence keyed to the academic year or cooperation cycle, and fields include the cooperation entity name, agreement term, signatures and receipts; order class training plans are maintained by the teaching management department per semester, with fields including class name, enrollment quantity, course start date, course modules and approval signature; master apprenticeship records are reported by the mentoring master weekly or monthly, with fields including apprentice name, number of apprentices, apprenticeship start and end dates and master signature. When the three types of materials enter workflow orchestration, their roles differ: the cooperation agreement serves as the top-level basis, the training plan serves as the execution framework, and the apprenticeship records serve as process evidence. Material sources are scattered and versions iterate frequently, and fields are most prone to cross-material discrepancies in four places: name, quantity, date, and signature, requiring field-by-field comparison on the same object to locate inconsistencies between the ledger and the materials.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "discrepancy list" is 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 state; after the user completes the selection, execution continues along the branch corresponding to the chosen option, and subsequent nodes reference the selection result variable to continue processing.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Name, date, signature and receipt are consistent between the agreement and the ledger | Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and compare the agreement name, signing date and signature receipt |
| Order class training plan | Class name, enrollment quantity, course start date and approval signature are consistent between the two materials | Reference the selection result variable in a subsequent node and do a trial run, and check the name, quantity and date fields of the plan and the ledger |
| Master apprenticeship record | Apprentice name, number of apprentices, apprenticeship start and end dates and master signature are consistent between the record and the ledger | Locate the record node by nodeId, compare the number of apprentices and the start and end dates one by one, and check whether the master signature is complete |
| Workflow node | Each option corresponds to one branch, and the interaction state is recorded | Check the options and branch connections one by one in the node, trigger once to view the node status in the run record |
Three common errors
- Symptom: The name and quantity of the same record do not match between the agreement and the ledger. Cause: The two materials are maintained separately, without field-level comparison and write-back.
- Symptom: The training plan version is not synchronized, and the course start date and course modules still use the old version. Cause: The update cadences are inconsistent, and version identifiers and synchronization nodes are lacking.
- Symptom: The apprenticeship record lacks the master signature or receipt, and the discrepancy list cannot be closed. Cause: The material circulation step does not enforce validation of the signature field.
How to verify the setup
Acceptance of this feature: run a trial for each option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and do a trial run referencing variables and nodeId in a subsequent node.
Business test: use one real record to find fields inconsistent with the ledger, locate name, quantity, date or signature discrepancies and write them into the discrepancy list.
- Compare name, quantity, date and signature field by field across the school-enterprise cooperation agreement, order class training plan, and master apprenticeship record, and mark inconsistent items
- Trigger the user selection node once, view the node status and branch direction in the run record, and confirm that the selection result variable has been passed to subsequent nodes