What this category's data looks like
Adult college entrance examination registration and admission management involves three types of materials: registration forms, care bonus point materials, and admission rosters. The registration form is filled out by the candidate, and its fields include name, ID number, application level, and signature field; the care bonus point materials are submitted by the candidate, and include the certificate name, issuance date, and review signature; the admission roster is compiled by the handling stage, and includes the candidate's name, admitted major, admission date, and responsible person's signature. The three types of materials play different roles in Q&A handling and missing-item follow-up: the registration form is the baseline for identity and application information, the care bonus point materials are used to verify the basis for bonus points, and the admission roster is used to confirm the admission result. The materials are updated with the registration batch and admission batch. For the same record, the name, date, and signature in the registration form and the admission roster may be inconsistent and need to be compared item by item.
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 acceptance record and the completed follow-up questions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from previous nodes through variables, and the returned responseData is used by subsequent nodes.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether the name, ID number, application level, and signature field are complete, and whether the date is within the registration batch | Check the registration form fields and signature, and compare the name and date in the registration form and the admission roster |
| Care bonus point materials | Whether the certificate name, issuance date, and review signature are consistent, and whether the receipt is missing | Check the material name and issuance date, and check whether the review signature and receipt are complete |
| Admission roster | Whether the admitted major, admission date, and responsible person's signature are complete, and whether the version is synchronized | Check the admission roster fields, and compare the name, quantity, and date in the registration form and the roster |
| HTTP request | Whether Authorization is passed in according to the external system's requirements, and whether the variables placeholders are resolved into actual values | View the fully rendered URL in the request preview, and check the request header names and value sources |
Three common errors
- Symptom: The name or date for the same record does not match between the registration form and the admission roster. Cause: The two materials are entered at different stages, and no item-by-item comparison was performed.
- Symptom: The version of the care bonus point materials is not synchronized, and the review signature or receipt is missing. Cause: The materials were not returned after updating, and the signature field was not checked during acceptance.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue is incorrect, and thevariablesplaceholders are not resolved.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, and then compare the result against one sample; confirm that Authorization, variables, and responseData can all be traced to specific sources.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder and confirm that the request URL and path parameters can be resolved into actual values.
- Use one sample request to compare the response, and check that the request body fields are consistent with the external interface agreement.