What this category's data looks like
When handling inquiries, a college admissions physical examination organization receives three types of materials at the same time: physical examination forms, re-examination applications, and restricted-major notifications. The physical examination form records fields such as height, vision, past medical history, and the physician's signature; the re-examination application includes the application date, re-examination items, and the candidate's signature; the restricted-major notification contains the notification date, the name of the restricted major, and the receipt signature. These materials are aggregated in batches by the admissions office or the physical examination station and are updated along with admissions milestones. When entering the Q&A intake and missing-item follow-up function, the physical examination form serves as the main record, while the re-examination application and restricted-major notification serve as supplementary evidence; if the name, quantity, or date of the same record does not match across the two materials, or if the version is not synchronized, or signatures and receipts are missing, the intake record will be marked as having missing items, triggering follow-up questions.
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 intake record and the completed follow-up items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Whether the name, physical examination date, restricted conclusion, and physician's signature are complete, and whether the name, quantity, and date of the same record are consistent across the two materials | In the request preview, view the fully rendered address, check whether the request body fields are consistent with the external interface agreement, and compare the return using a sample request |
| Re-examination application | Whether the application date, re-examination items, candidate's signature, and receipt have missing items, and whether the version is synchronized with the physical examination form | Check the request header names and the sources of their values, and in the variables panel verify whether each placeholder comes from a global variable, system variable, or the output of a preceding node |
| Restricted-major notification | Whether the notification date, restricted major name, and receipt signature are complete, and whether the name and quantity match the physical examination form | Use variables to trace the origin of placeholders, and confirm that the fields returned by responseData can correspond to the missing-item follow-up |
Three common errors
- Symptom: The same candidate's name, item quantity, or date does not match between the physical examination form and the re-examination application. Cause: The two materials are entered separately, and field comparison is not performed against the same record.
- Symptom: The version of the restricted-major notification is not synchronized, and the receipt is missing a signature. Cause: Materials are updated in batches, an old version is still referenced, and the signature step is not returned.
- Symptom: The request returns 401, or the external system receives empty fields or the request times out. Cause: Authentication information is not passed in as required by the external system, and placeholder variables are not resolved into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that Authorization, variables, and responseData are all traceable.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder and confirm that the request address and path parameters can be resolved into actual values.
- Compare the return using a sample request, check that the request body fields are consistent with the external interface agreement, and check whether the missing-item follow-up is recorded in the intake record.