Security auditing
By tracking the changes to your system, you can understand how your system functions and be alerted of any potential problems. By default, Pega Platform™ tracks many types of security events, such as failed logins and password changes.
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.
Customers can easily configure fields from within App Studio/Dev Studio to track changes in a case type. This allows customers to maintain compliance and follow changes to critical information in cases.
Note: Only standard Pega Platform applications support field-level auditing. Applications that you build on Cosmos React do not support this feature.
Field-level tracking, and changes made in an instance of a rule, are captured in the History- class. Changes to data instances are saved in an instance of a subclass of the History-Data- class.
For example, the system records changes to access groups (Data-Admin-Operator-AccessGroup) in instances of the History-Data-Admin-Operator-AccessGroup class.
An audit entry shows the old value, the new value, who made the change, and when the change occurred. There may be two audit entries for data fields: one entry for modifying the initial value and another entry for adding a new value.
If you want to enable fields in a data relationship, click the name of a data relationship, and then select the check boxes next to the fields that you want to enable for auditing.
Note: Enabling auditing tracking on each property would adversely impact the performance of the application. Limit to enable the audit tracking only for the important data fields which are critical for the business.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?