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

TrackSecurityChanges history memos incorrect



When enabling field level auditing, attempting to track changes in a nested paglist (such as pagelist(1).pagelist(1).property) only partially succeeds.  The changes are tracked, but the history memos do not distinguish deeper than the first level of the pagelist.  That is, if you create 3 entries in pyTrackSecurityChanges as below, the history memos will all reference the first occurrence in the above list for which the first subscript is a match.   Changes to any of the nested subscripts will be tracked, but they will all refer back to the first occurrence matching the 1st-level subscript.
  •  pagelist(1).pagelist(1).property
  •  pagelist(1).pagelist(2).property
  •  pagelist(1).pagelist(3).property

Error Messages

Not Applicable

Steps to Reproduce

Configure the pyTrackSecurityChanges as highlighted below.

Root Cause

The system does not provide the fine level of detail attempted above.


The system does not provide the fine level of detail attempted above.  The changes will be tracked, but only the first reference to the first level subscript will be activated when the change occurs.


Published January 31, 2016 - Updated October 8, 2020

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