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 values are not getting picked from application ruleset

SA-31651

Summary



User has configured field values to track property changes.

Whenever the changes/addition/removal of property values are done, the audit gets recorded.

But Field values are not being picked from application ruleset for pagelist/scalar properties. Instead it shows "TrackSecurityChange_Add"|abc. 


Error Messages



Field values are not being picked from application ruleset


Steps to Reproduce



1. Create a field value for page list property. 
2. Add tracking for that pagelist. 
3. During the flow, delete any pagelist entry and submit. 
4. Observe the audit logs, the field values from application ruleset are not picked. 


Root Cause



User has created field values in the different class, hence they are not picked. 

Resolution



Create the field values in the embedded class of the page list and the source of pagelist property in pyTrackSecurityChanges data transform should be empty. 

For example, we want to track WorkBasket in Work Tab of Operator record, then create field values in the pxObjCass of that pagelist, that is,Embed-Data-Admin-WorkBasket. One can find the embedded class name in XML of that rule.

Refer:
 
https://pdn.pega.com/how-extend-security-auditing-feature-record-changes-additional-properties

which describes how the field values must be created inorder to get picked from application ruleset.  

 

Published January 3, 2017 - 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