What this category's data looks like
International student admissions and enrollment management involves materials such as international student admission brochures, admission letters, and visa application forms. The sources are the admissions office and the enrollment management department, updated with admission batches and visa policies. The admission brochure contains majors, program duration, fees, and application deadlines; the admission letter contains name, student ID, admitted major, registration date, and signature; the visa application form contains passport number, entry date, study duration, and receipt. When the materials enter the forms and interactions feature, the admission brochure fields are used to open the application entry point, the admission letter fields are used to confirm admission and registration, and the visa application form fields are used for authorized access and external services. The fields, dates, and signatures of the three must be consistent, versions synchronized; missing signatures or receipts will affect subsequent node processing.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, outputting the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry point and authorization scope are completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters the interaction state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| International student admission brochure | Fields, dates, and signatures must be consistent with the admission letter, versions synchronized | Check field names one by one in the node configuration, verify required markers and field passing after submission |
| Admission letter | Name, quantity, and date match the visa application form; missing signature or receipt cannot be released | Reference this field in subsequent nodes and test run, verify formInputResult and selectResult values |
| Visa application form | Passport number, entry date, and study duration are consistent with the admission letter, receipt complete | Access once with a restricted identity, verify the visible scope matches the authorization scope |
| Form input node | Required items cannot be submitted when empty, conversation does not get stuck in the interaction state | Check required settings one by one, after submission check whether subsequent nodes can obtain the corresponding field values |
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: Versions not synchronized, fields not checked item by item.
- Symptom: The visa application form lacks a signature or receipt but is still processed by subsequent nodes. Cause: Required markers not set or not validated after submission.
- Symptom: After submission, subsequent nodes cannot obtain values, and the conversation stays in the interaction state. Cause: Field passing was not referenced and test run in subsequent nodes.
How to verify the setup
Feature acceptance: Fill out once and submit, check the field values obtained by subsequent nodes, confirm that formInputResult and selectResult can obtain the corresponding fields.
Business test: Access once with a restricted identity, see whether the visible scope matches the settings; unauthorized access is not visible, open to parents or superiors.
- Check field names and required markers one by one in the node configuration, ensuring key material fields are marked as required.
- Reference this field in subsequent nodes and test run, verify field passing and authorization scope after submission.