What this category's data looks like
The materials for the review of professional and technical personnel vocational qualification examination registration include the registration form, education certificate, and work experience certificate. They are mostly filled in by the candidate and then stamped by the employer or archival institution, and are updated in batches or on a weekly basis. The registration form contains fields such as name, ID number, examination subjects, and employer; the education certificate contains the graduating institution, major, certificate number, and issue date; the work experience certificate contains start and end dates, position, and signature. When the three types of materials enter the workflow, the registration form serves as the primary record source, while the education certificate and work experience certificate serve as cross-check sources, and branches driven by user selection nodes determine which verification path the materials enter. Field characteristics center on date formats, name spellings, the presence or absence of signatures and receipts, and whether the quantities and dates of the same record are consistent across different materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. 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. The progress table and statistical scope description are then completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether fields, dates, and signatures are complete, and whether the name and quantity of the same record are consistent with the other two materials | Check the options and branch connections one by one in the user selection node, use variables to reference the selection result variable, and trial-run in subsequent nodes and view the run record corresponding to nodeId |
| Education certificate | Whether the graduating institution, major, certificate number, and issue date match what is filled in on the registration form, and whether the version is synchronized | Trigger an interaction state once, view the node status in the run record, and check whether the selection result variable has been passed to subsequent nodes |
| Work experience certificate | Whether the start and end dates, position, and signature or receipt are complete, and whether they are consistent with the work experience filled in on the registration form | Reference the selection result variable in a subsequent node and trial-run once, confirm that the selected branch differs from the default branch, and check whether the same session repeatedly enters interaction |
| Progress table and statistical scope description | Whether the number of records matches the statistical count, whether the scope is written in the header, and whether exceptions are clearly stated | Use one week of records to check the totals, compare the scope and exception descriptions, and confirm that the progress table and statistical scope description are completed by subsequent nodes continuing execution along the branch |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the registration form and the education certificate. Cause: The two are entered separately without cross-checking, and the versions are not synchronized.
- Symptom: The work experience certificate lacks a signature or receipt, but the registration form has already been marked complete. Cause: Material collection and verification belong to different stages, and the process advances before the receipt is returned.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Acceptance of this feature: trial-run each option one by one, check the branch direction and interaction state in the run record, and confirm that variables has been passed and that the record corresponding to nodeId can be queried.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly stated.
- In the user selection node, check the options and branch connections one by one, trigger an interaction state once, and view the run record.
- Reference the selection result variable in a subsequent node and trial-run, confirm that the selected branch differs from the default branch, and that the same session does not repeatedly enter interaction.