| Previous | Next |  | Contents | Index | Glossary

## Submit Concurrent Program Activity

The Submit Concurrent Program activity is available only in the version of Oracle Workflow embedded in Oracle Applications. It submits an Oracle Applications concurrent program from your workflow process, but does not wait for it to execute or complete. Once this activity submits a concurrent request, the Workflow Engine continues with the next activity in the process.

> Attention: Generally, the context for your process' item type is always set if your session is initiated from an Oracle Applications form. However, if an interrupt occurs in your session, for example, due to a notification or blocking activity, you must ensure that the context is set by calling `FND_GLOBAL.APPS_INITIALIZE(user_id, resp_id, resp_appl_id)` in SET_CTX mode in your Selector/Callback function. See: Standard API for an Item Type Selector or Callback Function.

The Submit Concurrent Program activity calls the standard Oracle Application Object Library API FND_WF_STANDARD.SUBMITCONCPROGRAM.

#### Activity Attributes

The Submit Concurrent Program activity has the following activity attributes:

- Application Short Name--Short name of the application to which the concurrent program is registered.

- Program Short Name--Short name of the concurrent program to run.

- Number of Arguments--Number of arguments required for the concurrent program.

- Item Attribute Name--Name of the item attribute to store the concurrent program request ID.

- Argument1, Argument2,...Argument100--Value of each concurrent program argument, ordered to match the correct syntax of the concurrent program. Up to 100 arguments are allowed, but you should only specify as many argument values as you define in the Number of Arguments activity attribute. See: To Define Activity Attribute Values.

| Previous | Next |  | Contents | Index | Glossary