Field Level Auditing for Data class


I am trying to have field level auditing on one of my data classes. Its working fine but everytime I save or modify the data instance, its tracking all the property values. Its not taking the previous values into consideration and tracking all the property values, even if those property values have not been changed. I found that its unable to get the pyPreviousValues for this instance. Can somebody tell me how exactly this works, and do we have this pyPreviousValues for the data instaces.


**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

July 16, 2012 - 1:51pm

I guess the OOTB feild level makes use of the pyPreviousValues, but for my instance i cant see this page. Do we need to do anything here.

July 11, 2012 - 2:26pm

Use a Declare Trigger on the data class. The Declare Trigger rules will cause an activity to run when instances of a specific class are created, updated, or deleted in the database. Read about the

Copy Value to (optional)
Optional. Identify a property of the same mode and type as the property in the Property field on this row. This property can retain the current value of the changed property. Copying occurs only if the trigger activity runs, and after the trigger activity completes.

Copying makes the previous property value available to the second and subsequent executions of this rule.

FOR WORK OBJECT: PRKB-25196 How to control history instances written to the audit trail.

July 11, 2012 - 2:30pm

You should use the Field Level Auditing tool.
Access from Pega Button to Process & Rules -> Work Management -> Field Level Auditing.

July 11, 2012 - 4:59pm

DUNND: Hi, where should I specify this "Copy Value to (optional)
Optional. Identify a property of the same mode and type as the property in the Property field on this row. "

July 11, 2012 - 5:01pm

AKGOK: But from the "Field Level Auditing tool", we can configure the audit only for the work types not for the Data. So I manually created the same rules that the tool creates.

June 26, 2013 - 8:05am




We are implementing field level auditing in our project, propertites which are in work level is working fine, but for the properties which are in page level or page list, we are getting "flow VerifySendCorr had an error n step, the property xxxxx was of mode pagelist" but i am refering page there. please let us know if you have any suggestion or any more information is required.