What this category's data looks like
Self-taught examination records and graduation review materials fall into three categories. The examination registration file records the candidate's basic information, admission ticket number, major name, and enrollment status, and is the foundational record of identity and eligibility; the course pass certificate records, course by course, the name, credits, score, and date obtained, and supports the calculation of graduation credits; the graduation application form carries the name, major, number of courses, signature, and receipt, and is the vehicle for the review conclusion. The three types of materials come from different sources: the examination registration file comes from the provincial-level examination registration database, the course pass certificate comes from each score release, and the graduation application form comes from the candidate and the host institution. In terms of update cadence, the examination registration changes with transfer examinations, exemption applications, and information corrections, the pass certificate is appended with each score announcement, and the application form is generated in a concentrated manner during the graduation application period. When the materials enter the authorized access and external service function, the examination registration file determines the visitor's identity and visible scope, the course pass certificate determines the field-level visible content, and the graduation application form determines external opening and the receipt destination.
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 externally available entry point and authorization scope are completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The request URL and path parameters, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Examination registration file | Visitor identity and visible scope match; unauthorized access is not visible | Check the source of the Authorization value in the request headers, preview the fully rendered URL, and confirm that path parameters are parsed into actual values |
| Course pass certificate | Course names, quantities, and dates match the examination registration file item by item | Use a sample request to compare returned fields, and check whether the number of courses and dates obtained match the foundational record |
| Graduation application form | Signature and receipt are complete, and the version is in sync with the examination registration file | Check that the request body fields are consistent with the external interface agreement, and check the source of each placeholder in the variables panel |
| Variable source | Every placeholder can be traced to a specific origin | Check the sources of variables and responseData in the variables panel, and confirm that the output of preceding nodes has been parsed |
Three common errors
- Symptom: The name or number of courses for the same candidate does not match between two materials. Cause: The examination registration file and the course pass certificate have different update cadences, and one side has been corrected while the other has not been synchronized.
- Symptom: The graduation application form lacks a signature or receipt, and the review conclusion cannot be made external. Cause: The application form is generated in a concentrated manner during the application period, and the signature and receipt steps were not checked one by one.
- Symptom: The request returns 401, and the external system receives empty fields. Cause: The authentication information in the request headers was not passed in as required by the external system, and the variable placeholders 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, and then compare the result against a sample; check whether the request header Authorization and the returned field responseData conform to the agreement.
Business test: access once with a restricted identity and see whether the visible scope matches the setting
- Check the request header names and value sources, and confirm that
Authorizationis passed in as required by the external system - Use a sample request to compare the return, and confirm that the request body fields are consistent with the external interface agreement