Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Field Level Auditing Memo for pagelist cannot be customised

SA-84962

Summary



On changing the Memo text for Field level auditing on a pagelist property, the system is unable to locate the correct field value rule created for the property in a pagelist.

The Audit history displays TrackSecurityChange_Add <Value of the property> or TrackSecurityChange_Remove <Value of the property>.


Error Messages



Not Applicable


Steps to Reproduce

  1. Create a pagelist with multiple properties. The structure of the page is Page1.Page2.PageList.
  2. Add a property in the pyTrackSecurityChanges data transform. The field added is similar to the below. The Source is left empty to allow Memo customization.
     
    Target  Source
    .Page2.PageList(1).PageListProperty  
  3. Create a field value rule in the same class as the PageList and Field Name similar to PageListProperty.


Root Cause



An issue in the custom application code or rules.


Resolution



Here’s the explanation for the reported behavior:

User has a page structure as below which Pega 7 Platform does not support.

Page1.Page2.PageList(1).PageListProperty 

For Field Level Auditing, adding a custom Memo text is supported only for one level of nested property.

That is, only for Pagelist(1).PageListProperty.

Published December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us