This transaction deletes tasks previously archived by the Task Purge.
You can use the pseudo-logic of purge codes to benefit in analyzing purges. A task from the history table is picked up for purge if it meets the following condition:
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | TASKHISTORYPURGE |
Base Document Type | General |
Base Process Type | TASK_EXECUTION |
Abstract Transaction | No |
APIs Called | None |
User Exits Called | YFSBeforePurgeUE |
The following are the criteria parameters for this transaction:
Parameter | Description |
---|---|
Action | Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value. |
Live | Optional. Mode in which to run. Defaults to N.
|
PurgeCode | Required. Cannot be modified. Used for internal calculations, such as determining retention days. Corresponds with the PurgeCode used in Business Rules Purge Criteria. |
Organization Code | Optional. Organization for which the Task History purge needs to be run. If not passed, then all organizations are monitored. |
AgentCriteriaGroup | Optional.
Used to classify nodes. This value can be accepted
by WMS time-triggered transactions that only perform their tasks on
the nodes with a matching node transactional velocity value. Valid values are: LOW, HIGH, and any additional values defined by the Hub from Sterling Application Platform > System Administration > Agent Criteria Groups. |
ColonyID | Required in a multischema deployment where a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumHistoryTasksPurged | Number of history tasks purged. |
For this transaction the pending job count is the number of records that can be purged from the YFS_TASK_H table.
None.
YFS_BATCH_H
YFS_BATCH_LOCATION_H
YFS_TASK_H
YFS_TASK_STATUS_AUDIT_H