What this category's data looks like
In international student admissions and enrollment management, the admissions prospectus, admission letter, and visa application form are three core types of materials: the admissions prospectus is issued by the admissions department per academic year, with fields including program name, duration of study, application deadline, fee items, and signature field; the admission letter is jointly issued by the department and the admissions office, with fields including student name, passport number, admitted program, registration date, issuer signature, and acknowledgment; the visa application form is filled out by the student and checked by the admissions office, with fields including name spelling, date of birth, passport validity, intended date of entry, and personal signature. The three types of materials have different update rhythms: the prospectus is replaced as a whole per academic year, admission letters are generated one by one per admission batch, and visa application forms enter on a rolling basis as students submit them. After the materials enter the workflow, the prospectus and admission letter assume the role of baseline comparison, while the visa application form assumes the role of the object to be verified; together, the three support discrepancy localization.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Admissions prospectus | The program name, duration of study, and application deadline in the prospectus must be consistent with the corresponding fields in the admission letter | Check the options and branch connections one by one in the node, compare the prospectus fields side by side with the admission letter fields, write inconsistent items into the branch direction record, and reference variables in subsequent nodes |
| Admission letter | The student name, passport number, admitted program, registration date, and issuer signature in the admission letter must be consistent with the corresponding fields in the visa application form | Trigger a user selection node once, check the node status in the run record, confirm that discrepancy items have been passed to subsequent nodes with the selection result variable, and check nodeId |
| Visa application form | The name spelling, date of birth, passport validity, intended date of entry, and personal signature in the application form must be consistent with the ledger record | Reference the selection result variable in a subsequent node and run a trial once, use one real record to find and mark fields inconsistent with the ledger, and record variables |
| Workflow node | Each option corresponds to one branch, and options and branch connections must correspond one by one | Check the options and branch connections, confirm that the process continues downward after the interaction is completed and does not fall into the default branch, and check nodeId |
Three common errors
- Symptom: The name spelling or date of birth of the same student does not match between the admission letter and the visa application form. Cause: The two materials are entered in different stages, lacking field-level comparison and discrepancy localization.
- Symptom: The admissions prospectus has been replaced per academic year, but the admission letter still references the old program name or duration of study. Cause: The versions are not synchronized, and version marking and comparison were not performed when the materials entered the workflow.
- Symptom: The admission letter lacks the issuer signature, and the visa application form lacks the personal signature or acknowledgment. Cause: Signatures and acknowledgments were not included in the verification checklist and were not intercepted before entering the interaction state.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the process continues downward after the interaction is completed, and check variables and nodeId.
Business test: use one real record to find fields inconsistent with the ledger, write the discrepancy items into the discrepancy list, submit them to the reviewer for confirmation, and write them back.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, trigger once to view the node status in the run record, and check
variablesandnodeId. - Reference the selection result variable in a subsequent node and run a trial once, confirm that the process continues downward after the interaction is completed, and submit the discrepancy list to the reviewer for confirmation and write-back.