What this category's data looks like
The exception tracing and manual review for enterprise independent skill talent evaluation revolves around three types of materials: enterprise evaluation filing forms, evaluation specifications, and candidate rosters. Filing forms come from human resources and social security department filing receipts and internal approvals, and are updated by evaluation batch; evaluation specifications come from the item-setting and assessment group, and are re-versioned as occupational standards or item banks are adjusted; rosters come from registration and examination affairs systems, and are generated on a rolling basis by session. When the three types of materials enter the form input node, their roles differ: the filing form provides batch and institution fields, the evaluation specification provides occupation, level, and assessment method fields, and the roster provides candidate name, ID number, declared level, and score fields. Exception tracing requires that each record in the exception list be traced back to the original fields, dates, and signatures of these three types of materials, and the review conclusion is then handed to the responsible person for disposition.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The "exception list and review conclusion" is completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | The filing batch, evaluation institution, filing date, and handler signature must match the evaluation specification and roster; name and quantity fields must not be inconsistent between the two materials | Check field names one by one in the node configuration, compare batch number, institution name, and date item by item against the original filing form, and if signatures or receipts are missing, record them in the exception list |
| Evaluation specification | The occupation name, level, assessment method, and version number must be consistent with the declared information in the roster; if the version is not synchronized, the currently effective version shall prevail and be documented | Check the required markers and confirm that the version number field is marked as required; reference this field in subsequent nodes and run a trial, comparing the specification version with the version referenced in the roster |
| Candidate roster | Candidate name, ID number, declared level, score, and date must correspond one by one with the filing form and evaluation specification; the quantity and date of the same record must not fail to match | Check field names one by one in the node configuration, extract one exception record and trace it back to the original row in the roster, and check whether signatures and receipts are complete |
| Form fields and submission transfer | Field names correspond one-to-one with the material fields to be collected, key fields are marked as required, and subsequent nodes can retrieve the corresponding field values after submission | Use formInputResult and selectResult to check field names and required settings one by one, reference this field in subsequent nodes, and run a trial |
Three common errors
- Phenomenon: The declared level or number of people for the same candidate does not match between the roster and the filing form. Cause: The two materials are maintained separately by the registration and examination affairs steps, and no item-by-item comparison was made.
- Phenomenon: After the evaluation specification is re-versioned, the roster still references the old version number. Cause: The version was not synchronized, and the node fields did not record the currently effective version.
- Phenomenon: Exception records lack handler signatures or receipts, and the review conclusion has no basis. Cause: Material archiving is incomplete, and signature and receipt fields were not checked at submission.
How to verify the setup
Acceptance of this function: fill it out once and submit, check the field values retrieved by subsequent nodes, confirm that field transfer after submission via formInputResult and selectResult is normal, and that submission is not allowed when required items are empty.
Business test: create one exception record, see whether it can be traced to the source materials, and check the names, quantities, dates, and signatures of the filing form, evaluation specification, and roster.
- Check field names and required markers one by one in the node configuration, and confirm that they correspond one-to-one with the fields of the filing form, evaluation specification, and roster.
- Reference the submitted fields in subsequent nodes and run a trial, compare the names, quantities, and dates of the same record in the two materials, and if signatures or receipts are missing, supplement them.