Reprocess error purge

This purge deletes reprocess errors from the system. This reduces the load on frequently accessed tables.

You can use purge codes pseudo-logic to analyze purges. If the following conditions are met, a YFS_REPROCESS_ERROR table is picked up for purge:

  • The YFS_REPROCESS_ERROR records with State = Fixed or Ignored is processed.
  • The last modified time is earlier than the lead time, in days setup.
  • The YFS_REPROCESS_ERROR records with State=Initial and the yfs.purge.reprocess.defaultExpiryWindow database property is set to a number, maximum 3 digits such that the modified timestamp is less than the current date minus the expiry window property. Such alerts are moved to Ignored status.

This purge reads only the rules defined by the hub. Enterprise overridden rules are not considered.

Any enterprise using the Console must schedule purge transactions.

Attributes

The following are the attributes for this time-triggered transaction:

Table 1. Reprocess error purge attributes
Attribute Value
Base Transaction ID REPROCESSPRG
Base Document Type General
Base Process Type General
Abstract Transaction No
APIs Called None
User Exits Called YFSBeforePurgeUE

Criteria parameters

The following are the criteria parameters for this transaction:

Table 2. Reprocess error purge criteria parameters
Parameter Description
Action Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value.
Number of Records To Buffer Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000.
Live Optional. Mode in which to run. Valid values are:
  • Y - Default value. Moves qualifying records from the regular tables listed under Tables Purged to the corresponding history tables.
  • N - Test mode. Determines the rows that are moved to history tables without actually moving them.
PurgeCode Required. Cannot be modified. Used for internal calculations, such as determining retention days. Corresponds with the PurgeCode used in Business Rules Purge Criteria.
ColonyID Required in a multi schema deployment where the YFS_REPROCESS_ERROR table may exist in multiple schemas. Runs the agent for the colony.

Statistics tracked

The following statistics are tracked for this transaction:

Table 3. Reprocess error purge statistics
Statistic Name Description
NumReprocessErrorsPurged Number of reprocess errors purged.

Pending job count

For this transaction, the pending job count is the number of records that can be purged from the YFS_REPROCESS_ERROR table.

Events raised

None.

Tables purged

YFS_REPROCESS_ERROR