What this category's data looks like
University admissions physical examination organization materials mainly consist of three types: physical examination forms, re-examination applications, and restricted-major notifications. They come from each stage of the campus hospital and admissions office, and are updated document by document by batch and by candidate. The physical examination form records height and weight, past medical history, physician conclusion, and signature; the re-examination application records the re-examination items, date, and applicant signature; the restricted-major notification records the restricted major name, notification date, and candidate or parent receipt. When entering the exception tracing and manual review function, the physical examination form serves as the original record, the re-examination application serves as the basis for change, and the restricted-major notification serves as the notification voucher. The three are linked by candidate identifier and date into a chain of evidence, for the reviewer to compare whether names, quantities, dates, and signatures are consistent.
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 conclusion" is parsed from the response by subsequent nodes, or handled externally according to the agreement and then completed. The HTTP module sends a request to the target address. Path parameters, request body, and request headers can all use variable placeholders. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | The name, date, and signature must match the re-examination application and restricted-major notification | Take one exception record, check the candidate name, physical examination date, and physician signature in the physical examination form, then compare item by item with the other two materials |
| Re-examination application | The re-examination items, application date, and applicant signature must connect with the physical examination form conclusion | Check whether the re-examination application's items and date fall after the physical examination form conclusion, and whether the signature field is empty |
| Restricted-major notification | The restricted major name, notification date, and receipt must be consistent with the physical examination form conclusion | Check whether the restricted major name in the notification has the same name as the physical examination form conclusion, and whether the receipt is missing |
| Request body and variable sources | Fields are consistent with the external interface agreement, and every placeholder can be traced to its source | Use one sample request to compare the response, and check the sources of variables and Authorization in the variable panel |
Three common errors
- Symptom: the same candidate's name, quantity, or date does not match across two materials. Cause: during entry, data was not filled back using the same identifier and date criteria, so the original record and the basis for change are disconnected.
- Symptom: the version of the restricted-major notification is not synchronized with the physical examination form conclusion. Cause: the notification was issued first and the conclusion was changed later, and the two were not realigned under the same batch.
- Symptom: the re-examination application or notification receipt is missing a signature. Cause: the process entered review without collecting all signatures, so the chain of evidence breaks at the signature.
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; at the same time, check whether the fields returned in responseData are consistent with the external interface agreement.
Business test: create one exception record and see whether it can be traced back to the source materials, that is, from the exception list back to the corresponding entries in the physical examination form, re-examination application, and restricted-major notification.
- In the request preview, view the complete rendered address, check the value sources of path parameters and request headers, and confirm that the placeholders for
Authorizationandvariablescan both be parsed into actual values. - Use one sample request to compare the returned fields, check item by item whether the request body is consistent with the external interface agreement, and record the array length and the tokens budget of the referenced text.