What this category's data looks like
The materials for the review of professional and technical personnel vocational qualification examination registration mainly consist of the registration form, education certificate, and work experience certificate. They come from candidates' submissions and employers' issuance. The update rhythm is concentrated submission during the examination season, with batches rolling. The registration form contains name, ID number, examination subjects, work unit, date, and signature; the education certificate contains school name, major, graduation date, and certificate number; the work experience certificate contains start and end dates, position, employer seal, and receipt. When these three types of materials enter workflow orchestration, their roles differ: the registration form provides identity and subject fields, the education certificate provides education and major fields, and the work experience certificate provides date and position fields, jointly supporting the determination of the visible scope for authorized access and external services.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are continued and completed by subsequent nodes according to the branches. When triggered, the conversation enters an interaction state and records the workflow status. After the user completes the selection, the corresponding option's branch is followed for continued execution.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether name, ID number, examination subjects, work unit, date, and signature are consistent with the same record in the education certificate and work experience certificate | Compare the name, quantity, date, and signature of the three materials item by item, check whether the variables reference points to the same record, and check whether the branch corresponding to nodeId proceeds according to the selection result |
| Education certificate | Whether school name, major, graduation date, and certificate number are consistent with what is filled in the registration form | Check whether the graduation date connects with the start and end dates of the work experience certificate, check whether this field in variables has been passed to subsequent nodes, and run a trial once |
| Work experience certificate | Whether start and end dates, position, employer seal, and receipt are complete and match the dates in the registration form | Check whether the seal and receipt are missing, check whether the branch connections of nodeId correspond one-to-one with the options, and check whether variables records the selection result |
| Externally available entry points and authorization scope | Whether the visitor's identity matches the visible scope, and whether unauthorized access is invisible | Trigger a user selection node once with a restricted identity, check the branch direction and interaction status in the run record, and check whether variables is passed to subsequent nodes |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the registration form and the work experience certificate. Cause: The two materials are filled in separately, versions are not synchronized, and node branches are not checked against the same record.
- Phenomenon: The graduation date and major name in the education certificate and the registration form are inconsistent. Cause: The material update rhythms differ, the old version has not been replaced, and after the interaction is completed, the process continues along the default branch.
- Phenomenon: The work experience certificate lacks a signature or receipt. Cause: The issuing unit omitted filling it in, the node did not record the interaction status, and repeated entry into the interaction in the same session causes branch direction confusion.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction status in the run record, and check whether variables and nodeId continue execution along the branch corresponding to the option.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and unauthorized access is invisible.
- In the node, check the options and branch connections one by one, and check whether the references of
nodeIdandvariablesare consistent. - Trigger a user selection node once, and view the node status and interaction status records in the run record.