What this category's data looks like
This category's data involves three types of materials: the registration record documents the candidate's identity and enrollment status, the course pass certificate records individual subject scores and the date obtained, and the graduation application form carries the completion status of the professional plan and signatures. The materials come from provincial examination offices, main examining institutions, and study-aid institutions, and are updated by examination session and graduation batch. Fields include name, admission ticket number, course code, pass date, review opinion, and seal. When the materials enter the exception tracing and manual review function, the registration record serves as the baseline for identity and eligibility, the course pass certificate serves as the basis for scores and credits, and the graduation application form serves as the application carrier for the graduation conclusion. The three must corroborate each other in name, quantity, date, and signature; any inconsistency triggers the exception list.
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 are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP module sends requests to the target address. Path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Registration record | Name, admission ticket number, and enrollment status are consistent between the record and the pass certificate, and the date and signature are traceable | In the variable panel, check the source of each placeholder and confirm that the request body fields are consistent with the record interface agreement |
| Course pass certificate | Course code, pass date, and quantity match between the pass certificate and the graduation application form | Use one sample request to compare the response and check the pass certificate fields in responseData against the original records |
| Graduation application form | Review opinion, signature, and receipt are complete, and the version is synchronized with the current batch | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
| External system interface | Returned fields are consistent with the agreement, and placeholder variables can be resolved into actual values | In the request preview, view the complete rendered address and check variables and path parameters |
Three common errors
- Symptom: The same candidate's name or course quantity does not match between the pass certificate and the application form. Cause: The two materials were entered at different times, and there is a lack of field-by-field comparison using the registration record as the baseline.
- Symptom: The version of the graduation application form is not synchronized, and the old-version signature column coexists with the new-version review opinion. Cause: After the batch update, it was not regenerated according to the latest template and confirmed with a receipt.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information was not passed in according to the external system's requirements, and placeholder variables were not resolved into actual values.
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 one sample; confirm that the placeholders at Authorization, variables, and responseData are all traceable.
Business test: create one exception record, see whether it can be traced back to the source material, and check whether the exception list and review conclusion are supported by original records and signed.
- In the variable panel, check the source of each placeholder and confirm that the placeholders in the request address, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the response, check that the returned fields are consistent with the external interface agreement, and record the number of array items and the tokens of the referenced text.