What this category's data looks like
General college entrance examination registration qualification verification centers on the registration form, household registration and student status certificates, and materials for children accompanying migrant workers as its core categories. The registration form is filled in by the candidate and initially reviewed by the school, with fields including name, ID number, examination subject category, signature, and date; the household registration and student status certificates are issued by the household registration and student status management departments, with fields including household registration address, date of move-in, student status number, and seal; the materials for children accompanying migrant workers are provided by the family, with fields including residence permit, social insurance payment records, proof of enrollment, and receipt. The three types of materials enter in batches according to the registration batch, and the update rhythm is driven by qualification verification milestones, with supplementary submissions and corrections often occurring. When entering this function, the registration form serves as the primary record, while the household registration and student status certificates and the materials for children accompanying migrant workers serve as supporting evidence, each taking on the roles of field comparison, date verification, and signature and receipt inspection, providing original record support for exception tracing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 | Check the name, ID number, examination subject category, and signature date, and confirm consistency with the household registration and student status certificates | Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run records, and use variables and nodeId to locate the exception record |
| Household registration and student status certificates | Check the household registration address, date of move-in, student status number, and seal, and confirm that the dates match those on the registration form | Reference the selection result variable in subsequent nodes and run a trial once to confirm it has been passed to subsequent nodes, and compare the dates and names on the two materials |
| Materials for children accompanying migrant workers | Check the residence permit, social insurance payment records, proof of enrollment, and receipt, and confirm that no signature or receipt is missing | Trigger one interaction, view the node status in the run records, and confirm that the selection result variable has been passed to subsequent nodes |
| Exception list and review conclusions | Check that exceptions are supported by original records and that the reviewer has signed, and confirm that they can be traced back to the source materials | Check the options and branch connections one by one in the node, run a trial branch to confirm the direction, and record variables and nodeId |
Three common errors
- Phenomenon: The same candidate's name is written differently on the registration form and the household registration and student status certificates, and the dates also do not match. Cause: The two materials are entered in different stages, and field-level comparison and version synchronization have not been performed.
- Phenomenon: The materials for children accompanying migrant workers lack a receipt or signature, yet the review conclusion is still submitted. Cause: Material receipt and review belong to different nodes, and receipt inspection has not been included in branch judgment.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections have not been checked one by one, and the selection result variable has not been passed to subsequent nodes.
How to verify the setup
Acceptance of this function: run trials for each option one by one, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and use variables and nodeId to locate node status.
Business test: create an exception record, see whether it can be traced back to the source materials, confirm that the exception is supported by original records and has the reviewer's signature, and then hand it over to the person in charge for handling.
- Check the options and branch connections one by one in the node, trigger one interaction, view the node status in the run records, and confirm that the status is recorded when entering the node.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm it has been passed to subsequent nodes, while also recording the number of references and the reference content budget, and checking the tokens of the referenced text.