Bhagyashree Choudhary (BhagyashreeC9567)
Evoke Technologies

Evoke Technologies
BhagyashreeC9567 Member since 2018 18 posts
Evoke Technologies
Posted: June 19, 2018
Last activity: June 21, 2018
Posted: 19 Jun 2018 12:02 EDT
Last activity: 21 Jun 2018 10:21 EDT

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!


Low-Code App Development Data Integration Java and Activities Case Management Security
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.