What this category's data looks like
Materials for material verification and discrepancy localization in self-funded study abroad application services come from three types: study abroad service contracts, school application forms, and personal statements. The contract is signed by the service provider and the applicant and then archived, containing the scope of services, fee terms, signatures of both parties, and the signing date; the application form is generated or exported by the school system, containing name, date of birth, application program, intake season, and submission receipt; the personal statement is written by the applicant and reviewed by the service provider, containing version number, word count, submission time, and a signature confirmation page. The three types of materials update at different rhythms: the contract changes at signing and with supplementary agreements, the application form is resubmitted with school rounds and program adjustments, and the personal statement iterates by revision rounds. When the materials enter workflow orchestration, the contract assumes the role of the signing and terms baseline, the application form assumes the role of the identity and program field baseline, and the personal statement assumes the role of the text version and submission receipt, with the three using the same application object as the anchor for field alignment and discrepancy localization.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction state records. When the user selection node is triggered, the conversation enters the interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the selected option. The discrepancy list is then completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Study abroad service contract | Fields, dates, and signatures: whether the applicant name, number of service items, signing date, and signature page in the contract are consistent with the ledger | Compare the contract and the ledger field by field, mark discrepancies in name, quantity, date, and signature, and record the discrepancy location and material page number |
| School application form | Fields, dates, and signatures: whether the name, date of birth, application program, and submission receipt in the application form are consistent with the contract and the ledger | Check the application form fields against the contract and the ledger, check whether the submission receipt exists, and write inconsistent fields into the discrepancy list with the source noted |
| Personal statement | Fields, dates, and signatures: whether the version number, submission time, and signature confirmation page of the personal statement are consistent with the ledger and the application form | Compare the personal statement version with the ledger records, check the signature and receipt, locate items whose versions are not synchronized or that are missing, and write them into the discrepancy list |
| Workflow node (user selection and branching) | Options and branches, interaction state, selection result variable: each option corresponds to one branch, the state is recorded when the node is entered, and the selection result variable has been passed to subsequent nodes | In the node, check the options and branch connections one by one, trigger it once to view the node state in the run records, reference variables in a subsequent node and run a trial, and check the branch direction corresponding to nodeId |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the contract and the application form. Cause: the two materials are entered separately and no field-level alignment is performed, so the discrepancy is not located.
- Symptom: the personal statement version is not synchronized, and the ledger record is inconsistent with the text version number. Cause: revision rounds are not written back to the ledger, and the version update lacks a synchronization action.
- Symptom: the application form lacks a signature or receipt, and the contract signature page is missing. Cause: signature and receipt fields are not checked when materials are archived, and missing items are not marked.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, and check whether variables is passed to subsequent nodes and whether the branch corresponding to nodeId is correct.
Business test: use one real record to find fields inconsistent with the ledger, covering the name, quantity, date, and signature items of the study abroad service contract, school application form, and personal statement.
- Compare the study abroad service contract, school application form, and personal statement with the ledger, check the name, quantity, date, and signature field by field, and write inconsistent items into the discrepancy list with the material source and page number noted.
- In the user selection node, check the options and branch connections one by one, trigger it once to view the node state in the run records, reference
variablesin a subsequent node and run a trial, and confirm the branch direction corresponding tonodeIdand the interaction state records.