Audit

Contains properties connected with the runtime setting of auditing options.

Table 1. Audit settings
Property Name	Type	Meaning
curam.audit.opaudittrail	BOOLEAN	Specify whether operation level auditing for the operation 'OPERATIONNAME', within the client visible class 'CLASSNAME' of the code package 'CODEPACKAGE' is enabled or disabled. Format: curam.audit.opaudittrail.PROJECTNAME.CODEPACKAGE.CLASSNAME.OPERATIONNAME Default: determined by the option set in the model.
curam.audit.audittrail	BOOLEAN	Specify whether table level auditing for the operation 'OPERATIONNAME' of entity 'CLASSNAME' within the code package 'CODEPACKAGE' is enabled or disabled. Format: curam.audit.audittrail.PROJECTNAME.CODEPACKAGE.CLASSNAME.OPERATIONNAME Default: determined by the option set in the model.
curam.custom.external.operation.hook	STRING	Specify the name of a class which implements 'curam.util.audit.DataAccessHook' and which will be used to audit client-visible operation calls.
curam.custom.predataaccess.hook	STRING	Specify the name of the class which implements 'curam.util.audi.DataAccessHook' and is used to audit data access calls.
curam.custom.audit.writer	STRING	Specify the name of a class which implements curam.util.audit.AuditLogInterface and will be used to capture and write audit information.
curam.audit.audittrail.noxmlaudit	BOOLEAN	Specify whether the XML audit writer is disabled for data access operations. This saves XML from being generated for each invocation of the operation done so far. Default: false.

Note: There are two ways to turn off auditing:

Set the 'curam.custom.predataaccess.hook' property in the Application.prx to be blank and set the 'curam.audit.audittrail.noxmlaudit' property to be true.
Set the value of the property 'curam.custom.audit.writer' to be 'curam.util.audit.DisabledAudit'. The 'curam.util.audit.DisabledAudit' is a class that is provided by the Infrastructure that contains empty methods. Therefore the class will be called but no auditing will take place. This ensures that the 'Audit.logDataAccess' class gets called and builds up the xml that will form part of the auditing but it does not actually insert any audit records onto the database.

The first option is the preferred option.