Question
Field Level Auditing for Data Classes
Hi Guys,
What is the best way to implement field level auditing for Data Classes.
Business wants to capture Audit for every operation that user performs, for instance "User XYZ changed the value of Owner Fax to 321-324-2123 from 321-706-4543" and so on.
Pega OOTB Field Level Auditing works only for Work Classes. We don't have any work object associated with these data objects. They are primarily data grids and edit screens without any process flow- where user can edit any object or create or delete one.
1. Would Declare Trigger be a good approach? There are going to be lot of end users in production that might be editing information on different objects at the same time and updating the Audit table. Could this lead to Performance issue?
2. Also, if declarative rules are used- is there a way to track which properties got changed-because of which it was fired?
3. Should the existing Pega History tables be used for Audit or separate table should be created?
Thanks much!
Bhagyashree
Thanks Bhavya,
Our client doesnt encourage DB Triggers considering Performance in mind. These tables could also be used by other applications. Can you suggest some other alternative from within the application.
Also, just to understand how and when would Declarative Rules impact Performance and in what way.
Thanks!
You can implement field auditing on data class by below steps:
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”
Though i am not sure about its performance as mentioned by @Bhavya_Incessant
There is a feature called as "Security Auditing" , available in OOTB.
https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#security/auditing/sec-enable-sec-auditing-tsk.htm
Hi
Declare triggers may not be the right option for Audit changes as that would overload the system. In the long run, the application may be come slow. We are struggling in our application with that.
The one way I see is to used Database level triggers, for Insert,Delete and Update on properties.
We have created db triggers on our tables and a separate table is updated with the caseid, fieldname, Operation(I/D/U), Previous value, new value , Updated On, Updated by.
Give it a try and see if its feasible in your application.
Regards
Bhavya