What this category's data looks like
This category's data covers three types of materials: written and interview registration forms, Putonghua certificates, and medical examination forms. The registration form contains name, ID number, examination subjects, examination district, payment and signature fields; the Putonghua certificate contains certificate number, grade, issue date, and seal; the medical examination form contains examination items, conclusion, hospital signature/seal, and date. The materials come from the registration system, testing institutions, and medical examination hospitals, with an update rhythm of concentrated submission during the registration period and concentrated verification before certification. When the three types of materials enter workflow orchestration, the registration form serves as the main record to initiate progress, while the Putonghua certificate and medical examination form serve as attachment branches to supplement fields; nodes split the flow by material type and then aggregate it into a progress table and statistical scope description.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statistical scope description" is then completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and records the workflow status; 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 | Fields include name, ID number, examination subjects, examination district, payment and signature; the date must match the registration deadline; the signature field must not be empty | In the node, check the options and branch connections one by one, confirm that the registration form follows the main record branch, and reference variables to pass it to subsequent nodes |
| Putonghua certificate | Fields include certificate number, grade, issue date, and seal; the name must match the name on the registration form; the quantity is counted by the number of certificate pages | Trigger a user selection once, view the node status in the run record, and check whether the certificate branch enters the corresponding connection according to material type |
| Medical examination form | Fields include examination items, conclusion, hospital signature/seal, and date; the conclusion must be qualified; the date must be within the certification validity period | In a subsequent node, reference the selection result variable and run a trial once, and check whether the medical examination form branch matches the registration form's date and name |
| Progress table and statistical scope description | The number of records matches the statistical count, the scope is written in the header, and exceptions are noted one by one | Use one week of records to check the totals, and view whether the branch direction corresponding to nodeId is consistent with the interaction status records |
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 entered separately, versions are not synchronized, and there is no unified receipt verification.
- Symptom: The Putonghua certificate number and the number of referenced numbers on the registration form are inconsistent. Cause: Certificate pages are not registered page by page, the statistical scope is not written in the header, and the total shows a deviation.
- Symptom: The medical examination form lacks a hospital signature/seal or the registration form lacks a signature. Cause: After material submission, interaction status review is not triggered, branch directions are not recorded, and subsequent nodes cannot determine completeness.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and run a trial once in a subsequent node referencing variables and nodeId.
Business testing: use one week of records to check the totals and see whether the scope and exceptions are clearly written; check whether the names, quantities, dates, and signatures of the registration form, Putonghua certificate, and medical examination form are consistent, and whether the number of records matches the statistical count.
- In the node, check the options and branch connections one by one, trigger a user selection once, view the node status in the run record, and confirm that the process continues downward after the interaction is completed.
- In a subsequent node, reference the selection result variable and run a trial once, check the fields, dates, and signatures of the registration form, Putonghua certificate, and medical examination form, write the scope in the header, and note exceptions.