What this category's data looks like
This category's materials include three types: physical examination forms, re-examination applications, and notices of restricted majors. Fields cover name, ID number, examination items, conclusion, date, and signature. The physical examination form is filled in by the candidate with basic information, and the hospital fills in the examination results and signs; the re-examination application is submitted by the candidate or the middle school and reviewed by the physical examination station; the notice of restricted majors is issued by the physical examination station and signed for by the candidate. The material sources are each middle school and physical examination station, and the update pace advances with the admissions batch; re-examinations and notices are often revised multiple times within a week. After these materials enter the version ledger and change record function, each takes on a different role: the physical examination form serves as the basic data source, the re-examination application serves as the change trigger evidence, and the notice of restricted majors serves as the basis for external reference. The version ledger must ensure that the current version is unique, old versions are traceable, and references are synchronized, avoiding mismatches in names, quantities, and dates for the same record across two 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 externally 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 |
|---|---|---|
| Physical examination form | Whether the fields, date, and signature are consistent with the re-examination application | Take one physical examination record, check the name, number of examination items, and examination date, then check whether the signature field is complete |
| Re-examination application | Whether the application date and receipt correspond to the conclusion of the physical examination form | Compare the submission date of the re-examination application with the conclusion date of the physical examination form, and check whether the receipt signature exists |
| Notice of restricted majors | Whether the notice date and signature are synchronized with the current version | Check the major name, restricted conclusion, and version number on the notice, and confirm they are consistent with the current version in the ledger |
| Version ledger | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check the variables source in the variable panel, and use responseData to compare the returned fields |
Three common errors
- Symptom: The same candidate's name and number of examination items do not match between the physical examination form and the re-examination application. Cause: The two materials are entered separately by different nodes, without field-level comparison and receipt verification.
- Symptom: The notice of restricted majors has been updated, but external documents still reference the old version. Cause: The version was not synchronized, the reference relationship was not updated when the version number changed, and the old version was not marked as invalid.
- Symptom: The re-examination application lacks a signature or receipt, and the external system receives empty fields. Cause: The request body fields are inconsistent with the external interface agreement, and the authentication information was not passed in according to the
Authorizationrequirement.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample; at the same time, check whether variables and responseData can be traced to a specific source.
Business test: change one piece of content and see whether the version number and references are updated synchronously; if the number of references changes, record the array length separately, and check the tokens of the reference text against the quoteMaxToken budget.
- In the request preview, view the complete rendered address and check whether the path parameter placeholders are parsed into actual values.
- In the variable panel, check the source of each placeholder and confirm whether it comes from a global variable, system variable, or the output of a preceding node.