Field-level auditing

Pega Platform™ automatically tracks actions performed, for example, tracking which operators worked on a case and when. By default, Pega Platform maintains a history of actions performed on cases (Work- instances), such as when the case status changes, when the case is routed to an operator, or when the time to execute a service-level agreement expires.

You can enhance this capability by using field-level auditing. Field-level auditing enables you to monitor changes to important data values in your cases. From a security perspective, it is useful to track modifications when sensitive data is involved.

You can use field-level auditing to track changes that users make to fields and data relationships. The actions are automatically recorded for the field in the History dialog, in the Field History tab. For example, you may want to know if an employee's salary has changed. The following image shows an updated field value for Salary that is tracked by using the field-level audit feature. This update affects the tax withholding amount in the next stage.

An audit entry shows the old value, the new value, who made the change, and when the change occurred. For data relationships, there may be two audit entries: one entry for modifying the prior value and another entry for adding a new value.

To track updates to field values in your application, you use the Settings tab in App Studio. Enable field auditing and select the field you want to audit.

In the center of the following image, slide the vertical line to compare the differences between field-level auditing for a single property and a data relationship property.