What this category's data looks like
This page focuses on the filing materials for enterprise independent skilled talent evaluation. The category materials include the enterprise evaluation filing form, the evaluation specification, and the candidate roster. The filing form records the evaluation institution, occupation name, level, and filing date; the evaluation specification provides the assessment method, scoring criteria, and signature field; the roster lists candidate names, ID numbers, declared levels, and units. When the three types of materials enter the workflow, their roles differ: the filing form and evaluation specification serve as basis sources, while the roster serves as the personnel scope source, and all must enter according to the current version. In terms of update cadence, the filing form is synchronized with filing changes, the evaluation specification is updated with standard adjustments, and the roster is submitted by batch. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. When cross-checking materials, attention must be paid to whether the same record is expressed consistently across the three materials, whether the version is current, and whether signatures and receipts are complete.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. Basis items that can be traced back to the original text are continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | Fields include evaluation institution, occupation name, level, filing date, and signature; the name, quantity, and date of the same record in the roster must be consistent, and the version must be current | In the node, check the options and branch connections. After triggering once, view the node status in the run record to confirm that the branch direction corresponds to the filing form fields |
| Evaluation specification | Fields include assessment method, scoring criteria, and signature field; the occupation name, level, and date must match those in the filing form. Missing signature or receipt is considered incomplete | In subsequent nodes, reference variables and nodeId for a trial run, and check whether the specification item can be traced back to its original text location |
| Candidate roster | Fields include candidate name, ID number, declared level, and unit; the name, quantity, and date must be consistent with those in the filing form and evaluation specification, and the version must be synchronized | After triggering one interaction, check whether the selection result variable has been passed to subsequent nodes, and verify the correspondence between roster items and the original text |
| User selection node | Each option corresponds to one branch; the interaction status is recorded when entering the node; the selection result variable must be passed to subsequent nodes | Run trial runs for each option one by one, check the branch direction and interaction status in the run record, and confirm that there is no mistaken default branch, process halt, or repeated entry into the interaction |
Three common errors
- Phenomenon: the same candidate name is written differently in the roster and the filing form. Cause: the two materials are entered in different steps, and the names were not uniformly proofread, so the basis items cannot be traced back to the same original text.
- Phenomenon: the evaluation specification version is not synchronized, and the old scoring criteria are still referenced. Cause: the specification was not updated after the filing change, and the unsynchronized version causes the basis items to correspond to expired content.
- Phenomenon: the filing form lacks a signature or receipt, and the roster quantity does not match the filing form. Cause: signatures were missed or receipts were not uploaded during submission, and the quantity was not checked by batch, resulting in incomplete basis items.
How to verify the setup
This function's acceptance: run trial runs for each option one by one, and check the branch direction and interaction status in the run record; check whether variables and nodeId are passed as expected, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: ask a cross-material basis question, see whether the answer provides a traceable source, and check whether the source can match the original text locations, versions, and signatures of the enterprise evaluation filing form, evaluation specification, and candidate roster.
- In the user selection node, check the options and branch connections one by one. After triggering once, view the node status and branch direction in the run record.
- In subsequent nodes, reference
variablesandnodeIdfor one trial run, and check whether the fields, dates, and signatures of the enterprise evaluation filing form, evaluation specification, and candidate roster are consistent.