What this category's data looks like
The Q&A intake for general college entrance examination registration qualification review revolves around three types of materials: the registration form, household registration and student status proof, and materials for children accompanying migrating parents. The registration form contains the candidate's basic information, examination category, and signature field; the household registration and student status proof contains the household registration address, student status number, and school seal; the materials for children accompanying migrating parents contain the residence permit, social insurance payment records, and proof of parents' employment. The materials are submitted by the candidate or parent, and schools and admissions examination institutions accept them centrally according to the registration cycle, with the update pace advancing along with review batches. After entering the workflow, the registration form assumes the role of the main record, while the household registration and student status proof and the materials for children accompanying migrating parents assume the role of supporting evidence. The fields of the three must mutually corroborate one another in name, quantity, date, and signature; missing items and inconsistencies will trigger follow-up questions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Intake records and items to be completed" are continued and completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether fields, dates, and signature are complete, and whether the examination category and household registration address are consistent with the supporting materials | Check the signature field and date on the registration form, and compare the name and household registration address in the household registration and student status proof; reference variables in the node to check whether the selection result variable is passed to subsequent nodes |
| Household registration and student status proof | Whether the student status number and school seal are complete, and whether the name, quantity, and date match those on the registration form | Compare the name and date in the two materials item by item, and confirm the seal and receipt; use nodeId to locate the node and view the interaction status in the run record |
| Materials for children accompanying migrating parents | Whether the dates and quantities of the residence permit, social insurance records, and employment proof are consistent, and whether missing signatures or receipts are identified | Check the validity period of the residence permit and the social insurance payment months, and inspect the signature on the parents' employment proof; trigger a node once and observe whether the branch direction is consistent with the selected option |
| Intake records and items to be completed | Whether missing items are identified and followed up on, and whether the answers are based on materials | Check whether the follow-up items correspond to the missing materials, and confirm that the answers reference specific material fields; reference the selection result variable in subsequent nodes and run a trial once |
Three common errors
- Phenomenon: the same candidate's name is written inconsistently in the registration form and the household registration and student status proof. Cause: the two materials are filled in at different stages, and no field comparison or unification was performed.
- Phenomenon: the social insurance months in the materials for children accompanying migrating parents do not match the residence permit date. Cause: versions were not synchronized, and old-version materials were submitted with a new batch without verifying the date range.
- Phenomenon: the registration form lacks a signature or receipt, and after follow-up it still continues along the default branch. Cause: the options and branch connections were not checked one by one, and the process stops after the interaction is completed.
How to verify the setup
This function's acceptance: run trials option by option, check the branch direction and interaction status in the run record, and confirm that variables has been passed to subsequent nodes and that the node status corresponding to nodeId is recorded.
Business test: submit a question missing key information, see whether it first asks a follow-up question before answering, and check whether the answer is based on materials.
- In the node, check the options and branch connections one by one, trigger once, and view the node status and interaction status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that missing items are identified and followed up on, and that the answers are based on materials.