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

Property Description incorrect during Field level Auditing

SA-81139

Summary



Field level Auditing for a page group property displays all the Audit notes. This occurs even for a single page group property change.

For example, change in the Address(Home).city property displays Address(Office).city in the audit. 

The system does not verify the subscript of the page group to identify the correct label for a given property.



Error Messages



Not Applicable


Steps to Reproduce

  1. Create a single value property in a page group property.
  2. Create two pages of that page group.
  3. Create a section to capture this single value property in two different pages of the page group.
  4. Execute the 'Field level auditing' wizard to track changes in these properties values.
  5. Update the property value from the UI (section created in Step 2). An audit entry is created. However, in the Description, the property label is displayed incorrectly. The same label is displayed, though different labels are provided in the data transform.


Root Cause



This behavior is as per Pega product design: Page Group and Page List property types.


Resolution



Here's the explanation for the reported behavior:

For a Page Group, a finite list of subscripts is defined. However, for a Page List, the index is any integer and it is difficult to add an entry for all indexes and subscripts.

Hence, for easy configuration to track all the indexes, track all the entries.
Suggest Edit

Published August 15, 2019 - Updated October 8, 2020

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