Information Captured by Table-level Auditing

The following information is captured:

• Date and time - The date and time of the transaction.
• User ID - The ID of the user who invoked the transaction.
• Table name - The name of the database table which was modified.
• Program name - The FID of the function which invoked the transaction.
• Transaction type - Indicates whether the transaction was online / batch / deferred / etc.
• Key info - The key which was provided to this operation. Note that this may identify one or many records.
• Details of changed data - These details are logged in an XML format. The exact format of this XML can be seen in the JavaDoc details for the class curam.util.audit.AuditLogInterface in the doc/api directory of the SDEJ. They include the names of the all the fields referenced by the details struct, the field types, the new version of the field data and, if optimistic locking is enabled, the old version of the field data.

  If optimistic locking is switched on, then the operation is guaranteed to have only affected a single record. Therefore, the audit information includes information about the record before and after the operation. The old version of the record is re-read, the old value of each field is compared to the new value, and any field which has changed is included in the audit information, i.e. unchanged fields are filtered out.

  If optimistic locking is switched off then for performance reasons the record is not re-read during the update, so the audit information will contain only the new versions of all the fields involved in the update, not a before-after comparison of the record. Also, any non-optimistic updates apart from the 'modify' stereotype can potentially affect more than one record, in which case it is not possible to record a before-after comparison of the update. All the detail fields will be included regardless of whether the new value is different to the old value.

  This data can be compressed when using the default auditing handler by specifying the curam.audit.audittrail.datacompressionthreshold property described in the Cúram Configuration Parameters appendix of the Cúram Server Developer's Guide.

• Operation type - Indicates whether the operation was one of: create, read, update or delete.