What this category's data looks like
This page focuses on the category of primary and secondary school student status establishment and changes. The materials come from three types: student status archives, transfer applications, and suspension/resumption materials, including student basic information forms, transfer contact forms, suspension applications, and resumption certificates. The update cadence follows the change windows at the beginning and middle of the semester, and the field characteristics center on name, student status number, class, change date, handler signature, and receipt column. When materials enter the Q&A intake and missing-item follow-up function, student status archives serve as the baseline for identity and enrollment status, transfer applications serve as the basis for transfer-in/transfer-out direction and dates, and suspension/resumption materials serve as the basis for reason and duration. Together, the three support missing-item identification and follow-up questioning. If any material field is missing or a version is not synchronized, the follow-up chain must fall back to re-ask.
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). The intake record and the completed question items are then handled by subsequent AI nodes or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Student status archive | Fields include name, student status number, class, signature, and receipt; the date must match the transfer application | Open the tool node introduction fields, check the parameter introduction and whether each is required, and test-run with a question missing the student status number |
| Transfer application | If any of transfer-out/transfer-in direction, change date, handler signature, or receipt is missing, it is judged as a missing item | On the canvas, check the diamond interface connections and node status, and confirm whether toolChoice and functionCall are triggered according to the introduction |
| Suspension/resumption materials | The suspension reason, duration, resumption date, and signature receipt must be synchronized with the student status archive version | Check the material dates and signature columns item by item, and inspect whether the returned result contains values that do not exist in the materials |
| Tool calling node connections | The diamond interface is connected to the target tool, and the node status is readable | On the canvas, check the diamond connections and node status, and confirm the call records of toolChoice and functionCall |
Three common errors
- Symptom: The name or date of the same record does not match between the student status archive and the transfer application. Cause: The two material versions are not synchronized, and the baseline material was not checked again during follow-up.
- Symptom: Values that do not exist in the business materials appear in the returned result. Cause: When there are no required parameters, the model may fabricate parameter values on its own without asking first.
- Symptom: Suspension/resumption materials are still accepted when the signature or receipt is missing. Cause: Whether a field is required does not correspond to the material fields, and the model answers directly without calling the tool.
How to verify the setup
Acceptance for this function: test-run with a question missing required parameters, check the inputs and returns in the call record, confirm whether it asks a follow-up or calls according to the introduction, and inspect the trigger records of toolChoice and functionCall.
Business test: ask a question missing key information and see whether it asks a follow-up before answering.
- 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 each is required one by one.
- On the canvas, check the diamond connections and node status, test-run with a question missing that field, and confirm that it does not fabricate directly.