What this category's data looks like
International student admissions and enrollment management involves three core types of materials: the international student admissions prospectus, the admission letter, and the visa application form. The admissions prospectus originates from admissions policies and the program catalog and is updated by academic year; the admission letter is generated from admissions results and is issued by batch; the visa application form is filled in based on admission information and passport details and changes with visa policy. The three types of materials share fields such as student name, nationality, program, length of study, registration date, signature, and receipt. When entering workflow orchestration, the admissions prospectus serves as the qualification basis, the admission letter serves as the admission credential, and the visa application form serves as the entry application document; each plays a different role, but the name, quantity, and date of the same record must remain consistent, versions must be synchronized, and signatures and receipts must be complete.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. Draft materials that can be issued and handover records are completed by subsequent nodes continuing execution according to the branch. 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 selected option.
| Object | Check | Verification action |
|---|---|---|
| International student admissions prospectus | Fields are complete, the responsible person is clear, and the version and date are consistent | Verify the student name, nationality, program, length of study, registration date, signature, and receipt; check the options and branch connections one by one in the node, and check whether variables are passed to subsequent nodes |
| Admission letter | The name, quantity, and date of the same record do not match across the two materials | Compare the admissions prospectus with the visa application form, and verify the admission batch, program name, and registration date; view the node status and branch direction corresponding to nodeId in the run record |
| Visa application form | The version is not synchronized, or the signature or receipt is missing | Verify the version number of the visa application form against the date of the admission letter, and check the signature and receipt; reference the selection result variable in a subsequent node and run a test once |
| Handover record | The responsible person is clear, and the version and date are consistent | Verify the signatures and receipts of both parties in the handover, check whether the selection result in variables is passed to the handover node, and trigger a run to view the run record |
Three common errors
- Symptom: The name, program name, or registration date of the same student does not match between the admissions prospectus and the admission letter. Cause: The fields come from different sources and no consistency check was performed, and the versions were not synchronized.
- Symptom: The version number of the visa application form is inconsistent with the date of the admission letter, causing the materials to be returned. Cause: After the version was updated, it was not synchronized to the related materials, and the signature or receipt is missing.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed correctly.
How to verify the setup
This feature acceptance: run tests for each option one by one, verify the branch direction and interaction state in the run record, and confirm that variables, nodeId, and the selection result variable are passed correctly.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and trigger a run to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a test once to confirm that the branch direction and interaction state records are complete.