What this category's data looks like
This page focuses on data versioning and change maintenance under the graduate admissions re-examination and admission category, involving three types of materials: re-examination plans, candidate score sheets, and transfer lists. Re-examination plans are usually published annually by the admitting unit and contain procedures, time nodes, and scoring rules; candidate score sheets come from preliminary and re-examination scoring records, with fields including candidate number, subject, score, and date; transfer lists are exported from the transfer system and contain candidate number, original applying unit, proposed admission major, and signature field. In the HTTP interface and external system functions, the re-examination plan enters the request body as the rule baseline for external system verification, while candidate score sheets and transfer lists are passed as data payloads through path parameters and request headers. The update rhythm advances with admission batches, and the field characteristics are that dates, quantities, names, signatures, and receipts must be consistent across materials.
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 by the external system as agreed and then completed.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | The dates, procedure nodes, and signature requirements in the plan must be consistent with the current year's admission batch | In the request preview, check the rendered complete address and request body fields, and confirm the plan version number and reference source |
| Candidate score sheet | The name, quantity, and date for the same candidate number in the score sheet and transfer list must match | Use one sample request to compare the response, and check the source and value of each placeholder in variables |
| Transfer list | The proposed admission major, original applying unit, and signature receipt in the list must be consistent with the plan agreement | Check the request header names and value sources, and confirm that Authorization is passed in according to external system requirements |
| Version ledger | The current version is unique, old versions are traceable, and references are updated synchronously | After changing one piece of content, check in the variable panel whether the responseData returned fields and references are synchronized |
Three common errors
- Symptom: The name, quantity, or date for the same candidate does not match between the score sheet and the transfer list. Cause: The two materials are maintained separately, without cross-checking against the current version as the sole baseline.
- Symptom: After the re-examination plan is updated, the external system still processes according to the old version's fields. Cause: The version was not synchronized, and the request body and request headers were not adjusted to the current version.
- Symptom: The transfer list lacks a signature or receipt, but the external system still returns success. Cause: The request body does not include the signature field, and subsequent nodes do not parse the missing marker in the response.
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; confirm that the three placeholders Authorization, variables, and responseData are traceable.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the variable panel, check the source of each placeholder, and confirm that the variables in the request address, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the response, check that the fields are consistent with the external interface agreement, and record the array length and the tokens budget of the reference text.