What this category's data looks like
This page focuses on grade entry and credit recognition, handling three types of materials: transcripts, deferred examination applications, and makeup examination arrangements. Transcripts are exported from the academic affairs system or submitted by teachers, and contain course name, credits, grade, entry date, and a signature field; deferred examination applications are submitted by students, and contain the course, original examination date, reason for deferral, and approval signature; makeup examination arrangements are published by departments, and contain the makeup examination course, time, location, and receipt. The update rhythm is: transcripts are summarized weekly, deferred examination applications are entered as they are submitted, and makeup examination arrangements are published in batches. When the three types of materials enter the tool call node, each has a different role: the transcript is the main record, the deferred examination application is the source of exceptions, and the makeup examination arrangement is the basis for subsequent actions. In terms of field characteristics, the name, quantity, and date of the same course may be inconsistent across the three materials, versions may not be synchronized, or signatures or receipts may be missing, so the statistical scope statement must clearly state which one prevails.
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 inputs and returns in the call record). The "progress table and statistical scope statement" is then completed by a subsequent AI node or manual reconciliation. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to call the tool this time; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable value in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Whether the fields, dates, and signature match the deferred examination application and makeup examination arrangement | Open the tool node description fields and check the course name, credits, grade, entry date, and signature field; run a test with a question missing a required parameter to see whether it asks first |
| Deferred examination application | Whether the name, quantity, and date of the same record are consistent across the two materials | Open each parameter configuration one by one and check the description and whether it is required; check whether the reason for deferral, original examination date, and approval signature correspond to the transcript |
| Makeup examination arrangement | Whether the version is synchronized and whether the signature or receipt is missing | Check the diamond connectors and node status on the canvas, and confirm that the makeup examination course, time, location, and receipt are consistent with the scope of the transcript and deferred examination application |
| Tool call node | Whether the description, parameter descriptions, and whether required can support the model's judgment | Check the inputs and returns of toolChoice and functionCall in the call record, and confirm that there are no values that do not exist in the business materials |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match between the transcript and the deferred examination application. Cause: The two materials are entered separately, no field-level reconciliation is done, and the statistical scope is not written into the header.
- Symptom: The version of the makeup examination arrangement is not synchronized, and the old version is still referenced. Cause: The tool call node does not call again based on the latest material, and an old date appears in the returned result.
- Symptom: The deferred examination application lacks a signature or receipt but still enters the statistics. Cause: The whether-required parameter does not correspond to the business material field, and the model calls directly without asking first.
How to verify the setup
Feature acceptance: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks first or calls according to the description; at the same time, check toolChoice, functionCall, and the diamond connector status.
Business test: reconcile the totals using one week of records, and see whether the scope and exceptions are clearly stated; compare the record counts and statistical counts of the transcript, deferred examination application, and makeup examination arrangement item by item, and write the scope into the header.
- Open the tool node description fields, check whether this description can be understood when taken out on its own, and check the parameter descriptions and whether-required items.
- Run a test with a question missing that field to see whether it asks first; then check the diamond interface and node status on the canvas to confirm that no value was directly fabricated.