What this category's data looks like
In international student admissions and enrollment management, the admissions prospectus, admission letter, and visa application form constitute a chain of materials that must be issued. The admissions prospectus first defines the major, program duration, fees, and application deadline; the admission letter then carries the student's name, passport number, admitted major, registration date, and signature field; the visa application form then restates the name, passport number, entry date, and program name. The three materials come from different sources and have different update rhythms: the prospectus is revised by academic year, the letter is generated individually by admission batch, and the visa form is adjusted according to embassy and consulate requirements. Field characteristics center on name spelling, passport number, major name, dates, and signature receipt. When the materials enter the forms and interaction stage, each plays a different role: the prospectus provides the field template and version baseline, the admission letter handles item-by-item verification and issuance, and the visa application form handles consistency review with the former.
Configuration and implementation checks
| Object | Check | Verification action |
|---|---|---|
| Admission Brochure | Fields must cover program name, duration of study, fees, application deadline, and version date, and must match the corresponding items in the admission letter | Check field names one by one in the node configuration, confirm that the brochure fields correspond one-to-one with the admission letter fields, use formInput for a test entry, and check the values retrieved by subsequent nodes |
| Admission Letter | Student name, passport number, admitted program, registration date, and signature field must all be complete; if the signature or receipt is missing, it must not proceed to the next step | Check the required settings one by one, confirm that the signature and receipt fields are marked as required, and after submission check whether subsequent nodes can retrieve the corresponding field values |
| Visa Application Form | Name spelling, passport number, entry date, and project name must be aligned item by item with the admission letter, and the version date must not be earlier than the admission letter | Reference the formInputResult and selectResult fields in subsequent nodes and run a test, checking whether the name, quantity, and date of the same record match across the two documents |
| Handover Record | Responsible person, handover date, version number, and receipt status must be clear; if the version is not synchronized, it must not be signed for | Check whether the handover record fields are complete, confirm that the responsible person is clear and the version and date are consistent, then pass it to the next step for signing |
Three common errors
- Symptom: The major name and program duration quantity for the same student do not match between the prospectus and the admission letter. Cause: The two materials maintain their fields separately, and during drafting they were not checked item by item against the same template.
- Symptom: The admission letter has been updated to a new version, but the visa application form still uses the old version's date and program name. Cause: The version was not synchronized, and the version number and date were not checked during handover.
- Symptom: The admission letter is missing a signature or receipt but is still advanced to the next step. Cause: The signature and receipt fields were not marked as required, so the missing items were not blocked.
How to verify the setup
Acceptance for this feature: fill in once and submit, check the field values retrieved by subsequent nodes, confirm that the formInputResult and selectResult field values can be passed correctly, and that submission is impossible when required items are empty
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked
- Check the field names and required markers one by one in the node configuration, and confirm that the key material fields are marked as required
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a test, confirming that the corresponding field values can be retrieved after submission