Posted: 28 Feb 2021 7:00 EST Last activity: 13 Mar 2021 12:52 EST
Field Level Audit
We are looking at the new field level audit feature that's introduced in recent version of Pega 8 and it seems to be working quite well for scalar single value properties. However, for complex attributes like page list / group, we still see that there is no way to represent to the users, the specific page (e.g a unique identifier) where the change has happened.
So, if I have a pagelist like AccountList and each page within it has Account Number and Address, there is no way to identify (from the FL Audit) the account number for which the address changed.
We see that there is an extension point pySave within FLAudit class which we can specialize to achieve some of this functionality, but its extremely complex because of the underlying page structure for the audit.
Would like to know from the product team if there is an enhancement planned for this or the roadmap regarding FLAudit features. This is a key feature which customers demand and it doesn't help if every application needs to use the extension point to improve audit capabilities (which as per customers is OOTB as communicated by Pega :) )
***Edited by Moderator: Pooja Gadige to change content format from Discussion to Question***
We have provided improvements for supporting field group and field group(list) properties in the enhanced field-level auditing. As part of field history, one must be able to clearly differentiate the items that are newly added, modified, or deleted. However, I agree it is not possible to clearly differentiate the item using an identifier unless it is explicitly defined by the app developers. Drilling down further must provide the details of the updates that happened to a specific item of the page list.
The expectation is definitely valid and will make sure to consider this use case when planning further improvements around field audit.
Posted: 1 year ago
Posted: 13 Mar 2021 12:52 EST
Sudit Sengupta (SuditSNG)
Lead System Architect
@ArunSarada - Thanks for your response. Hope this is considered in one of the upcoming releases of the platform, as this will make life a lot easier for developers and help to deliver a solution quicker to the customer.