What this category's data looks like
For the pre-departure training and overseas safety reminders category, the core materials include pre-departure training courseware, safety reminder checklists, and accommodation contact lists. Courseware is updated by semester batch and contains course modules, dates, and instructor signature fields; safety reminder checklists are maintained by destination country and city and contain item names, quantities, effective dates, and receipt fields; accommodation contact lists are iterated by host version and contain contacts, room quantities, check-in dates, and confirmation signatures. When these three types of materials enter this feature, the courseware and checklists serve as the sources to be verified, and the contact list serves as the comparison baseline or another source; the tool calling node reads the fields and returns the call record, for subsequent nodes or manual personnel to localize discrepancies.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the inputs and returns in the call record). The "discrepancy list" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the name, quantity, date, and signature are consistent between the courseware and the ledger | Open the courseware node introduction and parameter introduction, check whether the date and signature fields are required, run a trial with a question missing the date and view the call record, and confirm the values of toolChoice and functionCall |
| Safety reminder checklist | Whether the item names, quantities, effective dates, and receipts match between the two materials | Check one by one whether the parameters are required, check whether the returned inputs contain values outside the checklist, record the discrepancy fields, and check the functionCall return status |
| Accommodation contact list | Whether the contacts, room quantities, check-in dates, and confirmation signatures are consistent with another source | On the canvas, check the diamond interface connections and node status, and confirm that the tool calling node is connected to the target tool with status indexed |
| Tool calling node connections | Whether the diamond interface is connected to the target tool and the node status is normal | View the canvas connections and confirm that the configurations related to toolChoice and functionCall are traceable in the call record |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the ledger. Cause: The two materials are maintained separately, and the fields have not been compared item by item.
- Symptom: The safety reminder checklist version is not synchronized, and old items are still referenced. Cause: The update cadence differs, and version verification actions are lacking.
- Symptom: The accommodation contact list lacks a signature or receipt but still enters the verification step. Cause: The signature field is not set as required, and the model calls without asking follow-up questions.
How to verify the setup
Feature acceptance: Run a trial with a question missing required parameters, check the inputs and returns in the call record, confirm whether it asks follow-up questions or calls according to the introduction, and view how toolChoice and functionCall are reflected in the record.
Business test: Use a real record to find fields inconsistent with the ledger, record the name, quantity, or date discrepancies, submit them to the reviewer for confirmation, and write them back.
- Open the tool node introduction fields, check whether the description can be understood when taken out on its own, and check the parameter introduction and whether it is required.
- On the canvas, check the diamond connections and node status, run a trial with a question missing a field, and confirm that it asks follow-up questions first rather than directly fabricating.