Skip to main content

Auditing field-level changes to security rule and data instances

Suggest edit
Updated on July 1, 2021

By simply creating a model and a trigger rule, you can generate history memos that automatically audit field-level changes to both rules and data instances. For example, you can create a model and trigger that will track changes to user RuleSet lists in an access group. Pega Platform™ also provides preconfigured reports to collectively view the history data.

  1. Opening the appropriate model to review the default properties

    The Pega-RULES ruleset contains four models (Rule-Obj-Model) named pyTrackSecurityChanges that allow you to quickly set up audit functionality for security-related records.

  2. Creating a declarative trigger

    In this step, you create a declarative trigger (Rule-Declare-Trigger) for each class you want to track.

  3. Verifying your new auditing changes

    Verify your configuration by changing a field (defined in the model) in the appropriate rule instance, and then opening the history memo.

  • Previous topic Auditing changes to aggregate properties
  • Next topic Opening the appropriate model to review the default properties
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us