What this category's data looks like
Materials for self-funded study abroad application services usually include three types: study abroad service contracts, school application forms, and personal statements. The contract is signed by the service provider and the family, and contains the scope of services, fees, and refund terms; the school application form is filled out by the applicant, and contains personal information, educational history, and the intended program of application; the personal statement is the applicant's own narrative text. When these three types of materials enter the form input node, each plays a different role: the contract provides the basis for authorization and signing, the application form provides the source of structured fields, and the personal statement provides supplementary explanation. The materials are submitted separately by the service provider and the applicant, and the update cadence changes with the application batch and signing progress. Field characteristics are concentrated in name, ID number, school name, major name, date, and signature fields; the same record must keep names, quantities, and dates consistent across multiple materials.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry points and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Study abroad service contract | The signing date and signature field are complete, and the scope of services corresponds to the application batch | Check the field names one by one in the node configuration, and confirm that the contract number, signing date, signature field, and required settings are consistent |
| School application form | Name, ID number, school name, and major name are consistent with the contract record | Reference this field in a subsequent node and run a test to check whether the application form field values can be retrieved |
| Personal statement | The version is synchronized with the application batch, with no missing signature or receipt | Check the field names one by one in the node configuration, and confirm that the personal statement version marker and submission receipt field have been marked as required |
| Form fields | Correspond one-to-one with the material fields to be collected | Use formInputResult and selectResult to check the field names, reference them in a subsequent node, and run a test |
Three common errors
- Symptom: The school name and major name for the same record do not match between the contract and the application form. Cause: The two materials are filled out by different people, and no field-level comparison or receipt confirmation was done.
- Symptom: The personal statement version is not synchronized, and the old draft is still referenced after submission. Cause: The version marker was not updated with the application batch, and the signature or receipt field is missing.
- Symptom: After submission, subsequent nodes cannot retrieve the values, or required items can be submitted even when empty. Cause: Required markers were not checked one by one, and field passing was not verified by running a test in subsequent nodes.
How to verify the setup
Acceptance for this feature: fill out and submit once, check the field values retrieved by subsequent nodes, and confirm that both the formInput output and the userSelect selection result can be passed.
Business test: access once with a restricted identity, and see whether the visible scope matches the settings and unauthorized content is not visible.
- Check the field names and required settings one by one in the node configuration, and confirm that key material fields have been marked as required
- Reference this field in a subsequent node and run a test to confirm that the corresponding field value can be retrieved after submission