What this category's data looks like
Materials for this category are mainly study abroad service contracts, school application forms, and personal statements. They come from the service provider and the applicant after both parties sign or fill them out and submit them, and the update cadence advances with application rounds, institution batches, and visa milestones. The study abroad service contract carries the scope of services, fees, and signatures of both parties; the school application form carries the institution, major, intake season, and submission date; the personal statement carries the applicant's experience, motivation, and signature. When the three types of materials enter the form input node, each plays a field-source role: the contract provides the entity name and signing date, the application form provides the institution and major names, number of applications, and deadline, and the personal statement provides the version number and finalization date. The field characteristics are that name, quantity, date, and signature information appear interleaved, and the same record is prone to discrepancies across different materials, requiring field-by-field comparison; for missing items, ask follow-up questions first before answering.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). "Intake records and items to be completed" are handled 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 |
|---|---|---|
| Study abroad service contract | Whether the contract fields, dates, and signatures are complete, and whether the entity name matches the application form | Check the field names one by one in the node configuration, reference the fields with formInputResult, and run a test |
| School application form | Whether the institution, major, intake season, number of applications, and submission date match the contract | Check the required settings one by one, select the institution field with userSelect, and submit to verify |
| Personal statement | Whether the version number, finalization date, and signature match the application form submission date | Reference this field in a subsequent node and run a test, checking for unsynchronized versions and missing signatures |
| Intake records and items to be completed | Whether missing items are identified and followed up on, and whether answers are based on materials | Ask a question missing key information and see whether it asks follow-up questions first before answering |
Three common errors
- Symptom: The institution name and number of applications for the same application record do not match between the contract and the application form. Cause: The two materials are filled in separately, without field-by-field comparison and receipt confirmation.
- Symptom: The personal statement version is not synchronized, and the finalization date is later than the application form submission date. Cause: After the version was updated, it was not sent back to the intake record, and the field value is still the old version.
- Symptom: The contract lacks a signature or receipt, and key material fields are empty yet submission is still possible. Cause: The required markers do not cover the signature and receipt fields, and the interaction state does not intercept it.
How to verify the setup
Fill it out once and submit, check the field values obtained by subsequent nodes, and confirm that the field values referenced by formInputResult and selectResult can be retrieved.
Business test: Ask a question missing key information and see whether it asks follow-up questions first before answering.
- Check the field names and required markers one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference this field in a subsequent node and run a test to confirm that after submission the field is passed successfully and the conversation does not remain in the interaction state.