What this category's data looks like
This page focuses on three types of materials in self-taught examination registration records and graduation review: registration records, course qualification certificates, and graduation application forms. Registration records come from the provincial registration system and contain name, ID number, examination registration number, major code, and enrollment status; course qualification certificates come from the unified examination score database and contain course code, course name, qualification date, and score; graduation application forms are filled out by candidates and preliminarily reviewed by the main examining institution, and contain major name, intended graduation time, number of courses, and signature field. The three types of materials are updated by examination period and batch, and dates and signatures in the fields are key to review. When entering this function, registration records serve as the basis for identity and enrollment status, course qualification certificates serve as evidence of course completion, and graduation application forms serve as the application carrier for the graduation conclusion. The three exchange with external systems through the HTTP interface, forming a version ledger and change records.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled and completed by the external system according to the agreement. The request URL, path parameters, request headers, and placeholder variables in the request body come from global variables, system variables, or outputs of preceding nodes, and the variable panel can be used to check the source of each placeholder.
| Object | Check | Verification action |
|---|---|---|
| Registration records | Name, ID number, examination registration number, major code, and enrollment status must be consistent item by item with the course qualification certificates and graduation application form | Check the placeholder sources in the variable panel, and use a sample request to compare the returned fields with the record fields |
| Course qualification certificates | Course code, course name, qualification date, and score must match the major plan in the registration records | Check the request header names and value sources, and verify whether Authorization is passed in according to the external system's requirements |
| Graduation application form | Major name, intended graduation time, number of courses, and signature field must be consistent with the summary results of the course qualification certificates | Preview the rendered request body, and check whether the variables and responseData fields are consistent with the application form agreement |
| HTTP request | The placeholder variables in the request URL and path parameters can be resolved into actual values | View the complete rendered URL in the request preview, and confirm there are no empty fields or timeouts |
Three common errors
- Symptom: The same candidate's name is written differently in the registration records and the graduation application form. Cause: The two materials are entered separately, without field-level comparison and version synchronization.
- Symptom: The date on the course qualification certificate does not match the summary date on the graduation application form. Cause: The old version of the qualification certificate was not updated with the examination period, and the reference still points to the old record.
- Symptom: The graduation application form lacks the signature or receipt of the main examining institution. Cause: The review step did not write back the signature status, and the external system did not handle the returned fields according to the agreement.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against a sample; check the values and sources of Authorization, variables, and responseData.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- Check the source of each placeholder in the variable panel, and confirm it comes from a global variable, system variable, or the output of a preceding node
- Use a sample request to compare the returned fields, and confirm that the request header names and value sources meet the external system's requirements