Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next

d-toc

d-s-ed
rtrue
editionsgdpent,gdppro,gdppr,awsent,awspro,awspr

...

Excerpt

...

plan is a sequence of tasks that are executed manually or based on a schedule.

...

 Plans can be used to automate the execution of multiple related tasks, such as all of the outputs generated from a set of multiple related flows.

  • 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.

      Info

      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.

...

Info

NOTE: Parameter values are applied to a plan, but you cannot apply parameter overrides to the plan. You can apply flow parameter overrides on individual flows , which in Flow View. These overrides are applied at the time of plan execution. For more information, see Manage Parameters Dialog.

Workflow steps:

  1. Identify the tasks that you wish to execute. 

    Info

    NOTE: You must have access to any flows that you wish to execute. See Flows Page.

  2. Add a task.
    1. In Plan View, click the Plus icon at the bottom of your plan. 
    2. Specify the task to execute.
  3. Repeat the previous step to add additional tasks as needed.

    Tip

    Tip: You can insert tasks between other tasks. Use the Plus icon between two plan objects.

  4. To test your plan, click  Run now. The plan is immediately executed. 
  5. Edit the plan and repeat the above steps until the plan is ready for production runs. 

    Tip

    Tip: While a plan is in development, you may wish to disable its schedule, which prevents execution according to the schedule. You can still run test executions using the Run Now button.

  6. Create the schedule for the plan. 
    1. In the context menu for the plan, select Schedule.
    2. Specify one or more triggers for the schedule. When a trigger occurs, the plan is queued for execution.
  7. When ready, the plan runs at the time scheduled in the trigger.

...

  1. From the left nav bar, click the Plans icon.
  2. The Plans page is displayed. See Plans Page.
  3. In the Plans page, click Create. A new plan with the name  Untitled - X is created, where X is a number.  
  4. Click the  Untitled - X to enter a plan name and description.

  5. Your plan is saved and displayed in Plan View. See  Plan View Page.

In Plan View, you create the objects that are part of your plan. These include:

...

  1. When you first open Plan View, you should see an empty plan:

    D caption
    Plan View - empty plan
  2. To begin, do one of the following:
    1. From the Plan View context menu, click Schedule.
    2. Click the big circle. 
  3. In the right context panel, click Create schedule.
  4. In the Add Trigger panel, you can specify the triggers when the plan is executed. You can specify one or more triggers:

    D caption
    Add trigger(s)
  5. For each trigger:

    1. Timezone: Specify the timezone that applies to the scheduled time. For more information on timezones, see Supported Time Zone Values.

    2. Frequency: You can specify the frequency of when the schedule is triggered.

      1. In each trigger, you can specify multiple On values (e.g. Same time on Sunday and Monday).

      2. As needed, you can specify the On value using a modified form of cron job syntax. For more information, see cron Schedule Syntax Reference.

  6. To add more triggers, click Add another trigger and specify it.

    1. To delete a trigger, click the X next to it.

  7. Parameter overrides:

    1. If the flows in your plan contain parameters, you can apply overrides to the parameter values. 
    2. Overrides provided in this panel are applied only when the trigger is executed.

      Info

      NOTE: Multiple values are ok for plan parameters, as long as the parameter values do not conflict. If you see a warning icon next to a set of multiple parameter values, then you must fix this conflict in Flow View, or the plan fails to execution. For more information, see Manage Parameters Dialog.

    3. You can apply overrides through Plan View, too. For more information, see Manage Parameters Dialog.  
  8. To save your schedule, click Save.

  9. In the context panel, you can make changes to your schedule:
    1. After saving, the schedule is automatically enabled. To disable the schedule, use the slider bar. 

      Info

      NOTE: A plan cannot be executed if the schedule for it has been disabled.

    2. To make changes to the schedule and its triggers, click Edit.

...

Subsequent runs of the plan use this new value as the override for the parameter. For more information, see Plan View for Flow Tasks

...

.

...

Create Branching Plan

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. 

...

  1. in the upper-right corner of Plan View, click the Runs link.
  2. In the Plan Runs page, you can track the progress of your plan run.
    1. The most recently triggered plan run is displayed.
    2. If you have executed multiple runs, you can use the angle brackets next to the timestamp for the run.
  3. For tasks in progress, you can click the task to display information in the context panel.
  4. To see the details for the plan run, click the Outputs tab. Then, click Job details. See Job Details Page.

You can monitor the progress of your plan runs and review all previous plan runs. See ones in the Plan Runs Page.page.

D s also
inCQLtrue
label(label = "plan")