Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Enabling field-level auditing

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

Maintain case compliance and follow progress in your case types by enabling field-level auditing. When you enable fields for auditing, users of your application can conveniently track how values have changed, such as an estimated end date, so that they can plan and process work more efficiently.

Before you begin:
  • To see field-level changes at run time, ensure that your application uses the latest version of the UI Kit.
  • Mark as relevant records properties that correspond to the fields that you want to enable for auditing. For more information, see Marking a record as relevant.
When you enable field-level auditing, your application tracks changes that users make to fields and field groups in the data model that your case contains. Users of your application can then check previous and current field values, the last user to change the values, and the time of their modification.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the case working area, click the Settings tab.
  3. In the settings panel, click Auditing.
  4. In the Auditing window, turn on the Enable field audit switch.
  5. In the Fields column, select the check boxes next to the fields that you want to enable for auditing.
    Note: You can only enable fields, field groups, and field lists that contain scalar properties.
  6. If you want to enable fields in a field group, click the name of a field group, and then repeat step 5.
  7. Click Save.
Result: At run time, when users process the case, they see the changes to the fields on the Audit tab.What to do next:
  • Maintain the good quality of field-level auditing and troubleshoot errors by checking the pzStandardProcessor queue processor in Admin Studio.
  • Continue working on your field-level auditing data after you deploy your application on another system by packaging the appropriate rules and data. For more information, see Packaging rules and data that contain field-level auditing information.

This Topic is available in the following Module:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice