What this category's data looks like
International student admissions and enrollment management involves three types of materials: admission brochures, admission letters, and visa application forms, which come from the admissions office, the academic affairs system, and the visa service window, respectively. They are updated by academic year and batch, and their fields include name, student ID, nationality, admission date, visa number, signature, and receipt. Admission brochures provide the basis for majors and quotas, admission letters provide admission and registration status, and visa application forms provide visa progress and receipts. When these three types of materials enter workflow orchestration, each plays a different role: admission brochures serve as the source of statistical criteria, admission letters serve as the basis for enrollment records, and visa application forms serve as the source of visa progress and exception markers. In terms of field characteristics, the same record often shows cross-material discrepancies in name, quantity, and date. Unsynchronized versions or missing signatures will directly affect the verification results of the progress table and the statistical criteria description.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statistical criteria description" is 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 status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Admission brochure | Whether the name, quantity, and date are consistent with the admission letter, whether the versions are synchronized, and whether signatures or receipts are complete | Compare the name, quantity, and date of the two materials one by one, verify the version number of the admission brochure and the receipt signature of the admission letter, and record discrepancies in the progress table |
| Admission letter | Whether the enrollment record and the visa application form match in name, student ID, and admission date, and whether missing signatures or receipts are marked | Check the options and branch connections one by one in the node, reference variables and nodeId for a trial run, and verify the branch direction and interaction status in the run record |
| Visa application form | Whether the visa number and date are consistent with the admission letter, and whether unsynchronized versions or missing receipts are written into the criteria exceptions | Trigger an interactive state once, check the node status in the run record, verify that the selection result variable has been passed to subsequent nodes, and run a trial once |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the admission brochure and the admission letter. Cause: The versions of the two materials are not synchronized, and the field criteria are not clearly stated in the header.
- Symptom: The visa application form lacks a signature or receipt, but the progress table still includes it in the total. Cause: Exceptions are not marked, and the statistical criteria do not list missing signatures or receipts separately.
- 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 are not checked one by one, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, check the branch direction and interaction status in the run record, and confirm that variables and nodeId are validly referenced in subsequent nodes.
Business test: use one week of records to verify the total, check whether the criteria and exceptions are clearly stated, and confirm that the number of records matches the statistical count and that the criteria are written in the header.
- 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 run a trial once, and check the case where the same session re-enters the interaction.