Pruning unnecessary workunit data for the data area

Autopurge deletes significant amounts of data for a process and should be used with caution. Pruning only some workunit data using Workunit Data Cleanup is recommended instead in most cases.

See Pruning unnecessary workunit data by process.

If the autopurge feature is enabled, data in the these tables is automatically deleted:

• PfiActivity: This table contains all the activities which are created by the workunit. Each node in a flow will be stored in the PfiActivity table if the activity level logging is turned on.

• PfiActivityVariable: This table contains the variables associated with a particular activity.

In these situations, runtime data for workunits with a status of Completed or Canceled is not automatically deleted:

• Workunits associated with user actions, such as User Action and HRTM User Action nodes

  This ensures that actions that have been taken on a workunit are not lost until you choose to delete them.

• Data in the PfiWorkunit table, the highest level in the table hierarchy

  Workunits are displayed in your Workunit view until you delete them.

While autopurge does not delete all data associated with a workunit, it does delete data about activity node execution, except for User Action and HRTM User Action nodes. This might be appropriate depending on your circumstances. However, if a process is new, you might want to keep autopurge disabled until you know that the process runs as intended.

In addition, if your processes do not generate a large amount of data, you might want to leave autopurge disabled and delete data from Workunits and/or Workunit History views per the schedule you have established.

Autopurge is enabled when the autopurge parameter is added to your system.