What this category's data looks like
The filing and handover of enterprise independent skilled talent evaluation involves three types of materials: the enterprise evaluation filing form, the evaluation specification, and the candidate roster. The sources are the declaration unit's submission and the competent department's filing receipt, and the update cadence rolls with batches and evaluation cycles. The filing form carries the institution, occupation, level, and evaluation method; the evaluation specification carries the assessment modules, weights, and scoring criteria; the roster carries candidate identity, trade, level, and batch. When the three types of materials enter the workflow, their roles differ: the filing form serves as the prerequisite basis, the evaluation specification serves as the judgment benchmark, and the roster serves as the person-by-person verification checklist. When materials enter the drafting and handover stage, complete fields, clear responsible persons, and consistent versions and dates become the prerequisites for being issuable. Names, quantities, and dates must align across materials, and signatures and receipts must form a closed loop; otherwise, subsequent nodes cannot continue execution along the branches.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The issuable material drafts and handover records are completed by subsequent nodes continuing execution along the 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 |
|---|---|---|
| Enterprise evaluation filing form | Whether the institution name, occupation name, level, evaluation method, filing date, and signature are complete, and consistent with the evaluation specification | Verify field by field the filing form against the evaluation specification, check whether the institution and occupation names, level, and date align, whether signatures and receipts are complete; if any item is missing, stop at the interaction node and wait for completion |
| Evaluation specification | Whether the assessment modules, weights, scoring criteria, version number, and effective date are consistent with the filing form batch | Verify the occupation, level, and batch date of the evaluation specification against the filing form, check whether the version number is synchronized, use variables to record the batch and version, and run a branch trial once |
| Candidate roster | Whether candidate names, identity information, trade, level, and batch quantity are consistent with the filing form and evaluation specification | Verify person by person the names, quantities, and dates of the roster against the filing form and evaluation specification, check signatures and receipts; missing items are intercepted by the interaction node and nodeId is recorded |
| Handover record | Whether the responsible persons of both handover parties, handover date, version number, and receipt signature are clear and consistent with the material drafts | Verify the nodeId and branch direction of the handover record, check whether the responsible persons, date, and version are consistent with the material drafts; if the receipt is missing, return to the interaction state |
Three common errors
- Phenomenon: The same candidate's name, trade, and level do not match between the roster and the filing form. Cause: The two materials are filled in separately, there is no person-by-person cross-verification step, and fields enter the next stage without being aligned.
- Phenomenon: The evaluation specification has been updated to a new version, but the filing form and roster still use the old version date. Cause: The version number is not synchronized, a unified batch variable is not referenced during material drafting, and dates and versions are disconnected.
- Phenomenon: The handover record lacks a signature or receipt, yet the material draft has already flowed to the next stage. Cause: The interaction node did not intercept the missing item, and execution continued along the default branch before the responsible person was clarified.
How to verify the setup
Acceptance of this function: trial-run each option one by one, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, that the process does not stall after interaction is completed, and that the same session does not repeatedly enter interaction.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are intercepted.
- In the node, verify the options and branch connections one by one, confirm that each option corresponds to one branch, and use
variablesandnodeIdto record the selection result and node status. - Trigger the user selection node once, view the interaction status and branch direction in the run records, confirm that the selection result variable has been passed to subsequent nodes, and run a trial once.