| Array fan-out |
Executes, for each value contained in an array, the step between the fan-out and the
funnel-in, in parallel |
| Exit status |
Sets up a special exit status message within the workflow |
| Federated workflow |
Launches workflows on a remote Orchestrator instance and either gets the ID and outputs
or just gets the ID and does not wait for the outputs of the remote workflow |
| Filter |
At run time, selects the step to execute next based on defined conditions |
| Funnel-in |
Pairs with a fan-out and converges the multiple parallel threads back into
one |
| Merge point |
Reconciles the inputs coming from different branches of logical statements. It provides
the ability to define pairs of inputs that get merged. Such steps can be used without inputs to
clarify branching in a complex workflow |
| Orchestrator Alert Entry |
Enters custom alerts into Orchestrator |
| Snapshot |
Takes a snapshot of the Orchestrator configuration. |
| Sub-workflow |
Wraps an entire workflow—defined separately—into a step that can be used in another
workflow, thus facilitating the creation of a complex workflow composed of sub-workflows.It is
similar to the Workflow plugin; however, Sub-workflow and Workflow Launcher differ in the
following ways:
- Workflow Launcher launches another workflow and then the current workflow immediately
proceeds; this behavior is asynchronous compared with Sub Workflow, which waits for the
launched workflow to return before proceeding with the current workflow.
- A Workflow Launcher step is Complete when it successfully launches the workflow
to which it is configured, whereas a Sub Workflow step is Complete when the
sub-workflow it launches has completed its execution.
|
| User lookup |
Looks up information about Orchestrator users identified by ID, name, login, or email
address. |
| Work Order Metadata |
Provides information about work orders and customizes the label display for
them. |
| Workflow Launcher |
Launches one workflow from within another. It is similar to the Sub-workflow plugin;
however, Workflow Launcher and Sub-workflow differ in the following ways:
- Workflow Launcher launches another workflow and then the current workflow immediately
proceeds; this behavior is asynchronous compared with Sub Workflow, which waits for the
launched workflow to return before proceeding with the current workflow.
- A Workflow Launcher step is Complete when it successfully launches the workflow
to which it is configured, whereas a Sub Workflow step is Complete when the
sub-workflow it launches has completed its execution.
|