Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Verifying your new auditing changes

Updated on March 15, 2022

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

Before you begin: Complete the Creating a declarative trigger procedure.
  1. Using the Rule-Obj-Model in the Creating a declarative trigger procedure, open a Data-Admin-Operator-AccessGroup instance in your application.
  2. Add a Work Pool.
  3. Click the History tab and click the History Details button at the bottom of the form.
    Result: The memo appears.

The memo provides a timestamp of the event, the action performed on the property, and the ID of the operator who made the change. The standard memos take the following forms:

  • Added {ValueFromModel}{NewValue}
  • Changed {ValueFromModel} from {OldValue} to {NewValue}
  • Removed {ValueFromModel}{NewValue}

The memos track modifications in the following manner:

  • Single value properties, such as .pyDefaultAppName, are tracked as Changed. For example, if the Application Version was changed from 8.2 to 8.1, the memo would show

    Time                                   Memo                               Handled By
    2/26/2020 3:41 PM Changed application version from '8.2' to '8.1'  [email protected]
  • Complex property types such as value lists and pages lists are tracked as Added or Removed. For example, if Work Pools originally contained:
    • PegaSample
    • History-PegaSample
    And was modified to:
    • AlphaCorp-OrderEntrySystem
    • History-PegaSample
    • Previous topic Creating a declarative trigger
    • Next topic Extending the security auditing feature to record changes to additional properties

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us