@ADITIJ49

I've not seen Pega's OOTB audit being used on data records. You can instead try this way:

• Create a declare trigger on the data type class
• Write an activity where you'll save a new record in the history table
• Call this activity from the trigger on a committed save

@ADITIJ49

1. Create an Audit Table: This table will store the audit logs for any changes made to the data types. 

2. Create Database Triggers: Depending on your database, you can create triggers to automatically log changes.

    

@ADITIJ49 Auditing for data types you can do with following methods. 1. Creation of an audit table - Pega Platform maintains a historical record of changes to certain data classes and rule types. You can use this history to diagnose system issues and to demonstrate compliance to internal and external auditors.For example, you can record the application rule name that is referenced in an access group each time a user updates the Access Group form and adds, changes, or deletes an application rule name.

2. Database trigger rule using declare trigger - As per your DB changes you can trigger those rules anytime,

@ADITIJ49

Can you please check this configuration to see if this suffices your requirements?

Data -> View definition -> Advanced - Bypass History on Save section