This time-triggered transaction purges productivity data for a period greater than the lead_days specified in the Productivity Purge criteria for a specific OrganizationCode.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | PRODUCTIVITYPRG |
Base Document Type | General |
Base Process Type | General |
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. |
PurgeCode | Required. Cannot be modified. Used for internal calculations, such as determining retention days. Corresponds with the PurgeCode used in Business Rules Purge Criteria. |
Live | Optional. Mode in which to run. Defaults to N.
|
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. |
EnterpriseCode | Optional. Enterprise for which the Productivity Purge needs to be run. If not passed, then all enterprises are monitored. |
Organization Code | Optional. Organization for which the Productivity Purge needs to be run. If not passed, then all organizations are monitored. |
ColonyID | Required in a multischema deployment where the YFS_PRODUCTIVITY table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumProductivityRecordsPurged | Number of productivity records purged. |
For this transaction the pending job count is the number of records that can be purged from the YFS_PRODUCTIVITY table.
None.
YFS_PRODUCTIVITY