New Feature - Optimize Capability in Data Map

The data map in the BPM Connect data pipeline has been enhanced to support optimization at a pass level.  In the 313 pack of BPM Connect, you will now see a optimize column option in the data map.  This flag can be set as Y/N.

When a row is flagged as "Optimize", this will communicate to the Data Map engine to put the entire Pass into optimize mode.  Columns that are flagged "Y" in an optimized Pass, will be optimized.  Columns that are flagged "N" in an optimized will be disregarded.  The following rules apply when using the optimize flag:

1. The optimization flag can only be used on passes that contain "Column" Source Types, meaning it cannot resolve "Value" or "SQL" Source Types.  If an Optimize pass attempts to use "SQL" or "Value" source types, this will result in error. 
2. Optimization flag cannot be used on a pass that contains CTOR functionality
3. Optimization flag cannot be used on a pass that contains RTOC functionality (RTOC passes are optimized by their very nature)
4. Fields in an Optimized pass that are not flagged as Optimize = N will  be disregarded

Optimize will use any data type, ie. Natural, Dimension or Measure. However,depending on the data type chosen, the behavior will vary.  If a measure data type is used, it will be summed during the optimization process.  If dimension or natural data types are used, they will be grouped (distinct).

NOTE: Apply Data Map 7.1 enhancement patch to the 313 pack to get first and last pass capability.