What this category's data looks like
This category covers international student admissions and enrollment management, and its materials include three types: admission brochures, admission letters, and visa application forms. Admission brochures are updated by the admissions department each semester, and their fields include program name, application deadline, signature, and seal; admission letters are issued by the admissions committee in batches, and their fields include name, passport number, admitted program, issue date, and authorized signature; visa application forms are filled out by students and reviewed by the international student office, and their fields include name, date of birth, passport information, signature, and receipt. When the three types of materials enter the authorized access and external services function, their roles differ: the admission brochure is publicly visible entry material, the admission letter is admission credential visible to restricted identities, and the visa application form is process material requiring receipt and signature confirmation. The name, quantity, and date of the same record in the three materials must be consistent, versions must be synchronized, and signatures and receipts must not be missing.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Admission brochure | The program name, application deadline, and signature and seal in the brochure must be consistent with the corresponding records in the admission letter and visa application form, and versions must be synchronized | Access once with a restricted identity, check whether the brochure's visible scope matches the authorization settings, then compare the names, dates, and signatures across the three materials |
| Admission letter | The name, passport number, admitted program, and issue date in the letter must be consistent with the visa application form, and the authorized signature and receipt must not be missing | In the request preview, view the complete rendered address, check the source of the Authorization request header value, then compare the returned fields against a sample |
| Visa application form | The name, date of birth, and passport information in the form must be consistent with the admission letter, the signature and receipt must be complete, and unsynchronized versions must be flagged | In the variables panel, check the variables source of each placeholder, and confirm that the responseData returned fields are consistent with the external interface agreement |
Three common errors
- Symptom: The program name and date of the same record do not match between the admission brochure and the admission letter. Cause: Versions are not synchronized, and the two places maintain fields separately.
- Symptom: The visa application form lacks a signature or receipt, while the admission letter has already been issued. Cause: The review step did not return confirmation, and the materials were not closed-loop.
- Symptom: When accessed with a restricted identity, admission letter fields beyond the authorized scope are visible. Cause: The visible scope was not matched to the identity, and unauthorized access was not blocked.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; at the same time, check the Authorization request header, the variables source, and the responseData returned fields.
Business test: access once with a restricted identity and see whether the visible scope matches the settings
- In the request preview, view the complete rendered address, and check that the path parameter placeholder variables can be parsed into actual values
- In the variables panel, check the source of each placeholder, and confirm that the request body fields are consistent with the external interface agreement