What this category's data looks like
The materials for social assessment of vocational skill level certification mainly consist of the assessment implementation plan, candidate registration forms, and assessor dispatch forms. The sources are the declaring institutions and assessment organizations, and the update cadence advances with each batch. The assessment implementation plan gives the occupational direction, level, and process nodes; the candidate registration forms carry identity, application conditions, and contact information; the assessor dispatch forms record personnel, dates, and signatures. When these three types of materials enter workflow orchestration, the assessment implementation plan determines the branch direction, while the candidate registration forms and assessor dispatch forms serve as the basis for verification at subsequent nodes, and the fields, dates, and signatures must be aligned item by item.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction status records. The "handover-ready deployment status and operation records" are continued and completed by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Assessment implementation plan | The occupational direction, level, process nodes, and dates must be consistent with the registration forms and dispatch forms, and signatures and receipts must be complete | Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records |
| Candidate registration forms | Identity, application conditions, dates, and signatures must match the implementation plan and dispatch forms, and the quantities must be consistent | Reference the selection result variable in a subsequent node and run a trial once, and check variables and nodeId |
| Assessor dispatch forms | Personnel, dates, signatures, and receipts must be consistent with the implementation plan and registration forms, and names must not be mixed up | Trigger one interaction, check the branch direction and interaction status in the run records, and record nodeId |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the implementation plan and the registration forms. Cause: The materials are updated separately, lacking item-by-item comparison and receipt confirmation.
- Symptom: The version is not synchronized, and the dispatch forms still use the personnel and dates of an old batch. Cause: The update cadence is not synchronized, and the version and signatures are not checked during handover.
- Symptom: Signatures or receipts are missing, and the process stops after the interaction is completed. Cause: The options and branches are not checked one by one, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
This feature's acceptance: run trials on each option one by one, check the branch direction and interaction status in the run records, and confirm that variables and nodeId records are complete.
Business testing: check item by item once according to the handover form, see which record is missing, and check whether the version, connections, and task records are consistent.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, and check whether
variablesandnodeIdare passed in according to the branch.