Audit trail

The history of a work item is sometimes known as the audit trail, a term adopted from accounting and bookkeeping.

Open the Audit tab on a user form to access the audit trail display, which shows which operators have worked on the work item and when, what automatic processes were performed by the application, and other details.

You can customize audit trail behavior as follows:

• To add a history instance at any point in the flow, add the utility activity Work-.AddHistory to a flow. Others are added automatically at runtime.
• To control the individual types of flow processing steps written to history, copy and customize the standard decision tree Work-.FilterHistory in your application. See Flows — Controlling the volume of generated work item history instances.
• To control whether this feature applies to a specific system, based on the production level, copy and customize the system setting rule Pega-ProCom.FilterHistory in your application. See Flows — Controlling the volume of generated work item history instances.
• To enable geolocation tracking, copy the standard when rule pyGeolocationTrackingIsEnabled to your application. See Using geolocation tracking.

Work object history instances are stored as objects in classes derived from the History-Work- class. The name of the class is History-ZZZZZ, where ZZZZZ is the name of the work item class.

	History- base class History-Add method
	About audit trails, case narratives, and attachments About Harnesses Flows — Controlling the volume of work item history instances

Definitions