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
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