- When a plan is triggered:
A snapshot of the objects in the plan is capture. This snapshot defines the set of tasks that are executed as part of a plan run.
NOTE: A snapshot does not capture the objects underlying the tasks. After a snapshot is taken, subsequent changes to the underlying flows could impact the outcome of the flow tasks when they are later executed during the plan run.
- The set of tasks in the plan are triggered in the order listed in the plan.
- All of the dependencies for any task are also executed. For example, if a flow output requires the outputs from another upstream flow, then that flow's output is also generated.
- If one task fails to execute, the other tasks are not executed.
- For more information on plans, see Overview of Operationalization .
- From the left nav bar, click the Plans icon.
- The Plans page is displayed. See Plans Page.
- In the Plans page, click Create. A new plan with the name
Untitled - Xis created, where
Xis a number.
Untitled - Xto enter a plan name and description.
- Your plan is saved and displayed in Plan View. See Plan View Page.
In some scenarios, you may need to branch plan execution steps based on the results of a task in the plan. For example, you may need to send separate messages using an HTTP task depending on whether a flow task succeeds or fails in execution. You can create branches in the plan graph by adding task execution rules and parallel nodes, which run based on the success and failure states of your plan runs.
To begin this simple example:
- Create your first task, which is a flow task in the above example. For more information, see Add Tasks above.
- Complete the following sections.
Add Task Execution Rule
Next, you create the first HTTP task that results from the above task and the execution rule that determines when it runs.
- This task should run based on the successful execution of the flow task.
- A task execution rule is a condition that is tested after a flow task has run to determine if the task that is downstream of it is executed as a result. In this case, you create an
- Click the plus icon below the existing flow task node.
- Select the HTTP task type and enter information in the required fields. See Add HTTP Tasks above.
- Click the link connecting the created HTTP task node and its previous task node and select
The HTTP task is executed only when the flow task has run successfully.
Add Parallel Task
Next, you can create the HTTP task that runs when the flow task fails.
- Click the plus icon below the existing flow task node and select Add a parallel node. A parallel node is added to the plan graph. See Example below.
- Select the HTTP task type and enter information in the required fields. See Add HTTP Tasks.
- Click the link connecting the new HTTP task and its previous task node and select