Question
ASB
NZ
Last activity: 25 Mar 2024 7:23 EDT
Field level auditing for data class
Hi,
I have a requirement to move data class and its history class to move to CustomerData and I need to audit changes for the fields in the data class.
I have tried the approach given in the below link, but it only works when data class is in PegaData. When I move data classes to CustomerData it will not have blob, hence its failing.
Auditing field-level changes to security rule and data instances | Pega
Can someone guide me how can I achieve this?
Thanks
Accepted Solution
Updated: 25 Mar 2024 7:23 EDT
Pegasystems Inc.
CA
We can have an option to capture the history on the data table instance. This will not track at the field level, however, it tracks at the record level. Please check if this is an option for your requirements.
Maantic Inc
IN
By default Pega's OOTB field level audit runs on Work- classes. The changes are automatically captured in the History- classes. You can refer to this link:
As an alternate way you can follow the below steps and give it a try:
1. You need to create pyTrackSecurityChanges DT in the data class for which you are implementing the audit- mention all the properties you are creating the audit
2. Make sure you have history class and table created for that specified data class
3. Create a declare trigger” TrackSecurityChanges” in the data class and call pega OOTB activity “TrackSecurityChanges”
Accepted Solution
Updated: 25 Mar 2024 7:23 EDT
Pegasystems Inc.
CA
We can have an option to capture the history on the data table instance. This will not track at the field level, however, it tracks at the record level. Please check if this is an option for your requirements.