Creating Blenders

When you create or open a blender, it is displayed on a named tab.

The blender wizard is used to define the parameters and criteria for the blender. The wizard content is organized across Source, Style, Filters, Properties, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.

To create a blender:

1. On the Home page, select Blend.
2. Click .
3. On the Source tab, select source and target versions or version variables for the blender.
4. Perform an action:

   • Select Blend all Hierarchies to blend all hierarchies in the selected versions.

     Note:

     If you select this option, the Use Profile Defaults For All Hierarchy Sets option is required.

   • Deselect Blend all Hierarchies and click New.

     1. On the Source tab, select the hierarchy and top node mappings to blend.

     2. On the Target tab, do one of the following:

        • To map the hierarchy and top node from the source version to the same hierarchy and top node in the target version, select Specified from the drop-down list, and then select Use Same as Source

        • To map the hierarchy and top node from the source version to a different hierarchy and top node in the target version, select Selected from the drop-down list, and then select the hierarchy and top node in the target version.

     3. Optional: On the Domain Options tab, select a domain property.

     4. Click OK.

   Note:

   You can select Use Profile Defaults For All Hierarchy Sets to use default values for all hierarchy/top node sets. You set the profile defaults for properties on the Properties tab. If you deselect this option, you have the option of choosing which hierarchies should use the defaults and which should not when you select hierarchy/top node pairs.

5. On the Style tab, do the following:

   • Select from the following structure options:

     • Process Structure — To blend structural elements, such as nodes and hierarchy relationships.

     • Allow Hierarchy Creation — To create hierarchies in the target version that exist only in the source version.

       Note:

       If this option is not selected and there are hierarchies that exist in the source but not in the target, then an error occurs.

     • Allow Leaf Promotion — to promote a node with children in the source to a limb in the target.

       Note:

       If a node in the source has children, but its corresponding node in the target is a leaf node (an outermost node with no children allowed), then this option enables the Blender to promote the node to limb status. The child nodes from the source are then added to the limb node in the target.

   • Select from the following property options:

     • Process Properties — To blend property values

     • Disable Realtime Validations — To turn off the real-time validations on the target version prior to blending. This setting only applies if the target version is detached. If the target version is saved (not detached) then validations are still enabled regardless of this setting.

       Note:

       Real-time validations can prevent changes from being propagated to the target.

     • Process Version Validation Assignments — To process version-level validation assignments from the source to the target

   • In the Domain Options section, specify how domain names are assigned by selecting an option:

     • None––Domains names are not used.

     • Select a Domain––Specify a single domain to assign to all nodes.

       Note:

       If you select this option, select the domain to assign to all nodes.

     • Select a Domain Property––Select a domain holding property from the drop down list.

   • Optional: Select Assign Domains to Target Version.

6. On the Filter tab, select from these options on the Profile Defaults tab or the Hierarchy Overrides tab.

   Note:

   If you selected Use Profile Defaults for All Hierarchy Sets in step 3, make selections on the Profile Defaults tab. If any hierarchy sets exist and any are set to NOT use defaults, then the Hierarchy Overrides tab is enabled. Provide overrides for each hierarchy set on this tab.

   • Process Inserts––To insert any nodes existing only in the source hierarchy to the target hierarchy.

   • Process Removes––To remove any nodes existing only in the target hierarchy according to the setting in the Remove Mode list and the Remove Indicator list.

     If you selected Process Removes, select one of the following Remove Modes:

     • Remove––Node is immediately removed during blending

     • Mark––Node is marked for later removal

       When the Remove Mode is set to Mark, the Remove Indicator option designates which property contains the value showing that the node is flagged to be removed. The remove indicator property must be created as a local, Boolean property. For information on creating properties, see the Oracle Data Relationship Management Administrator's Guide.

   • Process Moves––To move any node which has a different parent in the source to that parent in the target.

   • Process Activations––To process node activations (inactivate and reactivate) from the target to the source.

   • Process Hierarchy Validation Assignments––To process the hierarchy level validation assignments from the source to the target.

7. On the Properties tab, from Property Selection, select one of the following ways to blend properties:

   • All Excluding Val/Access––All properties are blended; excludes properties used for node-level validations and for node access group leaf and limb-level settings.

   • None––No properties are blended.

   • Selected––The selected properties are blended.

8. From Property Propagate Mode, select one of the following modes to determine how the property is populated in the target.

   Note:

   If you selected Use Profile Defaults for All Hierarchy Sets in step 3, make selections on the Profile Defaults tab. If you did not select to use profile defaults, make selections on the Hierarchy Overrides tab.

   • Force––The property is assigned for every node in the target, whether that property is defined at that node, is inherited, or derived.

   • Difference––Populates the property for any node where the value is different, regardless of how that property is populated in the target.

   • Defined––The property is blended only when it is specifically defined for the node in the source.

9. Optional: Select Propagate Property Locks if you want inheritance locks in the source to be blended to the target.
10. On the Target tab, select the Target version:

    • Use Selected Target––To blend changes into the selected target version.

    • Copy to New Version––To blend changes into a copy of the selected target version.

      Note:

      If you select this option, you must specify a name and description for the new version.

11. Enter a value for Max Iterations.

    Note:

    This value determines the maximum number of attempts the Blender performs in reconciling the Source and Target versions. This prevents the Blender from running indefinitely in the case of irresolvable conflicts. The recommended value is 3.

12. Enter a value for Max Errors.

    Note:

    This value sets the maximum number of errors that can occur during processing before the Blender stops without completion.

13. Make selections for the following blender status properties options:

    • Clear Values––to set all Blender Status Property values to False during processing.

    • Populate Values––to set each Blender Status Property to True during processing.

    • Version Blended––The name of the property that will be set to TRUE if the version has been blended. This must be a defined, boolean, version level property.

    • Node Moved––The name of the property that will be set to TRUE if the node was moved by the blend. This must be a defined, boolean, local node level property.

    • Node Created––The name of the property that will be set to TRUE if the node was created by the blend. This must be a defined, boolean, global node level property.

    • Local Node Changed––The name of the property that will be set to TRUE if the node had local properties changed by the blend. This must be a defined, boolean, local node level property.

    • Node Assigned to Domain––The name of the property that will be set to TRUE if the node has a domain assigned.

    • Hierarchy Blended––The name of the property that will be set to TRUE if the hierarchy has been blended. This must be a defined, boolean, hierarchy level property.

    • Global Node Changed––The name of the property that will be set to TRUE if the node had global properties changed by the blend. This must be a defined, boolean, global node level property.

    • Node Inserted––The name of the property that will be set to TRUE if the node was inserted by the blend. This must be a defined, boolean, node level property.

    • Leaf Promoted––The name of the property that will be set to TRUE if the node was promoted from a leaf to a limb by the blend. This must be a defined, boolean, global node level property.

14. Click to save the blender.

    You are prompted to define a name, description, and an object access group for the blender. Select a custom group or one of the following:

    • User––Personal objects that are only available to an individual user to view and run.

    • Standard––Public objects that are available to all users to view and run. Only Data Manager users can create and modify standard blenders.

    • System––Restricted objects that are only available to Application Administrator role users to view and run.