About Orchestration Links

An orchestration link defines the data that is sent to an orchestration workflow when a transition is executed or a state is reached in an application workflow. The values from the primary table fields that you select and any additional data items you define are passed to the orchestration workflow that you select when you create the orchestration link. For synchronous orchestration workflows, you also select primary table fields whose values should be returned from the orchestration workflow.

Remember: Because changes to an orchestration link propagate to the inputs and outputs of an orchestration workflow, the orchestration link is the primary area in which the inputs and outputs are defined.

Orchestration links are displayed directly under the Orchestration Links heading in App Explorer.

Event without Reply is added automatically. This defines event data for asynchronous orchestration workflows that are called from an application workflow when a transition is executed. This orchestration link can be exported and then imported into other orchestrations so they can handle the events that the application raises. These orchestrations do not have to be in the same process app.
Important: If you want the "Event without Reply" to be used by an asynchronous orchestration workflow in another process app, lock it before you export it, using the Event Editor. The definition includes an event type name (constructed from the application, state, and transition names) and the extension data fields that will be sent with the event. If you lock the definition, it becomes portable, because these names will not change in the event definition, even if the corresponding field names change in the original process app.
Other orchestration links are for synchronous orchestration workflows that are called from an application workflow when a transition is executed or a state is reached. These orchestration links are typically added when you create a new synchronous workflow through the Action Wizard. For more information, see Using the Action Wizard.

External Events

The orchestration links described above define inputs based on primary table fields in the calling application. Another use case is when an orchestration workflow needs to be called by one or more applications with different primary tables. This orchestration workflow could be defined as an interface to a particular application or as an interface to an external product.

To handle this use case, first export the "Event without Reply" from the application or export the event definition from the orchestration. Then import what you exported into the calling application. These orchestration links are displayed under the External Events subheading in App Explorer. In the Action Wizard, you map the orchestration inputs to the primary table fields of the calling application.

For instructions, see Tutorial: Calling an Orchestration Workflow from Any Application.

About Orchestration Links

External Events

Related Topics