1 person found this helpful
The Purge Obsolete Workflow Runtime Data Concurrent request can purge all item types which are eligible for purging:
1. Workflow item must be closed.
2. Workflow item must have all child/parents closed.
3. The persistence type is the appropriate one.
4. Using an age parameter value that is before the closing date of the workflow item.
For any open item types, except WFERROR, you have to check with your team how this can affect internally your processes.
The Purge Obsolete Workflow Runtime Data Concurrent request has a parameter called Core Workflow Only which by default is set to Yes.
This purges only core runtime information associated with work items for performance gain during periods of high activity.
Run a more comprehensive Purge Obsolete Workflow Runtime Data Concurrent request for ALL item_types by setting the Core Workflow Only value to NO.
This will purge obsolete runtime information associated with work items, including status information, any associated notifications, and it also purges obsolete design information, such as activities that are no longer in use and expired ad hoc users and roles, and obsolete runtime information not associated with work items, such as notifications that were not handled through a workflow process and, if the ECX: Purge ECX data with WF profile option is set to Y, Oracle XML Gateway transactions that were not handled through a workflow process.
Schedule this comprehensive Purge request once a month or every 2 weeks as needed.
For more information refer to Notes:
- How to Purge WFERROR (System: Error) Workflow Items? (Doc ID 804622.1
- A Detailed Approach To Purging Oracle Workflow Runtime Data (Doc ID 144806.1)
- Purge Obsolete Workflow Runtime Data Concurrent Request (FNDWFPR) Is Not Purging Data (Doc ID 752383.1)
Please don't forget to mark Correct/Helpful answers in the thread. It helps other Community users to identify the solution quickly !