What this category's data looks like
Teacher qualification exam and certification materials include written and interview registration forms, Mandarin proficiency certificates, and medical examination forms. Their sources are registration system exports, test institution issuances, and designated hospital issuances, and their update cadence changes with batches and certification cycles. The registration form contains identity information, exam subjects, dates, and signatures; the Mandarin proficiency certificate contains grade, number, and issue date; the medical examination form contains conclusion, physician signature, and hospital receipt. When materials enter the exception tracing and manual review workflow, the registration form serves as the main record anchor, while the Mandarin proficiency certificate and medical examination form serve as comparison sources. Fields, dates, and signatures are checked item by item, and any inconsistency triggers the generation of an exception list and the flow of review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Exception list and review conclusion" is completed by subsequent nodes continuing execution according to the branch. When this node is triggered, the conversation enters an interactive 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 name, subject, date, and signature are consistent with the main record; missing signature or receipt is an exception | Check options and branch connections one by one in the node, reference variables, and run a trial once |
| Mandarin proficiency certificate | Whether grade, number, and issue date match what is filled in the registration form; if the version is not synchronized, it is an exception | Trigger the node once and check the node status and nodeId in the run record |
| Medical examination form | Whether conclusion, physician signature, hospital receipt, and registration form date are consistent; missing receipt is an exception | Reference the selection result variable in subsequent nodes and run a trial to check the branch direction |
| Exception list and review conclusion | Whether each exception is supported by original records and whether the reviewer has signed | After continuing execution according to the branch, trace back to the source materials and signature fields |
Three common errors
- Symptom: The name and date of the same record do not match between the registration form and the Mandarin proficiency certificate. Cause: The two materials were entered separately, and field-level comparison was not performed before entering review.
- Symptom: The version of the medical examination form was not synchronized, and the old conclusion is still referenced. Cause: After the material was updated, comparison was not re-triggered, and the workflow continued to use the historical branch direction.
- Symptom: The review conclusion lacks a signature or receipt, and the exception cannot be handed to the responsible person for handling. Cause: The branch did not reach the signature confirmation node, and the interaction state was not fully recorded.
How to verify the setup
Function acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that options and branches correspond one-to-one, that the selection result variable has been passed to subsequent nodes, and verify by referencing variables and nodeId.
Business test: create an exception record, see whether the source material can be traced, and confirm that the reviewer's signature and original record support are complete.
- Run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that no default branch is mistakenly taken.
- Reference the selection result variable in subsequent nodes and run a trial to check whether the exception list and review conclusion continue execution according to the branch.