What this category's data looks like
This page focuses on progress records and statistical verification in self-taught examination registration and graduation review, involving three types of materials: registration archives, course qualification certificates, and graduation application forms. Registration archives are filed by the provincial examination office according to examination period, recording the candidate's basic information, admission ticket number, major, and main examining institution; course qualification certificates are generated one by one for each course, stating the course code, name, score, and date of acquisition; the graduation application form is submitted after all courses are passed, containing name, ID number, major, number of courses, signature, and receipt. When materials enter this function, the registration archive provides the basic identity and major scope, the course qualification certificates provide course-by-course qualification records and dates, and the graduation application form provides the summarized course count and signature status. The update rhythm advances with examination periods and graduation application batches, and the field characteristics are concentrated in names, course names, quantities, dates, and signature receipts.
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 "progress table and statistical scope description" is parsed by subsequent nodes, or handled externally according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Registration archive | Name, admission ticket number, major, and main examining institution are consistent in naming across the archive, qualification certificates, and application form, and dates are traceable | Check fields and dates, and compare the name and major wording in the two materials |
| Course qualification certificate | Course code, name, score, and date of acquisition correspond one by one, and the quantity matches the summarized course count on the application form | Compare names and dates course by course, and count the number of passed courses |
| Graduation application form | Course count, name, ID number, and signature receipt are complete, and dates do not conflict with the dates of acquisition on the qualification certificates | Check the signature and receipt, and verify the summarized course count against the number of qualification certificates |
| HTTP node output | The response body, status code, and returned fields are returned as agreed, and the number of records and statistics in responseData match | View the rendered address and request body in the request preview, and compare the returned fields using a sample request |
Three common errors
- Symptom: The same candidate's name or course name is written differently in the two materials. Cause: Different entry batches, without verification against a unified scope.
- Symptom: The number of course qualification certificates does not match the summarized course count on the graduation application form. Cause: Some qualification certificates were not synchronized or were omitted from the count, and the statistical scope was not written into the header.
- Symptom: The graduation application form lacks a signature or receipt, and the date conflicts with the date of acquisition on the qualification certificate. Cause: Versions were not synchronized during material circulation, and the review step was not backfilled.
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 a sample; in the variable panel, check the sources of variables and Authorization, and confirm that the number of records and statistics in responseData are consistent.
Business test: use one week of records to verify the totals, and see whether the scope and exceptions are clearly stated.
- In the request preview, view the complete rendered address, and check whether the path parameters and request body fields are consistent with the external interface agreement.
- In the variable panel, check the source of each placeholder, and confirm that
variables,Authorization, andresponseDatacan be traced to global variables, system variables, or outputs from preceding nodes.