Field level auditing on Data Object from App Studio
Hi,
Working in App Studio, we have a field in the data model of our Case Type. This field is of the type Data Reference, and pointing to a Data Object.
When trying to turn on Field Level Auditing for this field, it does not show up in the Auditing tab of the Case Type Settings.
Is this intended behaviour? And if yes, how should I get Field Level Auditing on fields in a Data Object?
Any ideas?
Thanks, Rex
edit: looking more closely at the filtering of the Auditing tab, I can see the data references are explicitly excluded. Does someone know the logic behind that?
Accepted Solution
Achmea
NL
In the end we filed an SR for this question. The answer is to make the Data Object an Embedded data type in the data model of the case. Instead of the Data Reference.
That way field level auditing can be done on the Data Object.
Mphasis
IN
@RexDeJong I could remember Pega OOTB Field Level Auditing works only for Work Classes. Thanks
Chandan U
Achmea
NL
@ChandanU5252Yes, true.
But when I look at the work class, the field which is of the data reference type, is a property of the work class.
And it also stores the data in the work object, so I would expect field level auditing to function :)
Capgemini
IN
@RexDeJong - Can you please check if these properties are marked as "Relevant Records"? Only Relevant Records appear for field level audit setting.
Updated: 13 Jan 2022 3:47 EST
Achmea
NL
@SuditSNG Yes, it is. At least the field that is of the type Data Reference. That field is visible as a relevant record. Not the underlying properties btw.
Looking more deeply at the screen "Auditing" in the Case Type Settings, I see the other underlying filters to show possible fields to enable. In those filters I can see Data References are explicitly excluded from showing up in this screen.
I'll update the question with it.
Capgemini
IN
@RexDeJong - Can you also please mark the underlying properties in the data class as relevant record and check?
Achmea
NL
@Sudit SenguptaYes, I checked. Those are also marked as relevant records. Configuring things from App Studio marks a lot by itself :)
Pretty sure it is the filter I found, where it excludes the Data Reference.
Accepted Solution
Achmea
NL
In the end we filed an SR for this question. The answer is to make the Data Object an Embedded data type in the data model of the case. Instead of the Data Reference.
That way field level auditing can be done on the Data Object.