Use the following Oracle Workflow Administrator windows to help manage your Workflow processes.
For more information about these windows, see Oracle Workflow Developer's Guide and Oracle Workflow User's Guide.
This process is necessary for new events and subscriptions added as a result of creating a new XML message. The seeded business events and event subscriptions delivered by the Oracle E-Business Suite have already been registered. There is no need to register a seeded event subscription that was configured during implementation.
Use the Events window to add a new business event.
Use the Subscriptions window to add a new subscription to consume the new event.
Use the Developer Studio to view the seeded item types delivered by Oracle Workflow Business Event System, Oracle XML Gateway, and Oracle E-Business Suite modules.
Use the Events window to view the seeded business events delivered by Oracle Workflow Business Event System, Oracle XML Gateway, and Oracle E-Business Suite modules.
Select the business event and click on Edit Subscription to proceed to the Subscriptions window to view the associated subscriptions.
From the Subscriptions window, select the subscription and click Edit to configure the subscription. Click Delete to delete the subscription. You can modify the rule function or Workflow process defined for the subscription.
Use the Worklist window to view and respond to notifications awaiting your attention.
To purge workflow or non-workflow related XML Gateway transaction data, Oracle XML Gateway allows you to use the following concurrent programs to purge XML Gateway transactions:
To purge non-workflow related XML Gateway transactions, Oracle XML Gateway lets you use the Purge Obsolete ECX Data concurrent program to exclusively purge XML Gateway transaction data based on transaction type, transaction subtype, and date range.
Note: Since Workflow purge is associated with item_type and item_key, XML Gateway logs do not have these parameters available all the time. In case of inbound transaction item_type and item_key parameters are not available, you can submit the Purge Obsolete ECX Data concurrent program to specifically purge XML Gateway transaction data.
Parameters and Purge Behavior
| Parameters | Expected Behavior |
|---|---|
| Transaction Type | All data corresponding to that specific Transaction Type will be deleted. |
| Transaction Type Transaction Subtype | All data corresponding to that specific Transaction Type and Subtype will be deleted. |
| Transaction Type Transaction Subtype From Date | All data corresponding to that specific Transaction Type and Subtype will be deleted after the specified date. |
| Transaction Type Transaction Subtype From Date To Date | All data corresponding to that specific Transaction Type and Subtype will be deleted within the specified date range. |
| From Date | All data after the specified date will be deleted regardless of Transaction Type and Subtype. |
| From Date To Date | All data within the specified date range will be deleted regardless of Transaction Type and Subtype. |
| No parameter is given | All data will be deleted regardless of Transaction Type, Subtype, and date range. |
Use the Submit Requests form in Oracle E-Business Suite to submit these concurrent programs.
Note: Commit Cycle will be of 500 rows as it is done in Workflow Purge.
When purging workflow related XML Gateway transactions, use the Purge Obsolete Workflow Runtime Data concurrent program instead. This concurrent program is used in conjunction with the 'ECX: Purge ECX data with WF' profile option which lets you have an option to either purge XML Gateway data along with workflow data or purge workflow data only.
When the Purge Obsolete Workflow Runtime Data concurrent program is submitted, the 'ECX: Purge ECX data with WF' profile value will be retrieved to determine whether XML Gateway data will be purged together with workflow data or only workflow data will be purged.
If the profile value is set to 'Y' (default), then all XML Gateway data along with workflow data will be purged.
If the profile value is set to 'N', then XML Gateway data will not be purged with workflow data, but only workflow data will be purged.
For more information on 'ECX: Purge ECX data with WF' profile option, see Define System Profile Options.
Note: If you are using the version of Oracle Workflow embedded in Oracle E-Business Suite 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, see the Oracle Applications Manager online help.