What this category's data looks like
Teacher qualification exams and certification involve three types of materials: written and interview registration forms, Mandarin proficiency certificates, and medical examination forms. Sources are registration system exports, test institution issuances, and medical examination receipts from designated hospitals. The update cadence changes with exam batches, certification announcements, and certificate replacement or renewal. Registration forms contain name, ID number, exam subjects, exam district, and signature field; Mandarin proficiency certificates contain grade, test date, certificate number, and issuing institution seal; medical examination forms contain examination date, conclusion, physician signature, and hospital receipt. The three types of materials have different roles when entering the workflow: the registration form serves as the identity and subject baseline, the Mandarin proficiency certificate serves as the qualification condition credential, and the medical examination form serves as the certification validity credential. They need to be maintained uniformly according to the version ledger and change records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Written and interview registration form | Whether fields, dates, and signatures are consistent with the current version, and whether the name, quantity, and date of the same record match across the two materials | Check options and branch connections one by one in the node, reference variables for a trial run, and check the branch direction corresponding to nodeId |
| Mandarin proficiency certificate | Whether grade, test date, certificate number, and issuing institution seal are complete, and whether the old version can be traced | Reference the selection result variable in a subsequent node and run a trial once, then check the node status and branch direction in the run record |
| Medical examination form | Whether examination date, conclusion, physician signature, and hospital receipt are missing, and whether the version is synchronized | Trigger a user selection node once, and check the status of nodeId in the run record and whether the selection result variable has been passed to subsequent nodes |
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, versions are not synchronized, and there is no unified ledger and change record.
- Symptom: An old version of the Mandarin proficiency certificate is still referenced, and the current version is not unique. Cause: When updating the knowledge base or external documents, write-back was not performed according to the branch, and references were not synchronized.
- Symptom: The medical examination form is missing the physician signature or hospital receipt. Cause: When the material entered the workflow, the signature and receipt fields were not validated according to the branch, and it was released directly after the interaction was completed.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that the branch corresponding to nodeId and the transfer of variables are correct.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and confirm that the current version is unique, the old version can be traced, and references are synchronized.
- Check options and branch connections one by one in the node, trigger a user selection node once, and view the node status and selection result variable in the run record.
- Reference this variable in a subsequent node and run a trial once, confirm the branch direction and interaction state record, then update the knowledge base or external documents.