What this category's data looks like
This page focuses on the self-taught examination registration records and graduation review category. The materials come from three types: registration records, course pass certificates, and graduation application forms. Registration records hold the candidate's basic information and enrollment status; course pass certificates carry individual subject scores and the time they were obtained; graduation application forms summarize credits and signed receipts. The update cadence advances by exam session and review batch, and the field characteristics are name, course name, quantity, date, signature field, and version number. When entering the tool call feature, registration records serve as the base ledger for identity and eligibility, course pass certificates serve as the source for quantity and date, and graduation application forms serve as the summary and signature carrier; the three respectively take on the roles of foundation, detail, and aggregation, for subsequent reconciliation of progress and statistical criteria.
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 input parameters and return in the call record). The "progress table and statistical criteria description" is then completed by a subsequent AI node or manual reconciliation.
| Object | Check | Verification action |
|---|---|---|
| Registration records | Fields, dates, and signatures must correspond item by item with the course pass certificates, and the name wording must be consistent | Open the registration records, check the name, enrollment status, date, and signature field, then compare with the pass certificates |
| Course pass certificates | The same course name, quantity, and date must be consistent across the two materials, and the version must be in sync | Check the course name, quantity, and date obtained on each course pass certificate one by one, and check the version number and receipt |
| Graduation application forms | The total credits must match the number of pass certificates, and signatures and receipts must be complete | Check the summary figures on the application form against the pass certificate details, and check for missing signatures or receipts |
| Tool call node | The input parameter fields must correspond to the real fields in the business materials; if required fields are missing, ask follow-up questions first | Test-run with a question that is missing required parameters, and inspect toolChoice, functionCall, and the call record |
Three common errors
- Symptom: the name or quantity of the same course does not match across the two materials. Cause: the criteria were not unified at entry, and versions were not synced, causing differences between the statistical total and the details.
- Symptom: the graduation application form is missing a signature or receipt, and the review cannot be closed. Cause: the signature field was not checked during material circulation, the receipt was not archived with the form, and the progress record has a breakpoint.
- Symptom: values appear in the returned result that do not exist in the business materials. Cause: when there are no required parameters, the model may fabricate parameter values on its own, and after multiple tools are chained, results cross-contaminate each other.
How to verify the setup
Acceptance for this feature: test-run with a question that is missing required parameters, check the input parameters and return in the call record, confirm whether it asks follow-up questions or calls according to the description, and check the toolChoice and functionCall records.
Business test: reconcile the totals using one week of records, see whether the criteria and exceptions are clearly written, and compare the names, quantities, dates, and signatures across registration records, course pass certificates, and graduation application forms.
- Open the tool node description fields, check whether the description can be understood when read on its own, and check the two items of parameter description and whether it is required.
- On the canvas, check the diamond connectors and node status, confirm that the tool call node is connected to the target tool, then test-run a question with a missing field.