Page tree

Versions Compared


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

D toc


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

Flow Structure and




D s product
, the basic unit for organizing your work is the flow. The following diagram illustrates the component objects components of a flow and how they are related:

D caption
ObjectsAssets in a Flow


flow is is a container for holding one or more datasets, associated recipes and other objectsassets. This container is a means for packaging 

D s item
 for the following types of actions:


  • Copying
  • Execution of pre-configured jobs

  • Creating references between recipes and external flows

Imported Dataset

Data that is imported to the platform is referenced as an imported dataset. An imported dataset is simply a reference to the original data; the data does not exist within the platform. An imported dataset can be a reference to a file, multiple files, database table, or other type of data.


After you have created an imported dataset, it becomes usable after it has been added to a flow. You can do this as part of the import process or later.


recipe is a user-defined sequence of steps that can be applied to transform a dataset.

  • A recipe object is recipe is created from an imported dataset or another recipe. You can create a recipe from a recipe to chain together recipes.
  • Recipes are interpreted by 
    D s product
     and turned into commands that can be executed against data. 
  • When initially created, a recipe contains no steps. Recipes are augmented and modified using the various visual tools in the Transformer page.
  • For more information on the process, see Transform Basics.

In a flow, the following objects are asset types are associated with each recipe, which are described below:

  • Outputs
  • References

Outputs and Publishing Destinations

Outputs contain one or more publishing destinations, which define the output format, location, and other publishing options that are applied to the results generated from a job run on the recipe. 

When you select a recipe's output object objects in a flow, you can:

  • Define the publishing destinations for outputs that are generated when the recipe is executed. Publishing destinations specify output format, location, and other publishing actions. A single recipe can have multiple publishing destinations.
  • Run an on-demand job using the specified destinations. The job is immediately queued for execution.

Reference Datasets

When you select a recipe's reference object, you can add it to another flow. This object asset is then added as a reference dataset in the target flow. A reference dataset is a read-only version of the output data generated from the execution of a recipe's steps.

Flow Example

The following diagram illustrates the flexibility of object relationships between assets within a flow. 

D caption
Flow Example
Standard job executionRecipe 1/Job 1

Results of the job are used to create a new imported dataset (I-Dataset 2) from the Job Details page.

Create dataset from generated resultsRecipe 2/Job 2

Recipe 2 is created off of I-Dataset 2 and then modified. A job has been specified for it, but the results of the job are unused.


Chaining datasetsRecipe 3/Job 3

Recipe 3 is chained off of Recipe 2. The results of running jobs off of Recipe 2 include all of the upstream changes as specified in I-Dataset 1/Recipe1 and I-Dataset 2/Recipe 2.

Reference datasetRecipe 4/Job 4I-Dataset 4 is created as a reference off of Recipe 3. It can have its own recipe, job, destinations, and results.

Flows are created in the Flows page. 

Working with recipes

Recipes are edited in the Transformer page, which provides multiple methods for quickly selecting and building recipe steps.


  • Transform job: Executes the set of recipe steps that you have defined against your sample(s), generating the transformed set of results across the entire dataset.
  • Profile job: Optionally, you can choose to generate a visual profile of the results of your transform job. This visual profile can provide important feedback on data quality and can be a key for further refinement of your recipe.
  • When a job completes, you can review the resulting data and identify data that still needs fixing in the Job Details page.
  • For more information on the process, see Running Job Basics.


D s ed

connection is a configuration object that provides a personal or global integration to an external datastore. Reading data from remote sources and writing results are managed through connections.

  • Connections are not associated with individual datasets or flows.
    • Connections are not reflected in the above diagram.
  • Most connections can be created by individual users and shared as-needed.
  • Depending on the datastore, connections can be read-only, write-only, or both.
  • Connections are created in the Connections page.

Flow Schedules

D s ed

You can associate a schedule with a flow. A schedule is a combination of one or more triggers and the outputs that are generated from them.


  • A trigger is a scheduled time of execution. When a trigger's time occurs, all of the scheduled output destinations are queued for generation.
    • A schedule can have multiple triggers associated with it. Therefore, a flow can be scheduled for execution at multiple intervals.
  • A scheduled destination is an output associated with a recipe. This output is generated only when the schedule for the flow is triggered.
    • A scheduled destination is not tied to a specific trigger. When a trigger occurs, all scheduled destinations in the flow are generated.
    • A scheduled destination generates one or more publishing actions (outputs) from the recipe when triggered.
    • A recipe can have only one scheduled destination.
    • Each recipe in a flow can have a scheduled destination.
    • If a flow has a trigger but no scheduled destination, nothing is generated at trigger time.

Below, you can see the object hierarchy within a schedule.


Schedules are created for a flow through Flow View page.


D s ed

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 assets 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 assets that are executed as part of a plan 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.