Previous	Next		Contents	Index	Glossary

This program purges obsolete runtime information associated with work items, including status information and any associated notifications and Oracle XML Gateway transactions. By default, 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 or 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.

Navigate to the Submit Requests form in Oracle Applications to submit the Purge Obsolete Workflow Runtime Data concurrent program. When you install and set up Oracle Applications 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. See: Overview of Concurrent Programs and Requests, Oracle Applications System Administrator's Guide and Running Reports and Programs, Oracle Applications User's Guide.

You can supply the following parameters for the Purge Obsolete Workflow Runtime Data concurrent program:

• Item Type--The item type to purge. Leaving this field blank defaults to purging the runtime data for all item types.

• Item Key--The item key to purge. Leaving this field blank defaults to purging the runtime data for all item keys.

• Age--Minimum age of data to purge, in days.

• Persistence Type--The persistence type to be purged, either 'TEMP' for Temporary or 'PERM' for Permanent. The default is 'TEMP'.

• 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'.

• Transaction Type - The Oracle XML Gateway transaction type to purge. Leave this field blank to purge the runtime data for all transaction types.

• Transaction Subtype - The Oracle XML Gateway transaction subtype to purge. The transaction subtype is a code for a particular transaction within the application specified by the transaction type. Leave this field blank to purge the runtime data for all transactions of the specified transaction type.

Note: If you are using the version of Oracle Workflow embedded in Oracle Applications and you have implemented Oracle Applications Manager, you can use Oracle Workflow Manager to submit and manage the Purge Obsolete Workflow Runtime Data concurrent program. For more information, please refer to the Oracle Applications Manager online help.