What this category's data looks like
This page is intended for enterprise compliance and security training scenarios. The materials include three categories: compliance training courseware, security operating procedures, and exam records. Compliance training courseware is updated by course version and release batch, with fields including course name, applicable position, effective date, author, and approval signature; security operating procedures are iterated by equipment or process version, with fields including procedure number, operating steps, risk level, revision date, and responsible person's signature; exam records are generated by session, with fields including examinee, exam paper version, score, exam date, and invigilation receipt. When these three categories of materials enter the conversation logs and audit feature, courseware and procedures are cited as knowledge sources, and exam records are compared with business results and citation information. During exception tracing, first locate the session message, then trace back to check whether the fields, dates, and signatures of the corresponding courseware, procedures, and exam records are consistent.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and the total number of records, including roles and citation information. The "exception list and review conclusions" are then completed manually or by an external system, for registration, export, and review.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Course name, applicable position, effective date, author, and approval signature are consistent across versions | Pull records by application and session dimension, and check the courseware name, effective date, and signature field corresponding to the cited text |
| Security operating procedures | Procedure number, operating steps, risk level, revision date, and responsible person's signature are consistent with the version cited in the exam records | Open a single record to check the citation information and duration field, and compare the procedure number and revision date |
| Exam records | Examinee, exam paper version, score, exam date, and invigilation receipt match the dates and names in the courseware and procedures | Page through to retrieve all records by total record count, extract one record to check the role, citation information, and time, register the exception, and hand it to the responsible person for handling |
| Session message records | The two role types, question and answer, appear alternately, and the total record count matches the pagination offset | Check the application and session identifiers in the request parameters, pull two pages consecutively to compare the total record count and offset, and confirm response code of 200 |
Three common errors
- Symptom: For the same exam, the course name and date in the courseware and exam records do not match. Cause: After the courseware version was updated, the exam records did not synchronously cite the new version, making it impossible to locate the source material during exception tracing.
- Symptom: The revision date of the security operating procedure is inconsistent with the version cited in the exam records, and the signature or receipt is missing. Cause: The receipt was not reissued after revision, so the reviewer cannot confirm that the examinee used the current version.
- Symptom: The interface returns empty but there are sessions in the UI, or only the first page is retrieved, and the exported records lack citations. Cause: The sources of the application and session identifiers are inconsistent, the pagination offset was not paged through to retrieve all records, and the citation field was not exported with the records.
How to verify the setup
This feature's acceptance: page through to retrieve all records by total record count, extract one record to check the role, citation information, and time, confirm response code of 200, and check the correspondence between the message identifiers and content fields _id, dataId and value and the records.
Business test: create an exception record, see whether the source material can be traced, and compare the fields, dates, and signatures of the compliance training courseware, security operating procedures, and exam records.
- Check the source of the application and session identifiers in the request parameters, pull two pages consecutively to compare the total record count and offset, and confirm response
codeof 200. - Open a record to check the role, citation information, and duration field, register the exception list and hand it to the responsible person for handling, and have the reviewer sign to confirm.