What this category's data looks like
The materials for the teacher qualification exam and certification fall into three categories: written and interview registration forms, Mandarin proficiency certificates, and medical examination forms. The registration form fields include name, ID number, exam subjects, and exam district; the dates are the registration and review dates; the signature fields require signatures from the candidate and the reviewer. The Mandarin proficiency certificate includes grade, certificate number, test date, and issuing authority; it has no signature field, but the certificate number and grade correspondence must be verified. The medical examination form includes examination items, conclusion, examination date, and physician signature; both the signature and the receipt are indispensable. When these three types of materials enter the HTTP interface and external systems, the registration form serves as the main record driving the version ledger, while the Mandarin proficiency certificate and medical examination form participate in version comparison as attachment fields. The update cadence changes with certification batches and policy adjustments; old versions must remain traceable, and references must be synchronized to the knowledge base or external documents. The field characteristics are many dates and many signature fields, and the names and quantities of the same record across different materials must be aligned.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "version ledger and change records" are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables; authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Written and interview registration form | Fields, dates, and signatures are complete, and the name, ID number, and dates match those in the Mandarin proficiency certificate and medical examination form | In the request preview, view the fully rendered URL, verify that the registration form fields match the external interface agreement, and check the sources of Authorization and variables |
| Mandarin proficiency certificate | The certificate number, grade, and test date do not conflict with the registration form and medical examination form records | Use one sample request to compare the response, verify the certificate number and grade fields in responseData, and confirm that the old version is traceable and references are synchronized |
| Medical examination form | The examination conclusion, examination date, physician signature, and receipt are complete, and align with the registration form dates | Verify the request header names and value sources, check whether the signature and receipt fields are updated with the version number, and avoid date mismatches for the same record |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are updated synchronously | After changing one piece of content, verify each placeholder source in the variables panel, and confirm that the version number and references are updated synchronously |
Three common errors
- Symptom: The name and date of the same record do not match between the registration form and the medical examination form. Cause: The two materials are maintained separately, the HTTP node request body fields are not aligned with the version ledger, and references are not synchronized.
- Symptom: The Mandarin proficiency certificate grade is inconsistent with the registration form record, and the old version is still referenced. Cause: The version is not synchronized, the change record is not written back, and subsequent nodes retrieve old fields when parsing the response.
- Symptom: The medical examination form lacks a physician signature or receipt, and the external system receives empty fields. Cause: The request body does not include the signature and receipt fields, or the variable placeholders resolve to empty, and missing authentication information causes a 401 response.
How to verify the setup
This feature's acceptance: preview the rendered request, verify the status code and returned fields, check whether the registration form, Mandarin proficiency certificate, and medical examination form fields in responseData are complete, then compare the result against one sample to confirm that Authorization and variables are parsed correctly.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the request preview, view the fully rendered URL and verify whether the path parameters, request headers, and variable placeholders in the request body resolve to actual values
- Use one sample request to compare the response, and check whether the fields, dates, and signatures of the registration form, Mandarin proficiency certificate, and medical examination form in
responseDatamatch the external system agreement