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
editionsawsent,awspro,awspr


d-excerpt

Explore the objects that you create and their relationships. Flows, imported datasets, and recipes are created to transform your sampled data. After you build your output objects, you can run a job to transform the entire dataset based on your recipe and deliver the results according to your output definitions.

...

For more information, see Overview of Automator.

Plans

D s ed
rtrue
editionsawsent,awspro,awspr

A plan is a sequence of triggers and tasks that can be executed across multiple flows. A plan is executed on a snapshot of all objects at the time that the plan is triggered.

...

.

  • A task is an executable action that is taken as part of a plan's sequence. For example, task #1 could be to execute a flow that imports all of your source data. Task #2 executes the flow that cleans and combines that data. Example task types:
    • A flow task is the execution of the recipes in a specified flow, which result in the generation of one or more selected outputs.
      • A trigger for a plan is the schedule for its execution.
      • A snapshot is a frozen image of the plan. This snapshot of the plan defines the objects that are executed as part of a plan
    is used plan runs
      • run.
    • An HTTP task is a request submitted by the product to a third-party server as part of the sequence of tasks in a plan. For example, an HTTP task could be the submission of a message to a channel in your enterprise's messaging system.

For more information, see Overview of Operationalization.

...