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 does not handle pagelist copy

SA-79256

Summary



TrackSecurityChanges does not add a manually appended pagelist entry as a new addition. This pagelist is added with a copy to the new DataTransform, which copies page(1) and forms Page(2) of the list. Instead of TrackSecurityChanges identifying the pagelist as a new addition, it captures the value change from XX to YY.


Error Messages



Not Applicable


Steps to Reproduce

  1. Run the Case type.
  2. Add a row in the table.
  3. Click Save. The message 'Added value XYZ' displays in the Audit.
  4. Click the Copy button. 
  5. Click Save. The message 'Changed value from XYZ to ABC' displays in the Audit. 


Root Cause



A defect in Pegasystems’ code or rules.
While copying the page, the pxTrackingIndex and the pyPropertyIndex properties which are responsible for tracking were also copied. Hence, logic considered that the property was already added and now it was changing the value.



Resolution



Perform the following local-change:

After copying the page in the pagelist, remove the pxTrackingIndex and pyPropertyIndex properties from the newly added page in the pagelist. 
Suggest Edit

Published August 15, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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