When you need more than 3 requirements to control stage and step execution, use an
evaluation flow. Select the Evaluation Flow tile in the New Flow window to create an evaluation
flow.
When you select the Evaluation Flow tile in the New Flow window, you create an evaluation
flow that contains a predefined Boolean output variable named
isOrchestrationConditionMet.
Initialize isOrchestrationConditionMet to false, and to indicate that
the custom conditions are met, set isOrchestrationConditionMet to true.
Evaluation flows only return a value for isOrchestrationConditionMet.
Values for any other output variables are discarded.
Evaluation Flow Execution
Every time an asynchronous background step, an interactive step, or a MuleSoft step within
the current stage is completed, the orchestration evaluates the conditions for that stage
and its steps. To trigger an evaluation of conditions for the current stage and its steps,
publish an orchestration event with $Orchestration.Instance
The status of each stage or step determines which conditions the orchestration checks. If
the condition being checked relies on an evaluation flow, the evaluation flow runs.
When a stage is in progress, the orchestration determines whether it can be completed.
For each not started step within the current stage, the orchestration determines whether
the step is ready to start.
For each in progress interactive step within the current stage, the orchestration
determines whether the step can be marked as completed.
Running Context of an Evaluation Flow
In API version 60.0 and later, evaluation flows can be run only in system context without
sharing and have access to all data.
In API version 58.0 and 59.0, evaluation flows always run in system context.
In API version 57.0 and earlier, evaluation flows run as specified in the flow’s How to Run
the Flow advanced option.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
