What this category's data looks like
The category materials for general college entrance examination registration qualification verification include three types: the college entrance examination registration form, household registration and student status proof, and materials for children accompanying migrant workers. The college entrance examination registration form is entered by the candidate or the registration point, and contains name, ID number, examination category, and signature field; the household registration and student status proof is issued by the household registration and student status management departments, and contains household registration address, student status start and end dates, handler signature, and receipt; the materials for children accompanying migrant workers are provided by the candidate's family and relevant departments, and contain residence permit, social insurance payment records, and parents' employment proof. Materials enter in batches according to registration batches and review nodes, and the update rhythm is synchronized with the review progress. Field characteristics are concentrated in names, dates, quantities, signatures, and receipts. When the three types of materials enter the exception tracing and manual review function, the registration form serves as the main record, and the household registration and student status proof and the materials for children accompanying migrant workers serve as the basis for comparison, respectively assuming the roles of identity verification and qualification condition verification.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "exception list and review conclusion" is parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| College entrance examination registration form | Name, date, and signature field are consistent across all materials | Check the name and ID number on the registration form, and compare the signature field with the receipt date |
| Household registration and student status proof | Household registration address, student status start and end dates, and handler signature are traceable | Verify the proof issuance date and student status start and end dates, and check the handler signature and receipt |
| Materials for children accompanying migrant workers | The dates and quantities of the residence permit, social insurance records, and parents' employment proof match | Compare the residence permit validity period with the social insurance payment months, and check the number of employment proof copies |
| HTTP request | Placeholder variables in path parameters, request headers, and request body can be resolved into actual values | View the fully rendered address in the request preview, and check the request header names and value sources |
Three common errors
- Symptom: The same candidate's name is written differently on the registration form and the household registration and student status proof, and the dates also do not match. Cause: The two materials were entered by different handling steps, and no cross-comparison was performed.
- Symptom: The version of the materials for children accompanying migrant workers was not synchronized, and an old version of the residence permit and a new version of the social insurance records entered at the same time. Cause: After the materials were updated, they were not uniformly replaced according to the review nodes.
- Symptom: The household registration and student status proof lacks the handler signature or receipt. Cause: The issuance step did not complete sign-off, and the materials directly entered the review queue.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample; check the Authorization request header and the source of the variables variables, and confirm that the responseData returned fields are consistent with the agreement.
Business test: create one exception record, see whether the source material can be traced, and check the reviewer's signature and the support from the original record.
- In the variables panel, check the source of each placeholder, and confirm that the variables in path parameters, request headers, and request body can all be traced to global variables, system variables, or outputs from preceding nodes.
- Use one sample request to compare the returned fields, check the request header names and value sources, and confirm that the authentication information is passed in according to the external system's requirements.