Field Level Auditing does not work correctly for page lists
Field level auditing does not work correctly for nested page list properties.
Steps to Reproduce
- Create a data structure, such as Page1.Page2.PageList1(1).PageList2(1).
- Audit the above structure by navigating to Designer Studio > Case Management > Work Management > Field Level Auditing.
- Update any scalar property in PageList2. Entries are incorrect in the audit history.
Field level auditing is not supported for nested page list properties.
Tracking changes in the page list for a specific page index property is not possible at the granular level. The logic of tracking the changes in a page list compares an entire page at a particular index (for example, index 1). If there is a difference between the current page and the previous page at index 1, audit messages are logged.
Changes to the existing page and a new page is not known. Two audit messages, such as 'Removed page at index 1' and 'Added page at index 1' display. This generates multiple entries in the audit.
Perform the following local-change:
Enable auditing for specific properties in the page list. This prints the correct audit messages, such as 'Account balance changed from '1000' to '2000'.'
However, the limitation is that it does not print the nested path of the property (that is, Account balance of the page list which was updated).
This behavior is currently not supported and is scheduled to be supported in a future Pega release.
0% found this useful