What this category's data looks like
Materials for progress records and statistical verification of enterprise independent skilled-talent evaluation come from three types: enterprise evaluation filing forms, evaluation specifications, and candidate rosters. The filing form records the evaluation occupation, level, batch, and planned dates; the evaluation specification states the assessment method, scoring criteria, and passing standard; the roster lists candidate names, ID numbers, examination subjects, and batch affiliation. When the three types of materials enter the workflow, their roles differ: the filing form and evaluation specification serve as sources of criteria, the roster serves as the source of records, and the progress table aligns the two by batch and date. The update rhythm advances with the batch: after registration closes, the roster is finalized; after the assessment ends, the criteria in the evaluation specification are used for statistical totals; the dates in the filing form are used to verify progress milestones. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. The way the same candidate's name is written in the roster and the filing form, the quantity of the same batch in the two materials, and the dates of the same assessment stage all need the criteria and exceptions clearly stated in the progress table header.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction-state records. The "progress table and statistical criteria description" is continued and completed by subsequent nodes according to the branch. After the user completes the selection, the conversation follows the corresponding option to continue execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | Check whether the evaluation occupation, level, batch, and planned dates are consistent with the evaluation specification, and whether signatures and receipts are complete | Compare the occupation name, level, and batch dates in the filing form and evaluation specification one by one, check the signature field and receipt attachment, and verify the node pointed to by nodeId |
| Evaluation specification | Check whether the assessment method, scoring criteria, and passing standard correspond to the batch in the filing form | Check the options and branch connections one by one in the node, confirm that the criteria source points to the same batch, and verify the variables references |
| Candidate roster | Check whether candidate names, ID numbers, examination subjects, and batch affiliation match the quantities and dates in the filing form | Use one week of records to verify the totals, view the node status and branch direction in the run records, and verify variables and nodeId |
| Progress table and statistical criteria description | Check whether the header clearly states the statistical criteria and exceptions, and whether the record count and statistical count match | Reference the selection result variable in subsequent nodes and run a trial once, and verify the totals and criteria |
Three common errors
- Phenomenon: the same candidate's name, quantity, and dates do not match between the roster and the filing form. Cause: the two materials are maintained separately, and the criteria are not uniformly verified by batch.
- Phenomenon: the evaluation specification version is not synchronized, and the old criteria are still used for statistics. Cause: after the version update, the node branch does not point to the new version, and subsequent nodes continue to use the old variables.
- Phenomenon: the filing form lacks a signature or receipt, but the progress table still includes it in the totals. Cause: signatures and receipts are not included in the verification items, and exceptions are not stated in the header.
How to verify the setup
Feature acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run records, confirm that the options and branch connections are consistent and that the selection result variable has been passed to subsequent nodes, and verify variables and nodeId.
Business testing: use one week of records to verify the totals, see whether the criteria and exceptions are clearly stated, and whether the record count and statistical count match.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, confirm that the interaction state is recorded, and verify
nodeId. - Reference the selection result variable in subsequent nodes and run a trial once, verify whether the branch direction and statistical totals are consistent, and verify
variables.