What this category's data looks like
This category's data covers three types of materials: written and interview registration forms, Putonghua proficiency certificates, and medical examination forms. Sources are registration system exports, test institution issuances, and designated hospital issuances, with update cadence rolling with batches and certification seasons. Registration forms contain identity, subject, and test area fields; Putonghua proficiency certificates contain grade, test date, and certificate number; medical examination forms contain examination conclusion, physician signature, hospital stamp, and date. When materials enter the workflow, the registration form serves as the main record anchoring the candidate's identity and batch, while the Putonghua proficiency certificate and medical examination form serve as supporting materials providing grade and conclusion. Field conventions must align with the main record, signatures and receipts serve as completeness evidence, and dates and names must be traced back to the source text item by item, forming a comparable unified terminology glossary and comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Written and interview registration form | Check identity, subject, test area fields and registration date, confirm signatures and receipts are complete | Check options and branch connections one by one in the node, trigger once to view node status in the run records |
| Putonghua proficiency certificate | Check grade, test date, certificate number match the name on the registration form, confirm issuance information can be traced back to the source text | Reference the selection result variables in subsequent nodes and do a trial run, check the branch direction |
| Medical examination form | Check examination conclusion, physician signature, hospital stamp and examination date, confirm missing items and version synchronization status | Compare nodeId with branch connections in the run records, confirm interaction state is recorded |
| Unified terminology glossary and comparison draft | The same term is consistent throughout, translated names can be traced back to the source text, sample three terms to check whether the writing is consistent throughout | Compare material fields item by item before delivery, confirm names, quantities, and dates match |
Three common errors
- Phenomenon: The same candidate's name is written differently on the registration form and the Putonghua proficiency certificate. Cause: The two materials are exported by different systems, and unified terminology mapping and trace-back verification were not performed.
- Phenomenon: The medical examination form date does not match the registration batch date. Cause: Versions were not synchronized, and an old version medical examination form entered the process together with new batch materials.
- Phenomenon: The medical examination form lacks a physician signature or the registration form lacks a receipt. Cause: The material collection step did not verify completeness, and signature and receipt fields were not included in the check.
How to verify the setup
This feature acceptance: trial run each option one by one, check the branch direction and interaction state in the run records, confirm options correspond to branch connections, and the selection result variable has been passed to subsequent nodes.
Business test: sample three terms to check whether the writing is consistent throughout, confirm the same term is consistent throughout and translated names can be traced back to the source text.
- Check options and branch connections one by one in the node, trigger once to view node status in the run records.
- Reference the selection result
variablesin subsequent nodes and do a trial run, check the branch direction corresponding tonodeId.