Embedded Dataflows

An embedded dataflow reduces the number of stages displayed on the Enterprise Designer canvas at one time by grouping stages together. The grouped stages then appear as a single stage. You can use embedded dataflows to:
  • Simplify the layout of complex dataflows by grouping stages together and having them represented as one stage on the canvas.
  • Process records in groups using the iteration feature.
  • Use a value in a field to set stage options in the embedded dataflow.

You can add an unlimited number of embedded dataflows to a dataflow, and you can put embedded dataflows within embedded dataflows.

Differences Between Embedded Dataflows and Subflows

There are two major differences between an embedded dataflow and a subflow. First, iteration processing is only available in embedded dataflows. Iteration allows you to process groups of records together for purposes such as aggregating records for processing or setting stage options based on field values. The second difference between an embedded dataflow and subflow is that an embedded dataflow cannot be used in more than one dataflow. If you want to reuse a portion of a dataflow in multiple dataflows, create a subflow instead of an embedded dataflow. Embedded dataflows can be converted into subflows if you decide you want to reuse an embedded dataflow in other dataflows, but when you convert an embedded dataflow to a subflow its iterations options are removed.