What this category's data looks like
This page is for the enterprise compliance and security training category. Materials include compliance training courseware, security operating procedures, and exam records. Courseware and procedures are usually updated at policy revision points, while exam records are generated session by session as training occurs. Fields cover material name, quantity, date, and signed receipt. When entering the deployment, operations, and application handover stage, courseware and procedures enter the main business database as business content, exam records enter the log database as process evidence or are co-located with the main database, and the cache and vector database handle session state and retrieval indexing respectively. Because the materials have different roles, the verification focus also differs: for courseware and procedures, check version and date; for exam records, check quantity and signatures. All three must be aligned item by item on the handover form.
Configuration and implementation checks
This step is performed by the deployment environment's connection configuration (server side), not by the capability execution of a model node, and it outputs whether the connection is available (service startup result and connection logs). The handover-ready deployment state and operation records are then completed by the deployment handover and subsequent business processing. The main business database, log database, cache, and vector database can point to different instances respectively. If the log database is not configured separately, it reuses the main database.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Name, version, and date must be consistent with the security operating procedures, and the signature field must be complete | Query the courseware records in the main business database, and check the name, quantity, and date against the handover form |
| Security operating procedures | Version and effective date must be synchronized with the courseware, and receipts must be complete | Query the procedure records in the main business database, and check the version number and signed receipts |
| Exam records | Session, quantity, and date must correspond to the courseware and procedures, and signatures must not be missing | Query the exam records in the log database, and compare quantity and date item by item with the handover form |
| Connection configuration | The main business database, log database, cache, and vector database are each connectable | Check that the values of MONGODB_URI, REDIS_URL, and PG_URL match the instance addresses, and view the connection results in the startup logs |
Three common errors
- Symptom: The same exam record has mismatched name, quantity, and date between the courseware list and the exam records. Cause: The two were entered separately and were not checked item by item against the handover form.
- Symptom: The courseware has been updated to a new version, but the procedures are still the old version, and the version on the handover form has not been synchronized. Cause: After revision, the other material was not updated in sync.
- Symptom: Exam records lack signatures or receipts, making them impossible to confirm at handover. Cause: Signatures were not added promptly after the session ended, and the records were not closed out.
How to verify the setup
Acceptance for this feature: connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and verify that the values of MONGODB_URI, REDIS_URL, and PG_URL match the instance addresses.
Business test: check once item by item according to the handover form to see which record is missing, focusing on the name, quantity, date, and signatures of the courseware, procedures, and exam records.
- In the deployment environment, check the values of the main business database and log database connection variables, and confirm that the database written to by the logs matches expectations.
- Use a client to connect once to the cache and vector database, check the response, and verify the selected vector database and address against the deployment instructions.