You can submit the Purge Obsolete Workflow Runtime Data concurrent program to purge obsolete runtime work item information, including status information, any associated notifications, and, if the ECX: Purge ECX data with WF profile option is set to Y, any associated Oracle XML Gateway transactions. Use the Submit Requests form in Oracle E-Business Suite to submit this concurrent program.
By default, this program purges obsolete runtime information associated with work items as well as 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. You can optionally choose to purge only core runtime information associated with work items for performance gain during periods of high activity, and purge all obsolete information as part of your routine maintenance during periods of low activity.
To preserve electronic signature evidence for future reference, this program by default does not delete any notifications that required signatures or their associated signature information. If you do not need to maintain signature evidence, you can choose to delete signature-related information as well.
Note: This program does not delete ad hoc users or roles whose expiration date is null. To ensure that ad hoc users and roles are purged in a timely fashion after they are no longer needed, estimate how long they should be active and specify an appropriate expiration date when you call WF_DIRECTORY.CreateAdHocUser(), WF_DIRECTORY.CreateAdHocRole(), or WF_DIRECTORY.CreateAdHocRole2() to create them.
You can also optionally use this program to purge cached data from the WF_ATTRIBUTE_CACHE and WF_ENTITY_CHANGES tables. These tables contain cached data related to defining users as well as integration with LDAP and Oracle Directory Services.
Note: You can also use the Oracle Workflow Manager component of Oracle Applications Manager to submit and manage the Purge Obsolete Workflow Runtime Data concurrent program. See: Purging Workflow Data.
Additionally, you can use the Purge Obsolete ECX Data concurrent program to purge Oracle XML Gateway transactions according to Oracle XML Gateway-specific parameters. For information about this program and about the ECX: Purge ECX data with WF profile option, see: Purge Obsolete ECX Data Concurrent Program and Purge Obsolete Workflow Runtime Data Concurrent Program.
Navigate to the Submit Requests form in Oracle E-Business Suite to submit the Purge Obsolete Workflow Runtime Data concurrent program. When you install and set up Oracle E-Business Suite and Oracle Workflow, your system administrator needs to add this concurrent program to a request security group for the responsibility that you want to run this program from. The executable name for this concurrent program is "Oracle Workflow Purge Obsolete Data" and its short name is FNDWFPR. See: Overview of Concurrent Programs and Requests.
Submit the Purge Obsolete Workflow Runtime Data concurrent program as a request. See: Running Reports and Programs.
In the Parameters window, enter values for the following parameters:
| Item Type | Item type associated with the obsolete runtime data you want to delete. Leave this argument null to delete obsolete runtime data for all item types. |
| Item Key | A string generated from the application object's primary key. The string uniquely identifies the item within an item type. If null, the program purges all items in the specified item type. |
| Age | Minimum age of data to purge, in days, if the persistence type is set to 'Temporary'. The default is 0. |
| Persistence Type | Persistence type to be purged, either 'Temporary' or 'Permanent'. The default is 'Temporary'. |
| Core Workflow Only | Enter 'Y' to purge only obsolete runtime data associated with work items, or 'N' to purge all obsolete runtime data as well obsolete design data. The default is 'N'. |
| Commit Frequency | The number of records to purge before the program commits data. To reduce rollback size and improve performance, set this parameter to commit data after a smaller number of records. The default is 500 records.
Note: After performing a commit, the program resumes purging work items with the next subsequent begin date. In some cases, if additional items have the same begin date as the last item that was purged before a commit, the program may not purge all eligible items. To purge these remaining work items, simply rerun the program. |
| Signed Notifications | Enter 'N' to preserve signature evidence, including notifications that required electronic signatures and their associated signature information. Enter 'Y' to purge signature-related information. The default is 'N'. |
| Other Cached Data | Enter 'Y' to purge cached user definition data from the WF_ATTRIBUTE_CACHE and WF_ENTITY_CHANGES tables. Enter 'N' if you do not want to purge this data. The default is 'N'. |
Choose OK to close the Parameters window.
When you finish modifying the print and run options for this request, choose Submit to submit the request.