Alert message

Alert message

Archive or Purge

Archive

Commit Type (Default)

EVERY_X_RECORDS

Commit Parameters (Default)

BATCH_RECORD_COUNT=1000

Default Aging Days

1096 days

Tables affected

MESSAGE

MESSAGE_HEADER

RECIPIENT_MESSAGE

NC_MESSAGE_PARAMETER

NC_MESSAGE_TAG

Description/Notes

Archive system-generated notifications such as schedule changes, rule violations, and timesheet reminders that have exceeded their retention period.

The first run of this policy may involve a high volume of data. The policy is configured with a batch record count of 1000 to enable the process to commit incrementally and resume safely if the task is interrupted. If you use custom reporting that references Alert messages, ensure those reports are updated to query the archive tables if historical data is required.

Note: To archive alert messages, you must manually add ALERT MESSAGE to the ARCHIVE_POLICY_NAMES parameter of the Archive Policy Run Task.

This process involves moving:

1. Records in the MESSAGE table where the message type is Alert such as MSGTYP_ID = 11 and the message date is older than the calculated aging data.
2. Related records in the RECIPIENT_MESSAGE table for the archived messages.
3. Related records in the MESSAGE_HEADER table for the archived messages.
4. Related parameters in the NC_MESSAGE_PARAMETER table for the archived messages.
5. Related tags in the NC_MESSAGE_TAG table for the archived messages.