Run Orchestration Component

Run Orchestration Component

Run another orchestration job to completion. After the orchestration job completes, other orchestration components can be linked to this one depending upon success or fail.

Use this component to better organise complicated orchestration job flows by breaking them into simpler pieces which can be composed together in another orchestration job.


Property Setting Description
Name Text The descriptive name for the component.
Orchestration Name Select Choose an existing existing Orchestration jobs.
Be careful not to create circular references, or a job may never complete. As such, the current job cannot be input here.
Set Variables Select Many Define Copied job variables to be used by the called Orchestration. A variable can be added by clicking the + button, then selecting it from the dropdown list. A value can then be assigned to this variable to be used by the Orchestration. Note that the assigned value must be of the correct type as given when the variable was declared. If choosing a variable name that has been defined as both an environment and job variable, the job variable will be used.

If a Shared variable named 'Message' is passed using this method, it can be later exported from this component (keeping any changes to the value that occurred within the Run Orchestration job) using the 'Message' export variable.
Set Grid Variables Dialog Job Grid Variables for the Orchestration job being called are listed and, by default, are used by the called job in their default state. Selecting a Job Grid Variable and choosing an option other than 'Use Defaults' in the 'Set Values' dropdown menu allows users to overwrite Grid Variables data in that job. Users can choose to either define individual values ('Values') or map columns using Grid Variables from the calling job ('Grid'). See Grid Variables for more information.


This example imports some data from RDS in one orchestration job, restructures it in a transformation job, and then performs a schema copy in another orchestration job.

The component only requires a descriptive name, and the name of the orchestration job to run.

We don't want this Orchestration to use its default 'test' value, so we set it manually but setting 'Overwrite Variables' to 'Yes' and using the 'Set Variables' property to assign the 'test' variable a new value of our choosing.