What this category's data looks like
In the vocational training subsidy application scenario, the materials entering the Q&A intake and missing-item follow-up stage are mainly of three types: training class filing, sign-in records, and completion assessment forms. Class filing comes from training institution declarations and contains fields such as class name, start and end dates, courses, and instructors; sign-in records are generated daily and contain trainee name, sign-in date, signature field, and receipt; completion assessment forms are summarized after the assessment ends and contain assessment date, score, and assessor signature. The three types of materials update at different rhythms: filing is submitted before the class starts, sign-in records are appended day by day, and assessment forms are filled in all at once after completion, so versions are easily misaligned. When entering this feature, filing is used to confirm the class and time scope, sign-in records are used to check personnel attendance and signature completeness, and assessment forms are used to check completion conclusions and assessor signatures. Field characteristics are concentrated in four categories: name, quantity, date, and signature. When comparing across materials, the most common issues are inconsistent spellings of the same record name, mismatched headcounts, and contradictory dates.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the inputs and returns in the call record). "Intake records and completed question items" are then handled by subsequent AI nodes or manual verification. The model decides whether to call based on the tool description, parameter descriptions, and whether parameters are required; toolChoice and functionCall determine the calling method for this instance.
| Object | Check | Verification action |
|---|---|---|
| Training class filing | Check the class name, start and end dates, and course fields, and confirm consistency with the scope of the sign-in records and completion assessment forms | Open the tool node description fields and confirm that the purpose and returned results are readable; run a test with a question missing the class name to see whether it asks a follow-up first |
| Sign-in records | Check trainee name, sign-in date, signature field, and receipt, and confirm that there are no missing signatures after daily appending | Open each parameter configuration one by one, check the parameter description and whether it is required; confirm that required fields correspond to fields that actually exist in the sign-in materials |
| Completion assessment forms | Check the assessment date, score, and assessor signature, and confirm that the date chain does not conflict with the filing and sign-in records | Check the diamond-shaped interface connections and node status on the canvas, and confirm that the tool calling node is connected to the target tool |
| Call records | Check whether the inputs and returns contain values that do not exist in the business materials | Run a test with a question missing a required field, check the inputs and returns in the call record, and confirm whether it asks a follow-up or calls according to the description |
Three common errors
- Phenomenon: the same class has inconsistent name spellings in the filing and sign-in records. Cause: the two materials are filled in by different stages, and field scope alignment was not performed.
- Phenomenon: the headcount in the sign-in records does not match the headcount in the completion assessment forms. Cause: sign-ins are appended day by day, while assessment forms are filled in all at once after completion, and versions were not synchronized.
- Phenomenon: dates or signatures that do not exist in the materials appear in the returned results. Cause: when there are no required parameters, the model may fabricate parameter values on its own without asking a follow-up first.
How to verify the setup
Acceptance for this feature: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up or calls according to the description; also check toolChoice, functionCall, and the connection status of the tool calling node.
Business test: submit a question missing key information and see whether it asks a follow-up before answering, rather than directly giving an intake conclusion.
- Open the tool node description fields, check whether this description can be understood when read on its own, and confirm that the returned results correspond to the business material fields.
- Open each parameter configuration one by one, check the two items of parameter description and whether it is required, and run a test with a question missing that field to see whether it asks a follow-up first.