What this category's data looks like
Enterprise independent skill talent evaluation generates multiple types of materials during filing and implementation: enterprise evaluation filing forms, evaluation specifications, candidate rosters, and conversation records and receipts from the evaluation process. The filing form contains enterprise information, evaluation occupation, level, and signature fields; the evaluation specification contains assessment methods, scoring elements, and dates; the roster contains candidate names, identity information, applied level, and quantity. These materials are updated by batch and evaluation cycle, with field characteristics concentrated in four places: name, quantity, date, and signature. When the materials enter the conversation record function, the filing form and specification serve as background basis, the roster serves as the candidate dimension reference, and the conversation records serve as process evidence, used to check whether questions and answers are consistent with the materials.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimension), outputting a session message list and total record count, including role and reference information. The version ledger and change records are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Conversation record interface | The application and session identifiers match reality, and the paginated record count matches the total record count | Check the source of chatId in the request parameters, pull two pages consecutively to compare the offset and the total record count total, confirm the list is non-empty when the status code is 200, and confirm a single record contains dataId and value |
| Enterprise evaluation filing form | The filing form fields, dates, and signatures match the evaluation specification and roster | Check the name, quantity, date, and signature fields item by item, and confirm that the same record does not show inconsistent names or quantities across the two materials |
| Evaluation specification | The assessment methods, scoring elements, and dates in the specification are the current version, and the old version is traceable | Check the specification version number and reference locations, and confirm that after changing one piece of content, the version number and references are updated in sync |
| Candidate roster | The roster headcount, applied levels are consistent with the filing form and specification, and signatures or receipts are complete | Compare the quantity and dates between the roster and the filing form, check entries missing signatures or receipts, and register them |
Three common errors
- Phenomenon: The same candidate's name, quantity, or date does not match between the roster and the filing form. Cause: The two materials are registered separately, no cross-check is performed, and versions are not synchronized.
- Phenomenon: The evaluation specification has been updated, but references still point to the old version. Cause: The version ledger has not registered the change, reference locations have not been replaced in sync, and the old-version traceability chain is broken.
- Phenomenon: The filing form or receipt is missing a signature. Cause: No signature confirmation is set up in the material circulation step, receipts are not collected, resulting in incomplete records.
How to verify the setup
This function acceptance: paginate through all records by the total record count total, sample one record to check the role, reference information, and time; when the status code is 200, the list contains two role types, questions and answers, and a single record contains dataId and value.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- Pull records by application and session dimension, check that
chatIdmatches the actual session, and paginate through all records up to the total record count total. - Open a single record to check the role, reference, and elapsed time fields; record the reference count by array length, and check the tokens of the reference text separately.