What this category's data looks like
This page focuses on progress records and statistical verification in modern apprenticeship and order class management, involving three types of materials: school-enterprise cooperation agreements, order class training plans, and master-apprentice records. Agreements are signed by both the school and the enterprise, training plans are jointly developed by the institution and the order class, and apprentice records are filled in weekly by the master. The update rhythm of materials is: agreements are updated by academic year or project cycle, training plans are revised as positions adjust, and apprentice records are submitted weekly. Field characteristics include student name, position name, apprenticeship date, signature field, and receipt status. When entering this function, the agreement and plan serve as the basis for definitions, and the apprentice records serve as progress details; together, the three support the generation of the progress table and statistical definition explanation.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the input parameters and return in the call record). The "progress table and statistical definition explanation" is then completed by subsequent AI nodes or manual verification.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Check whether the order class name, student list, cooperation start and end dates, and signatures/seals in the agreement are consistent with the training plan | Open the scanned agreement, compare item by item with the corresponding fields in the training plan, and mark inconsistencies in names, quantities, and dates |
| Order class training plan | Check whether the position names, course modules, and assessment methods in the plan match the positions and dates in the master-apprentice records | Extract one week of apprentice records, compare with the position list and date table in the plan, and check the version number and signature field |
| Master-apprentice record | Check whether the student name, apprenticeship date, work hours or task count, master signature, and receipt in the record are complete | Summarize the number of records by week, cross-check with the statistical table totals, and confirm entries missing signatures or receipts |
| Tool call node | Check the three configurations: tool introduction, parameter introduction, and whether it is required, and confirm that the model decides to call based on the introduction | On the canvas, check the diamond connectors and node status, run a test with a question missing a required parameter, and view the call record |
Three common errors
- Phenomenon: The same student's name or quantity does not match between the agreement and the training plan. Cause: The two materials were entered separately, without field-level synchronization verification.
- Phenomenon: The dates in the apprentice records are inconsistent with the weekly schedule in the training plan. Cause: The plan version was not updated synchronously, and records were filled in according to the old version.
- Phenomenon: Some apprentice records lack the master's signature or receipt. Cause: The signature field was not validated at submission, and they were directly included in the totals during statistics.
How to verify the setup
This function acceptance: Run a test with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; check the correspondence between toolChoice, functionCall, and the tool introduction fields.
Business test: Use one week of records to verify the totals, and see whether the definitions and exceptions are clearly stated.
- Open each parameter configuration one by one, check the parameter introduction and whether it is required, and ensure they correspond to fields that actually exist in the business materials.
- On the canvas, check the diamond connectors and node status, confirm that the tool call node is connected to the target tool, and check the configuration of
toolChoiceandfunctionCall.