What this category's data looks like
This page focuses on the graduate admissions re-examination and admission category. The materials come from the re-examination plan, the candidate score sheet, and the transfer list, and the update cadence is synchronized with admissions batches and weekly/monthly reports. The re-examination plan provides process nodes and signature requirements, the candidate score sheet provides scores and rankings, and the transfer list provides transfer destinations and statuses. When these three types of materials enter the progress records and statistical reconciliation function, each plays a different role: the re-examination plan serves as the basis for the statistical caliber, the candidate score sheet serves as the main record body, and the transfer list serves as exceptions and supplements. Field characteristics include candidate ID, name, major, date, quantity, and signature column, and the statistical caliber and exception notes must be written in the table header to facilitate subsequent verification of whether the number of records and the statistical count match up.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "progress table and statistical caliber description" is parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Whether the fields, dates, and signatures are consistent with the candidate score sheet | Check the name, quantity, date, and signature column in the plan, and confirm there are no missing signatures or receipts |
| Candidate score sheet | Whether the number of records and the statistical count match up, and whether the caliber is written in the table header | Use one week of records to verify the total, and check whether the names, quantities, and dates in the score sheet and the transfer list are consistent |
| Transfer list | Whether the version is synchronized and whether exceptions are clearly stated | Compare the version numbers of the transfer list and the score sheet, and confirm that the transfer status and signature receipts are complete |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the rendered full address in the request preview, and check the source of variables |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the re-examination plan and the candidate score sheet. Cause: The two materials are maintained separately and are not checked against the same caliber.
- Symptom: The version of the transfer list is not synchronized, causing the statistical count and the number of records to be inconsistent. Cause: The update cadence differs, and version markers and signature receipts are missing.
- Symptom: The request returns 401, and the external system receives empty fields or the request times out. Cause:
Authorizationorvariablesare not passed in according to the external interface agreement.
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 one sample to confirm that responseData and variables are traceable.
Business test: use one week of records to verify the total, see whether the caliber and exceptions are clearly stated, and confirm that the number of records and the statistical count match up.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Check the request header names and value sources, verify that
Authorizationis consistent with the external system requirements, and compare the response using one sample request.