What this category's data looks like
This page focuses on the regular higher education institution admissions enrollment filing business. The materials come from three types of documents: admissions plans, filing rules, and admission rosters, updated daily by admission batch. Admissions plans provide institution-major groups and planned numbers; filing rules give the filing ratio and tie-breaking basis; admission rosters record candidates' filing trajectories and admission results. When these three types of materials enter the progress records and statistical verification function, admissions plans and filing rules serve as the baseline criteria, and admission rosters serve as record details, used to generate progress tables and statistical criteria descriptions. Field characteristics include institution code, major group number, candidate number, filing date, admission status, and signature column. Names, quantities, and dates among materials must be aligned item by item, and versions and receipts must be retained in sync for reference in weekly or monthly reports.
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 criteria description" is parsed from the response by subsequent nodes, or handled externally by an external system according to the agreement. The HTTP module sends requests to the target address. Path parameters, request body, and request headers can all use variable placeholders, and variables come from global variables, system variables, or outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Admissions plan | Whether the institution code, major group number, planned number, and the batch and date in the filing rules are consistent item by item | In the request preview, check the rendered complete address, compare the returned fields with a sample request, and check whether the planned number and rule criteria are aligned |
| Filing rules | Whether the filing ratio and tie-breaking order correspond to the filing status and date in the admission roster | Check the request header names and value sources, confirm that authentication information is passed in according to the external system's requirements, and then compare the rule fields with the roster records |
| Admission roster | Whether the candidate number, admission status, signature column, and receipt are complete, and whether the version is in sync | In the variables panel, check the source of each placeholder, confirm the reference sources of variables, responseData, and Authorization, and then check the roster signature and receipt |
| Progress table and statistical criteria description | Whether the record count matches the statistical count, whether the criteria are written in the header, and whether exceptions are clearly stated | Use one week of records to check the totals, check the header criteria and exception notes, and confirm that the returned fields are consistent with the statistical results |
Three common errors
- Symptom: The institution name, quantity, and date for the same candidate do not match between the admissions plan and the admission roster. Cause: The versions of the two materials are not synchronized, or they were not checked against the same criteria during entry.
- Symptom: The batch date in the filing rules is inconsistent with the filing date in the roster. Cause: The rules were updated but not synchronized to the roster, or the date fields reference different sources.
- Symptom: The admission roster lacks a signature or receipt, and the statistical total does not match the record count. Cause: The signature step was not completed, or the receipt was not retained together with the version.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, and then compare the results against one sample; confirm the reference sources of variables, responseData, and Authorization.
Business test: use one week of records to check the totals, see whether the criteria and exceptions are clearly stated, and confirm that the record count matches the statistical count.
- In the request preview, check the rendered complete address and confirm that the path parameters and request body fields are consistent with the external interface agreement.
- In the variables panel, check the source of each placeholder and confirm that the references to global variables, system variables, and outputs from preceding nodes are correct.