What this category's data looks like
The Q&A intake and missing-item follow-up for general college entrance examination registration qualification review revolves around three types of materials: 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 carries the candidate's basic information and examination subjects, with fields including name, ID number, student status number, registration category, signature, and date; the household registration and student status certificates are issued by the place of household registration and the school attended, with fields including household registration address, date of move-in, student status start and end dates, and school seal; materials for children accompanying migrant workers include residence permits, social insurance payment records, and parents' employment certificates, with fields including document number, validity period, and handling signature. The sources of the materials are candidate submission and external system return, and the update rhythm advances according to registration batches and review nodes, with corrected materials flowing back after follow-up questions. When the three types of materials enter this function, the registration form serves as the main record, and the household registration and student status certificates and materials for children accompanying migrant workers serve as supporting documents, used to compare whether the name, quantity, date, and signature receipt of the same record are consistent.
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 intake records and the completed question items are parsed from the response by subsequent nodes, or handled and completed by the external system according to the agreement. The HTTP node is only responsible for sending the question and material fields according to the agreement, and does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| College entrance examination registration form | The name, ID number, registration category, signature, and date are consistent across all columns, and missing items can be identified as items pending follow-up questions | Check the placeholder sources in the variable panel, preview the rendered request body fields, and compare the returned fields with the sample |
| Household registration and student status certificates | The household registration address, date of move-in, student status start and end dates, and the dates and signatures of the school seal are complete, and match the same record in the registration form | Check the source of the Authorization value in the request header, and use a sample request to compare the returned fields |
| Materials for children accompanying migrant workers | The residence permit number, social insurance payment records, and parents' employment certificates have complete validity periods and handling signatures, and the quantity and dates do not conflict | Check that the request body fields are consistent with the external interface agreement, and confirm the mapping relationship between variables and responseData |
| HTTP node | The request address, path parameters, request headers, and placeholder variables in the request body can all be resolved into actual values | View the complete rendered address in the request preview, and check the source of each placeholder |
Three common errors
- Symptom: The same candidate's name is written differently in the registration form and the household registration and student status certificates. Cause: The two materials are entered by different handling steps, and the names and dates have not been compared for consistency.
- Symptom: The residence permit validity period in the materials for children accompanying migrant workers does not match the date in the social insurance records. Cause: The versions are not synchronized, and the corrected materials have not flowed back to the main record.
- Symptom: The registration form lacks the candidate's signature or receipt, but is still accepted as complete material. Cause: Missing-item identification does not cover the signature and receipt fields, and the follow-up question step is not triggered.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm the correspondence of the three identifiers Authorization, variables, and responseData in the request header, variable sources, and returned fields.
Business test: submit a question missing key information, and see whether it asks a follow-up question first before answering.
- In the request preview, check the complete rendered address and path parameters, and confirm that the placeholder variables can be resolved into actual values.
- In the variable panel, check the source of each placeholder, confirm that the request body fields are consistent with the external interface agreement, and use a sample request to compare the return.