What this category's data looks like
This page focuses on progress records and statistical verification for general college entrance examination registration qualification review. The materials come from three categories: the college entrance examination registration form, household registration and student status certificates, and materials for children accompanying migrant workers. The college entrance examination registration form provides the candidate's basic information and registration number, and is the source of the primary key for the progress table; the household registration and student status certificates carry the household registration address, student status number, and enrollment status, and are used to verify the household registration and student status conditions in registration qualification; the materials for children accompanying migrant workers supplement residence permit, social security contribution, and parental employment information, supporting the determination of accompanying migrant worker qualification. The three material categories are summarized weekly, and the update rhythm is synchronized with registration review batches. Field characteristics include name, ID number, registration number, household registration address, student status number, residence permit number, social security months, signature, and receipt date. When the materials enter this function, each serves as an independent data source, and the progress record step associates them by registration number. The statistical scope is stated in the table header, including the record count and deduplication rules, and exceptional cases are marked separately.
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 progress table and statistical scope description are completed by subsequent nodes parsing the response, or by an external system handling it according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| College entrance examination registration form | Whether fields, dates, and signatures are complete, and whether the registration number is unique | Check the name, ID number, registration number, and signature date, view the rendered complete address in the request preview, and confirm that path parameter placeholders can be resolved into actual values |
| Household registration and student status certificates | Whether the household registration address, student status number, and enrollment status are consistent with the registration form | Compare the name, household registration address, and student status number of the same record, check the date and signature, and verify the request header names and value sources |
| Materials for children accompanying migrant workers | Whether the residence permit number, social security months, and parental employment information match | Use one sample request to compare the response, verify that the request body fields are consistent with the external interface agreement, and confirm that variable sources are traceable |
| Variable sources | Whether each placeholder can be traced to a specific origin | Verify the source of each placeholder in the variable panel, confirm that the values of variables and Authorization are correct, and check the fields returned by responseData |
Three common errors
- Symptom: The name or date of the same candidate does not match between the registration form and the household registration and student status certificates. Cause: The two materials are entered separately, and no cross-check is performed by registration number.
- Symptom: The version of the materials for children accompanying migrant workers is not synchronized, and both old and new versions of the residence permit number and social security months appear. Cause: After the materials are updated, they are not uniformly replaced, and the progress table still references the old version.
- Symptom: Some records lack signatures or receipts, but are included in the total during statistics. Cause: Summary is performed before the review process is completed, and exceptional cases are not marked separately in the table header scope.
How to verify the setup
This function acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that responseData and Authorization are used correctly.
Business test: use one week of records to verify the total, check whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match and that the scope is written in the table header.
- Compare the names, quantities, and dates in the college entrance examination registration form, household registration and student status certificates, and materials for children accompanying migrant workers one by one by registration number, and mark inconsistent items.
- Verify the source of each placeholder in the variable panel, confirm that
variablesandAuthorizationare traceable, and check that theresponseDatafields are consistent with the agreement.