Data map extensions

Data map extensions represent the generalized mapping between two object definitions. To define data map extensions, first define object definitions. Object definitions provide a means, depending on the application connectors used in a process, by which you can dynamically browse custom fields and incorporate them into mappings. Custom objects, however, cannot be dynamically browsed and mapped.

Data map extensions can be used in conjunction with connection settings extensions. Connection settings extension values specify connection settings for the data sources from which source and destination profiles will be loaded when data map extension values are set.

Use data map extensions either to override field-to-field mapping or to add fields to flat file profiles in map components when a process is deployed.

To override field-to-field mapping

The first type allows field-to-field mapping defined by map components within a process to be augmented, replaced, or overridden when the process is deployed. You can map to destinations that have already been mapped in the original maps. However, you cannot map to a destination that has already been mapped by an override mapping. You can add functions to data map extensions. All function types except user-defined functions are available. The Simple Lookup function type can be used to return a single value.

The mapping controls are similar to those in the map component creation interface, which is drag-and-drop. Mapping overrides are displayed as black lines.

If at any time you need to change the mappings, you have the option to Clear all mappings and start over.

These field mapping extensions have the following limitations:

• You cannot select different source or destination profiles.

• Only mappings using XML or flat file profiles with single-record formats are supported.

• If the original maps contain map functions, those map functions are displayed in a gray color and disabled. You can view but not change the configuration and default values of the map functions.

• For function types that require a separate component, such as connection and operation components in connector calls, you can select only components that are defined in the original process. If you use extensions with integration packs, the Connector Call function is available but cannot be used. This is because no connection or operation components are available in the Connector Call dialog.

• You cannot add cached data to the source profile.

• You cannot add default values to the destination profile.

• The Map Function Ordering dialog is not available. Functions in the original maps are processed first, followed by functions in the Extensions dialog.

To add fields to flat file profiles

The second type of data map extension allows the addition of fields to flat file profiles used in map components within a process when the process is deployed. The profiles must have single-record formats, as opposed to multiple- or nested-record formats. This type of extension applies only to the map component for which the extension is defined; other maps that use the same profile are not automatically extended.

Defining data map extensions for a process

Add or edit data map extensions in the Extensions dialog.

1. Open the process and click the Extensions link above the process canvas.

   The Extensions dialog opens.

2. Select the Data Maps tab.

   Source and destination object definitions are listed in pairs. A list of the map components that reference profiles specified in those object definitions are grouped below each object pair.

3. For the first object pair, lock fields in the source profile to prevent them from being customized:

   1. Click Choose Locked Fields for Source Profile.

      The Locked Fields dialog opens.

   2. For each field you want to lock, select the check box adjacent to the element name.

   3. When you are done locking fields, click OK.

      The Locked Fields dialog closes, and focus returns to the Data Maps tab.

4. For the first object pair, lock fields in the destination profile to prevent them from being customized. Click Choose Locked Fields for Destination Profile, and select the fields in the Locked Fields dialog as in step 3.

5. For the first object pair, select the check box for each data map you would like to extend.

6. Repeat steps 3–5 for each additional object pair.

7. When you are finished defining extensions, click OK.

8. Click Save.

After defining data map extensions, you need to set values for them. See the topic Setting Extension Values linked below.