What this category's data looks like
International student admissions and student status management involve three types of materials: admissions prospectuses, admission letters, and visa application forms. The sources are the admissions system, the academic affairs system, and visa material archiving, and the update cadence advances with batches and semesters. Prospectus fields include program name, program duration, application deadline, and signature field; admission letters include admission number, name, registration date, and issuer signature; visa application forms include passport number, name spelling, entry date, and receipt number. When materials enter workflow orchestration, the prospectus serves as the basis for the eligibility branch, the admission letter serves as the basis for the student status registration branch, and the visa application form serves as the basis for the entry and registration branch, each taking on a different branch determination role.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. The handover-ready deployment status and operation records are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the 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 | Whether the program name, program duration, application deadline, and signature field are consistent with the admission letter | Compare item by item the program name, program duration, and deadline in the prospectus and admission letter, and check whether the signature field is complete |
| Admission letter | Whether the admission number, name, registration date, and issuer signature are consistent with the visa application form | Check the options and branch connections one by one in the node, and check how the admission number and registration date are written in the two materials |
| Visa application form | Whether the passport number, name spelling, entry date, and receipt number are consistent with the admission letter | Check the passport number and name spelling, and check whether the receipt number and entry date are missing a signature or receipt |
| Workflow node | Whether the options and branches, interaction status, and selection result variables are recorded completely | Trigger once to view the node status in the run record, reference variables in subsequent nodes and do a trial run, and check the branch corresponding to nodeId |
Three common errors
- Symptom: The program name, program duration, and deadline for the same record do not match between the prospectus and the admission letter. Cause: The two materials are updated separately, versions are not synchronized, and field definitions are inconsistent.
- Symptom: The name spelling, passport number, and entry date do not match between the admission letter and the visa application form. Cause: The entry batches are different, and the receipt number is missing or has not been backfilled.
- 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 to subsequent nodes.
How to verify the setup
This feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that variables has been passed to subsequent nodes and that nodeId corresponds to the correct branch.
Business test: check item by item once according to the handover form, see which record is missing, and check whether the version, connection, and task record are consistent.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and do a trial run once, and check that the version, connection, and task record in the handover form are consistent.