What this category's data looks like
International student admissions and enrollment management involves three types of materials: international student admission brochures, admission letters, and visa application forms. Admission brochures contain majors, tuition, application deadlines, and signature fields; admission letters contain name, student ID, admitted major, registration date, and issuer's signature; visa application forms contain passport number, name spelling, entry date, and receipt. Materials come from the admissions office, departments, and visa affairs positions, updated by admission season and batch, with fields mainly consisting of names, dates, quantities, and signatures. When entering workflow orchestration, the admission brochure serves as the entry judgment basis, the admission letter serves as the enrollment identity basis, and the visa application form serves as the external service basis; after the user selection node, the three continue to flow according to branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" is completed by subsequent nodes continuing execution according to branches. When a 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 admission brochure | Major name, application deadline, and signature field are consistent across the three materials | Compare the fields of the brochure with the admission letter and visa application form item by item, and check the options and branch connections in the node |
| Admission letter | Name, student ID, and registration date match the brochure and visa application form | Use variables to reference the selection result variable, and run a trial in a subsequent node to see the branch direction |
| Visa application form | Passport number, name spelling, entry date, and receipt are complete | Trigger a user selection node once, and view the interaction state corresponding to nodeId in the run record |
| Externally available entry points and authorization scope | Visitor identity matches the visible scope; unauthorized content is not visible | Access once with a restricted identity, and check the branch direction and interaction state record |
Three common errors
- Symptom: The same student's name spelling or registration date does not match between the brochure and the admission letter. Cause: The two materials are entered separately by different positions, lacking cross-material field comparison and signature receipt verification.
- Symptom: The admission brochure has been updated, but the admission letter still references the old version's major name or deadline. Cause: Versions are not synchronized, and material versions and date fields are not validated when branch execution continues.
- Symptom: The visa application form lacks a signature or receipt, but the process still enters the external service branch. Cause: The user selection node does not use signature and receipt as branch judgment criteria, and the interaction state record does not cover material completeness.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting and unauthorized content is not visible.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection node once, view the node status and branch direction in the run record, and check whether the same session repeatedly enters the interaction.