What this category's data looks like
This category's data involves three core types of materials: the adult college entrance examination registration form, care bonus point materials, and the admission roster. The registration form records the candidate's basic information, application level, and preferences, with fields including name, ID number, application subject category, date, and candidate signature; the care bonus point materials include the bonus item name, certificate number, review opinion, and handler signature, with an update cadence that advances along with review batches; the admission roster is generated by batch, including candidate number, admitted major, admission date, and responsible person's signature. When these three types of materials enter the authorized access and external service function, the registration form serves as the identity and application basis, the care bonus point materials serve as additional qualification evidence, and the admission roster serves as the final result evidence. During external service, parents or superiors view the corresponding records within the authorized scope; the names, quantities, and dates among the materials must remain consistent, versions must be synchronized, and signatures and receipts must be complete.
Configuration and implementation checks
This part is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "externally available entry point and authorization scope" are completed by subsequent nodes parsing the response, or by the external system handling it according to the agreement. The HTTP node sends a request 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 |
|---|---|---|
| Adult college entrance examination registration form | Name, ID number, application subject category, date, and candidate signature are consistent across the three types of materials, and versions are synchronized | In the request preview, view the complete rendered address, and check whether the registration form fields match the returned fields |
| Care bonus point materials | Bonus item name, certificate number, review opinion, and handler signature are complete, and the date is consistent with the registration form batch | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
| Admission roster | Candidate number, admitted major, admission date, and responsible person's signature match the registration form and bonus point materials | Use a sample request to compare the response, and check whether the roster fields in responseData are consistent with the material records |
| Variable sources | Every placeholder can be traced to a specific origin, and there are no empty fields or expired references in variables | In the variables panel, check the source of each placeholder, and confirm it comes from a global variable, system variable, or the output of a preceding node |
Three common errors
- Symptom: The same candidate's name or date does not match between the registration form and the admission roster. Cause: The two records were entered separately and version synchronization was not performed, resulting in inconsistent externally returned fields.
- Symptom: The care bonus point materials lack a handler signature or receipt. Cause: The review step was not closed-loop, so fields are empty when the materials enter external service, and the external system receives empty fields.
- Symptom: The request returns 401 or times out. Cause: Authentication information was not passed in according to the external system's requirements, or placeholder variables were not resolved into actual values, causing the request address and path parameter rendering to fail.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the references in Authorization, variables, and responseData can all be resolved.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting and unauthorized records are not visible.
- In the request preview, check the complete rendered address, and verify whether the path parameter placeholders are resolved into actual values.
- In the variables panel, check the source of each placeholder, and confirm that the request body fields are consistent with the external interface agreement.