What this category's data looks like
Teacher qualification exams and certification involve written and interview registration forms, Mandarin proficiency certificates, medical examination forms, and other materials. The registration form contains name, ID number, exam subjects, exam district, and date; the Mandarin proficiency certificate contains grade, certificate number, and issue date; the medical examination form contains examination conclusion, physician signature, and hospital seal. The material sources are candidate uploads and certification authority archiving, and the update cadence changes with registration batches, certificate issuance, and medical examination validity periods. When entering the Q&A acceptance and missing-item follow-up function, the registration form is used to verify identity and subjects, the Mandarin proficiency certificate is used to verify grade and number, and the medical examination form is used to verify conclusion and signature. The fields of the three materials are cross-compared, and names, quantities, dates, and signatures must be consistent; any missing item triggers a follow-up question.
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 acceptance 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. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Written and interview registration form | Name, subjects, date, and signature are consistent within the registration form, and cross-comparison with the Mandarin proficiency certificate and medical examination form shows no conflict | Verify the registration form fields and signature, compare the name and date in the two materials, and mark inconsistent items |
| Mandarin proficiency certificate | Grade, certificate number, and issue date are traceable, and match the name on the registration form | Verify the certificate number and issue date, check whether the signature or receipt is missing, and record items pending follow-up |
| Medical examination form | Examination conclusion, physician signature, and hospital seal are complete, and the date is within the validity period | Verify the signature and seal, compare the date with the registration form batch, identify missing items, and generate follow-up questions |
| HTTP request | The request URL and path parameter placeholder variables can be resolved into actual values, and the request header authentication information is passed in according to the external system's requirements | View the rendered complete URL in the request preview, verify the request header names and value sources, and compare the returned fields using a sample request |
Three common errors
- Symptom: The name or date for the same record does not match between the registration form and the Mandarin proficiency certificate. Cause: The two materials were entered separately, without cross-comparison and version synchronization.
- Symptom: The external system receives empty fields or the request returns 401. Cause: The request body fields are inconsistent with the interface agreement, or the authentication information was not passed in according to the external system's requirements.
- Symptom: The medical examination form is missing the physician signature or receipt, and the follow-up question is not triggered. Cause: The missing-item identification rules do not cover the signature and receipt fields, and the acceptance record does not mark the items pending completion.
How to verify the setup
Acceptance for this function: preview the rendered request, verify the status code and returned fields, then compare the result against one sample; check whether the Authorization request header, the variables variable sources, and the responseData returned fields are consistent with the agreement.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the variables panel, verify the source of each placeholder and confirm whether it comes from a global variable, system variable, or the output of a preceding node.
- Use one sample request to compare the returned fields and check whether the request body fields are consistent with the external interface agreement.