What this category's data looks like
In the professional and technical personnel vocational qualification examination registration review scenario, materials are mainly of three types: registration form, education certificate, and work experience certificate. Sources are online completion and upload by candidates and reuse of historical registration records. The update cadence rolls with registration batches. Field characteristics center on names, quantities, dates, and signature receipts. The registration form carries basic personal information, examination subjects, and employer opinion; the education certificate carries graduation institution, major, certificate number, and date of obtaining; the work experience certificate carries start and end dates, position name, and employer seal. When the three types of materials enter workflow nodes, each serves a verifiable-field supply role: the registration form provides identity and examination level, the education certificate provides the basis for qualification thresholds, and the work experience certificate provides the basis for calculating years of experience. Fields must be cross-compared. If any material lacks a signature, lacks a receipt, or has an unsynchronized version, it will be exposed during intake as an item requiring follow-up.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Intake records and items to be completed" are continued and completed by subsequent nodes according to the branch. When a 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 |
|---|---|---|
| Registration form | Whether the name, quantity, date, and signature are consistent with the education certificate and work experience certificate | Check the name, ID number, examination subjects, employer opinion signature, and date; compare item by item in the node and record the variables reference result |
| Education certificate | Whether the graduation institution, major, certificate number, and date of obtaining are consistent with the registration form | Check the certificate number, date of obtaining, and major name; run a trial once to view the branch and interaction state corresponding to nodeId |
| Work experience certificate | Whether the start and end dates, position name, employer seal, and receipt are complete | Check whether the start and end dates match the years filled in the registration form, and inspect the seal and receipt; if any item is missing, enter the follow-up branch |
| User selection node | Whether each option corresponds to one branch, and whether the selection result variable is passed to subsequent nodes | Run a trial for each option one by one, check the branch direction and interaction state in the run record, and confirm that the subsequent node reference to variables takes effect |
Three common errors
- Symptom: The name and date for the same record do not match between the registration form and the work experience certificate. Cause: The two materials were filled in separately, without cross-comparison and version synchronization.
- Symptom: The education certificate version is not synchronized, and the old certificate number is inconsistent with the new registration form. Cause: After the material was updated, re-verification was not triggered, and the historical cache continued to be used.
- Symptom: The work experience certificate lacks a signature or receipt, but answering still proceeds after intake. Cause: The missing item was not identified as a follow-up condition, and the branch directly took the default path.
How to verify the setup
Acceptance for this feature: run a trial for each option one by one, and check the branch direction and interaction state in the run record; confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the subsequent node references variables and nodeId and is run once more.
Business test: submit a question missing key information and see whether it first asks a follow-up before answering; check whether the follow-up items correspond to missing items in the registration form, education certificate, or work experience certificate, and whether the answer has a material basis.
- In the user selection node, check the options and branch connections one by one, and confirm that each option corresponds to one branch, with no default branch fallback.
- Trigger one interaction, view the node state and interaction state in the run record, and confirm that the selection result variable has been passed to subsequent nodes and takes effect in a trial run.