What this category's data looks like
The category materials for graduate admissions re-examination and admission include the re-examination plan, the candidate score table, and the transfer list. The three are updated by admissions year, with a common rhythm of the plan being issued first, the score table rolling with re-examination batches, and the transfer list being finalized after the transfer system closes. In terms of field characteristics, the plan contains assessment items, weights, dates, and signature fields; the score table contains candidate number, preliminary and re-examination scores, total score, and ranking; the transfer list contains transfer batch, original application unit, proposed admission major, and receipt. When the materials enter the exception tracing and manual review function, the plan serves as the basis for judgment, while the score table and transfer list serve as the objects being compared, each taking on the role of rule source and record source, used to check whether the name, quantity, and date of the same record match, whether versions are synchronized, and whether signatures or receipts are complete.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Whether the assessment items, weights, dates, and signature fields are consistent with the batches of the score table and transfer list | Compare the plan version number and signature fields, and check whether the assessment item names, weights, and dates in the plan can correspond to the batches recorded in the score table and transfer list |
| Candidate score table | Whether the candidate number, name, preliminary and re-examination scores, total score, and ranking are consistent across materials of the same batch | Spot-check the name, quantity, and date of the same candidate in the score table and transfer list, and check records missing signatures or receipts |
| Transfer list | Whether the transfer batch, original application unit, proposed admission major, and receipt are synchronized with the plan and score table | Check whether the transfer list version and plan version are synchronized, check whether the receipt field is empty, and trace each item back to the source material |
| HTTP node request | Whether the request URL and path parameters, request headers, and placeholder variables in the request body can be parsed into actual values | View the rendered complete URL in the request preview, check the Authorization request header and request body fields, and verify the source of each variables placeholder in the variables panel |
Three common errors
- Symptom: The name, quantity, and date of the same candidate do not match between the score table and the transfer list. Cause: The two materials were exported from different batches and were not merged and compared by the same candidate number.
- Symptom: The re-examination plan has been updated, but the score table and transfer list are still executed according to the old version. Cause: Versions are not synchronized, and the version number and effective date are not recorded during material circulation.
- Symptom: Exception records lack signatures or receipts, and review conclusions cannot be archived. Cause: The signature fields and receipt fields were not verified during material collection, and the exception list did not attach the original records.
How to verify the setup
This function acceptance: preview the rendered request, check the status code and returned fields, then compare one sample result to confirm that the exception list and review conclusion fields returned by responseData are complete.
Business test: create an exception record, see whether it can be traced back to the source material, and check the fields, dates, and signatures of the re-examination plan, candidate score table, and transfer list.
- In the request preview, check the rendered complete URL,
Authorizationrequest header, and request body fields, and confirm that eachvariablesplaceholder can be traced to a global variable, system variable, or output from a preceding node. - Use one sample request to compare the return, check whether the external system receives empty fields, and record whether the signatures and receipts of the exception list and review conclusions are complete.