What this category's data looks like
This page focuses on primary and secondary school student status establishment and changes. The materials come from student status archives, transfer applications, and suspension/resumption materials. These materials enter the workflow on a weekly basis, and the update rhythm is synchronized with the school's academic affairs arrangements. Field characteristics center on student name, ID number, student status number, change type, date, signature, and receipt. Student status archives serve as the base ledger, providing student identity and enrollment status; transfer applications serve as the basis for changes, providing transfer-in/transfer-out direction and time; suspension/resumption materials serve as evidence of status changes, providing suspension start/end and resumption confirmation. The three types of materials respectively assume the roles of base ledger verification, change triggering, and status write-back in the tool call node. The tool call results only record the input parameters and returns, and the progress table and statistical scope explanation are subsequently completed by AI nodes or manual verification.
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 results (input parameters and returns in the call record). The progress table and statistical scope explanation are subsequently completed by AI nodes or manual verification. The model determines whether to call the tool this time based on the tool introduction, parameter introduction, and whether parameters are required; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable values in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Student status archives | Whether fields, dates, and signatures are consistent with the transfer application | Open the tool node introduction fields and check whether the purpose, when to use, and what is returned can be understood; then check the parameter introduction and whether each is required item by item |
| Transfer application | Whether the name, quantity, and date of the same record match in the two materials | Run a test with a question missing a required field to see whether it asks first; check the input parameters and returns in the call record to confirm there are no values that do not exist in the business materials |
| Suspension/resumption materials | Whether versions are synchronized and whether missing signatures or receipts are clearly stated | Check the diamond connectors and node status on the canvas, and check whether the tool call node connector is connected to the target tool |
| Statistical scope explanation | Whether the record count and statistical count match, and whether the scope is written in the header | Use one week of records to check the total, and check whether the scope and exceptions are clearly stated; when reference limits are involved, check the tokens of the referenced text, and record the number of array items separately |
Three common errors
- Phenomenon: The name or date of the same student does not match between the student status archive and the transfer application. Cause: The two materials were entered at different times, and the fields were not checked for consistency.
- Phenomenon: The version of the suspension/resumption materials is not synchronized, and the old version is still being called. Cause: After the materials were updated, the reference in the node was not replaced, and the tool call results are still returned according to the old version.
- Phenomenon: The transfer application is missing a signature or receipt, but the tool is still called according to the introduction. Cause: The parameter is not marked as required, and the model directly executes according to the introduction without asking first.
How to verify the setup
Acceptance of this feature: Run a test with a question missing a required parameter, check the input parameters and returns in the call record, and confirm whether it asks first or calls according to the introduction; at the same time, check the actual values of toolChoice, functionCall, and toolChoice in the call record.
Business test: Use one week of records to check the total, and see whether the scope and exceptions are clearly stated.
- Open each parameter configuration one by one, check the introduction and whether it is required, and confirm that they correspond to fields that actually exist in the business materials.
- Check the diamond connectors and node status on the canvas, and confirm that the tool call node connector is connected to the target tool.