Audit Fields
Audit fields enable you to track changes or revisions made to a credit application after submission. You can specify which fields should be tracked. The application history page displays all edits made to the specified fields. Use the
Audit page to select the data fields that you want to audit. You can add the audit field configuration only in the Synchronous Consumer LOB.
Once you save the audit field configuration, the application history page displays all edits made to these fields after an application is submitted. If a field is deleted from the audit field list, edits to that field are no longer tracked. However, the application history retains all edits that were made to the field before the field was deleted from the list. If a field is added to the list, the application history displays all changes made the field after the configuration was saved.
 | Note: Specify only those fields that are absolutely essential to be audited. The lesser the number of audited fields, the better is the performance.
|
| Note: By default, sensitive field audit is disabled. To enable sensitive field auditing, in the
om_apm_audit eSpace, set the site property
AuditEnable to true. Once the property is enabled you can specify the sensitive fields. Note that enabling such auditing might impact the performance.
|