Database table-level auditing
Table-level auditing records provide information about the changes that are made to actual data on the database table. Use database table-level auditing to specify whether to perform table-level auditing for this operation.
Database table-level auditing only applies to database operations of entity classes.
The behavior of auditing depends on whether optimistic locking is switched on or off for the operation. For more information about auditing, see the Table-level auditing related link.
You can override the option at application startup-time by using application properties. This functionality is available to Audit BI. This option and the following is an example of how to use it.
Use the two options to target individual operations by specifying application properties whose format is as follows:
curam.audit.audittrail.<ProjectName>.<ClassName>.<OperationName> curam.audit.opaudittrail.<ProjectName>.<ClassName>.<OperationName>Or, if the class is in a code package:
curam.audit.audittrail.<ProjectName>.<CodePackage>.<ClassName>.<OperationName> curam.audit.opaudittrail.<ProjectName>.<CodePackage>.<ClassName>.<OperationName>Properties whose names begin with curam.audit.audittrail apply to the database table-level auditing option and capture data to table AuditTrail.
Properties whose names begin with curam.audit.opaudittrail apply to the Audit BI calls option and capture data to table OpAuditTrail.
Example (1): To switch on the table-level auditing for operation modify of entity CaseHeader, which is in code package core of the Cúram application, set the property curam.audit.audittrail.curam.core.CaseHeader.modify to true.
curam.audit.opaudittrail.curam.core.facade.Participant.modifyAddress
to false.- Changing the value of an auditing option requires an application restart to take effect.
- The curam.audit.opaudittrail.* properties only affect client-visible operations.
- The curam.audit.audittrail.* properties only affect stereotyped entity operations, excluding stereotypes ns and nsmulti.