What this category's data looks like
This category's data involves three core types of materials: registration forms, care bonus-point materials, and admission rosters. Registration forms are filled in by candidates and initially reviewed by registration points, with fields including name, ID number, application level, subject category, date, and signature; care bonus-point materials are submitted by candidates and reviewed by relevant departments, with fields including bonus item, certificate number, review opinion, and receipt; admission rosters are generated by admitting institutions by batch, with fields including candidate number, admitted major, admission date, and responsible person's signature. The three types of materials update at different rhythms: registration forms roll with registration batches, bonus-point materials are supplemented as review progresses, and admission rosters are generated centrally by admission batch. When materials enter the exception tracing and manual review function, registration forms serve as the original record support, bonus-point materials serve as the review basis, and admission rosters serve as the result comparison object; together, the three support the generation of the exception list and review conclusions.
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 conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether the name, date, and signature match the bonus-point materials and admission roster | Retrieve the original registration form record, check the name, ID number, application level, date, and signature, and compare with the other two materials |
| Care bonus-point materials | Whether the bonus item, certificate number, and receipt are complete and version-synchronized | Check the bonus item and certificate number, inspect the review opinion and receipt signature, and trace to the source when the version is not synchronized |
| Admission roster | Whether the candidate number, admitted major, and admission date are consistent with the registration form | Check the candidate number and admitted major, compare with the registration form date, and inspect the responsible person's signature and batch version |
| HTTP request | Whether the path parameters, request headers, and request body can be parsed into actual values | In the preview, check the address after variables rendering, check Authorization and the request body fields, and compare the responseData return |
Three common errors
- Symptom: The name or date of the same candidate does not match between the registration form and the admission roster. Cause: The two materials are entered at different stages, and no field-level comparison or version synchronization has been done.
- Symptom: The care bonus-point materials lack a review opinion or receipt signature. Cause: The review stage did not return the signed document, and the material version was not synchronized to the review node.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue was not checked, and thevariablesplaceholders were not parsed into actual values.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare one sample result to confirm that responseData is consistent with the agreement.
Business test: create one exception record, see whether the source material can be traced, and check the fields, dates, and signatures of the registration form, bonus-point materials, and admission roster.
- In the variable panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Check the request header names and value sources, confirm that
Authorizationis passed in according to the external system's requirements, and compare the returned fields using a sample request.