Document audit trail
Auditing is one of several features the system administrator can use to monitor activity and provide audit trail capabilities. For example, a Document class can be configured to create audit entries whenever documents of that class are checked in.
Applications can configure audit logging for common activities and can enhance audit logging with application-specific custom audit definitions.
Standard event audits are created by the user and logged automatically by the application when the appropriate event or operation is performed. Custom properties can be added to hold application-specific data.
- Object creation
- Updates
- Deletions
- Denials of access
- Audit configuration changes
- Queries on auditable objects
Auditable objects include Document, Folder, CustomObject, Link, ReferentialContainmentRelationship (RCR), and Annotation objects. ClassDefinition objects can also be audited for changes to the object store metadata.
Audit events are stored in a table in the object store. They can be queried, and can be exported to XML format for use by third party reporting tools. The audit events of auditable objects are listed on its audit history property sheet.
- The event or operation that triggered the audit entry (for example, creation of a new object)
- The user who triggered the entry
- Audit type (Audit Success or Audit Failure)
- Date and time of the entry
- The object associated with the event or operation (class, ID)
- Success or fail response from the event or operation that triggered the entry