What this category's data looks like
This category's data looks like this: General college entrance examination registration qualification review involves three types of materials: the college entrance examination registration form, household registration and student status proof, and materials for children accompanying migrating parents. The registration form is filled in by the candidate and initially reviewed by the school or registration point, with fields including name, ID number, examination category, graduating school, and signature field; the household registration and student status proof is issued by the public security authorities and the school, with fields including household registration address, date of move-in, student status start and end dates, and seal; the materials for children accompanying migrating parents are provided by the parents and relevant departments, with fields including residence permit, months of social insurance contributions, date of stable residence, and receipt. The three types of materials have different update rhythms: the registration form changes as the candidate modifies it, the household registration and student status proof is updated by semester or when move-in changes, and the accompanying materials are supplemented monthly or by batch. When materials enter this function, the registration form serves as the main record, and the household registration and student status proof and accompanying materials serve as comparison sources, used for item-by-item verification of names, quantities, dates, and signatures.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The discrepancy list is completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| College entrance examination registration form | Check whether the name, ID number, examination category, and signature field are consistent with the household registration and student status proof | Check the options and branch connections one by one in the node, and reference variables and nodeId to record the branch direction |
| Household registration and student status proof | Check whether the household registration address, date of move-in, student status start and end dates, and seal are consistent with the registration form | Trigger a node once, view the node status in the run record, and compare whether dates and signatures are missing |
| Materials for children accompanying migrating parents | Check whether the residence permit, social insurance months, date of stable residence, and receipt are complete | Reference the selection result variable in a subsequent node and run a trial once to confirm the branch direction and interaction state |
| Discrepancy list | Check whether the name, quantity, and date of the same record do not match across the two materials | Use one real record to find fields inconsistent with the ledger, submit them to the reviewer for confirmation, and write them back |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match across the two materials. Cause: The registration form and the household registration and student status proof are entered separately, without field-level comparison.
- Phenomenon: Versions are not synchronized, and an old receipt is still referenced. Cause: Accompanying materials are supplemented monthly, and the ledger is not refreshed as materials are updated.
- Phenomenon: Signatures or receipts are missing, and the materials are incomplete. Cause: The node only records selections and does not verify whether the signature field and receipt fields are complete.
How to verify the setup
How to verify the setup: Acceptance for this function: run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables and nodeId are correctly referenced.
Business test: Use one real record to find fields inconsistent with the ledger, submit them to the reviewer for confirmation, and write them back.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger a node once, view the node status in the run record, and reference the selection result variable in a subsequent node and run a trial once.