What this category's data looks like
The core materials for material drafting and responsibility handover in social evaluation of vocational skill level certification include the evaluation implementation plan, candidate registration form, and assessor dispatch form. These materials come from submissions by evaluation institutions and assessors, and are updated on a rolling basis by batch. Fields cover candidate name, vocational level, assessor ID, evaluation date, signature, and receipt. When entering workflow orchestration, the evaluation implementation plan serves as the primary basis, while the candidate registration form and assessor dispatch form serve as attachment materials. Together, the three support the draftable materials and handover records. During the material drafting stage, it is necessary to verify that fields are complete, responsible parties are clear, and versions and dates are consistent. During the handover stage, it is necessary to confirm the receiving party and receipt status. Common field discrepancies are concentrated in the same record having mismatched names, quantities, or dates across two materials, unsynchronized versions, or missing signatures or receipts. When materials enter this function, they each assume the roles of basis, supporting evidence, and dispatch confirmation, and subsequent nodes continue execution according to branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Draftable materials and handover records" are completed by subsequent nodes continuing execution according to 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 |
|---|---|---|
| Evaluation implementation plan | Fields are complete, responsible parties are clear, versions and dates are consistent; check candidate name, vocational level, evaluation date, and signature field | Check the options and branch connections one by one in the node, confirm that the version number and evaluation date of the implementation plan are consistent, and that missing items are blocked |
| Candidate registration form | The same record has mismatched names, quantities, or dates across two materials; check the candidate name, quantity, and date in the registration form and implementation plan | Trigger an interaction once, view the node status in the run record, and check whether the candidate quantity and date in the registration form and implementation plan are consistent |
| Assessor dispatch form | Missing signature or receipt; check assessor ID, dispatch date, and receipt record | Reference variables and nodeId in subsequent nodes and run a trial once, confirm that the dispatch form signature and receipt are complete, and that missing items are blocked |
| Handover record | Version not synchronized; check handover date, receiving party, and receipt status | Run trials option by option, check the branch direction and interaction status in the run record, and confirm that the handover record version and date are consistent |
Three common errors
- Phenomenon: The same candidate name is written differently in the registration form and the implementation plan. Cause: During material drafting, the field source was not unified, and the two materials were entered separately, causing the names to mismatch.
- Phenomenon: The assessor dispatch form is missing a signature or receipt. Cause: The handover step did not set up receipt confirmation, and the dispatch form did not enter the next node for verification along the branch.
- Phenomenon: The implementation plan version is not synchronized, and the date is inconsistent with the registration form. Cause: After the version update, the interaction was not retriggered, and subsequent nodes still referenced the old branch direction.
How to verify the setup
This function's acceptance: run trials option by option, check the branch direction and interaction status in the run record, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and inspect the branch direction and interaction status records.
- Reference
variablesandnodeIdin subsequent nodes and run a trial once, confirm that the selection result variable has been passed to subsequent nodes, and that missing items are blocked.