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.

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.

Related Topics

About Events

About Application Links and Event Definitions