What this category's data looks like
This category's data for international student admissions and enrollment management includes admissions brochures, admission letters, and visa application forms, sourced from the admissions system, the admission system, and visa material archives, with updates rolling according to batches and visa milestones. Field characteristics center on name, passport number, major, enrollment date, issue date, signature, and receipt. Admissions brochures enter the workflow as the source of admissions rules and the major catalog, admission letters serve as the basis for admission status and enrollment registration, and visa application forms serve as evidence for entry and enrollment changes. During exception tracing, the three types of materials serve as cross-references for one another; names, quantities, dates, and signatures must be aligned item by item, and the latest archived version prevails.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution along the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Admissions brochure | The major name, program duration, application deadline, and signature field must be consistent with the admission letter | Compare the name, date, and signature of the brochure and the admission letter item by item, and check whether the variables reference points to the same record |
| Admission letter | The admitted major, enrollment date, and receipt signature must be consistent with the visa application form | Check the options and branch connections one by one in the node, and confirm that the nodeId corresponds to the branch direction and interaction state record |
| Visa application form | The name, passport number, issue date, and signature must be consistent with the admission letter | Check whether the selection result variable has been passed to subsequent nodes, reference that variable in the subsequent node, and run a test once |
| Exception list | Each exception must be supported by the original record and accompanied by the reviewer's signature | Create an exception record and trace it back to the original fields and dates in the brochure, admission letter, or visa application form |
Three common errors
- Symptom: The major name, quantity, and date of the same record do not match between the brochure and the admission letter. Cause: The two materials are written by different nodes, and no field-level comparison was performed.
- Symptom: The admission letter version is not synchronized, and the old version is still referenced. Cause: After the archive was updated, the branch was not re-triggered, and the interaction state record did not cover the new version.
- Symptom: The visa application form lacks a signature or receipt, so the review conclusion cannot be signed. Cause: The signature field and receipt field were not validated when the material entered the workflow.
How to verify the setup
Acceptance of this feature: run a test for each option, check the branch direction and interaction state in the run record, and confirm that variables, nodeId, and the selection result variable are consistent.
Business test: create an exception record, see whether it can be traced back to the source material, and check the reviewer's signature and the responsible person's disposition outcome.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in the subsequent node and run a test once to confirm that the process continues execution after the interaction is completed.