Purging historical data

The Landmark system generates a large amount of data for such things as action requests, database session debug logs, message queues, and effective dated group processing. Because it is usually not necessary to preserve all of this data, Landmark provides schedulable actions for purging the data.

For a current list of the delivered framework purge actions, see the Maintenance Requests tab in the Async Framework. This tab shows the business class to which the data belongs and the specific action that is performed.

Many of these schedulable actions are delivered in an enabled state, and with settings for the scheduling frequency and and data retention duration. Others may be delivered in a disabled state. You can choose to enable all purge actions at once or enable the disabled ones individually. You can modify the delivered settings. For example, on the initial running of a purge action, if you know that a large amount of data is purged and you need to avoid a long-running process, you can adjust the setting for how far back to maintain data. You can start by preserving data from two years ago and onward, and then rerun the action with a setting that preserves data from one year ago and onward.

One important action that is delivered in an enabled state is a Purge action that removes AuditLogEntry records. This action prevents the potential large accumulation of these records. AuditLogEntry records are purged weekly based on these details:

  • Records that have a FrameworkType set are purged if they are older than 180 days.
  • Records that do not have a FrameworkType set are purged if they are older than 30 days.

You can purge archived AuditLogEntry records regardless of the date by selecting the Include Archived Framework Type Records and Include Archived Non Framework Type Records check boxes on the Purge Entries form.

If you want to archive any of the data that is to be purged, set up data replication for the business classes that the purge actions apply to, and run the data replication before the purge action runs.

Some actions already have queues and mappings set up, and for others, a System Purge queue is used.

  1. In the Async Administrator, select Setup and then select the Recurring Requests tab.
  2. Enable the maintenance request actions.
    • To enable all actions at once, click Enable or Disable Request and select the Enable option. Click Submit.
    • To enable a single action, select the action and select Yes in the Pending Scheduling option. Click Save.
  3. Optionally, modify the purge schedule and the data retention period.
    1. Select the action whose scheduling you want to modify and click Update.
    2. To make changes to the frequency settings, modify values in the Scheduling section.
    3. To make changes to the data retention period, click Parameters and modify either the Thru Date field or the Offset Days field.