You can now configure how to track changes of field values in your cases in a more intuitive and user-friendly way by defining field-level auditing. By tracking changes in your cases, you can analyze progress and maintain case compliance. For example, in a shipping order case, you can track how a shipping address changes, and who and when performs the change. In case of any issues with the shipping address, you can view details about the change and investigate further. 

You configure field-level auditing in case type settings in both App Studio and Dev Studio, instead of using only a landing page in Dev Studio. You can enable auditing for scalar values of single fields, field groups, such as personal details that include a name, a surname, and an address; and field group lists, for example, a list of users with their IDs and email addresses. Now field-level auditing works also for field group lists that are embedded within other field group lists, such as a list of customers, where a shipping address and a billing address is defined for each customer.

After you upgrade to Pega Platform™ 8.4, the field-level auditing landing page in Dev Studio is available in a read-only mode, and all of your auditing configurations continue to work as before. The new field-level auditing configuration is available by default for all new case types and existing case types that do not have auditing enabled. For case types with field-level auditing defined, you can switch to the new method to edit the existing field-level settings by simply switching on a toggle in the Auditing section on the Settings tab of your case type. After you switch to the new, simplified approach, an application migrates your field-level auditing settings, and any run-time data gathered so far is available in the History tab of a case. 

The following figure shows the configuration of field-level auditing in the case type settings:

Users see the audit data in a new gadget that you can embed in a form that displays case details on the Audit tab. 

The following figure shows field-level auditing at run time:

For more information, see Enabling field-level auditing.