What this category's data looks like
In international student admissions and enrollment management, the three main documents are the admissions brochure, the admission letter, and the visa application form. The admissions brochure comes from the school's admissions department and is updated by admissions season; its fields include program name, program duration, tuition currency and amount, application deadline, and signature field. The admission letter is generated by the admissions system and is updated by admission batch; its fields include the student's name spelling, passport number, admitted program, registration date, issuer signature, and receipt. The visa application form is filled in by the student and sent back, and is updated by batch; its fields include name, date of birth, passport number, entry date, signature, and date. When these three documents enter material verification and discrepancy location, the admissions brochure serves as the baseline version, the admission letter serves as the school's confirmation document, and the visa application form serves as the student's receipt document. The same record must be compared across the three for names, quantities, dates, and signatures.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), and outputs the tool call result (the input parameters and return in the call record). The "discrepancy list" is then completed by a subsequent AI node or manual verification. The model judges whether to call the tool this time based on the tool description, parameter description, and whether the parameter is required. When there are no required parameters, the model may fabricate parameter values on its own; when there are required parameters but no suitable value in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Admissions brochure | Whether fields, dates, and signatures are consistent with the admission letter and visa application form | Compare field by field the program name, program duration, tuition currency and amount, and deadline; check the signature field; use functionCall to record the call input parameters |
| Admission letter | Whether the names, quantities, and dates of the same record match across the two documents | Compare name spelling, passport number, admitted program, and registration date; check the issuer signature and receipt; use toolChoice to record the call return |
| Visa application form | Whether the version is synchronized, and whether signature or receipt is missing | Compare name, date of birth, passport number, entry date, and signature date; check the version number and receipt; use functionCall to record the call input parameters |
| Tool call node | Whether it asks follow-up questions first when a required parameter field is missing, instead of directly fabricating | Open the tool description and parameter description, and check the two items of whether it is required; check the diamond interface connection and node status on the canvas |
Three common errors
- Symptom: The program name and tuition quantity of the same record do not match between the admissions brochure and the admission letter. Cause: The versions of the two documents are not synchronized, and the admission letter was not written back after the admissions season update.
- Symptom: The visa application form lacks the student's signature or receipt date, and conflicts with the registration date on the admission letter. Cause: The student's returned document was not updated by batch, and the signature field and date field were left blank.
- Symptom: Values that do not exist in the business materials appear in the returned result, or the model gives an answer directly without calling the tool. Cause: The parameter description does not clearly state the meaning and values, and required items are not guided by prompts.
How to verify the setup
Acceptance for this feature: run a test with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the description; check whether toolChoice, functionCall, and the three items of tool description, parameter description, and whether it is required correspond.
Business test: use a real record to find fields inconsistent with the ledger, compare the three documents of admissions brochure, admission letter, and visa application form field by field, and record discrepancies in names, quantities, dates, and signatures.
- Open the description field in the tool node, check whether this description can be understood when read on its own, and verify that the diamond interface is connected to the target tool.
- Open the parameter configuration one by one, check the two items of description and whether it is required, and run a test with a question missing that field to see whether it asks a follow-up question first instead of directly fabricating.