Advanced business view configuration

This page explains advanced configuration topics for business views in Semarchy xDM.

Embedded collections

If the form used for a business entity contains embedded collections, then you can configure an embedded collection transition to configure which records are displayed in this embedded collection and how browsing takes place when clicking these records in the embedded collection.

Configure embedded collection transitions

To configure an embedded collection transition:

  1. In the Business View editor, scroll down to the Transition table.

  2. Select the parent business entity for the new transition.

  3. Click the Configure embedded collection transition Configure Embedded Collection Transition button in the toolbar of the transitions table. The Create New Transition wizard opens.

  4. In the Create New Transition wizard, set the following values:

    • Embedded Collection: Select one of the embedded collections of the form of your business entity.

    • Name: Enter the name for the transition.

  5. Click Next. The second step of the wizard configures the child business entity of the transition:

    • Select whether you want to create a new business entity or use an existing one.

    • If you choose to Create a New Business Entity, select an Entity and give a Name for the new business entity.

    • If you choose to Use an Existing Business Entity, select an existing Target Business Entity.

  6. Click Finish.

Configure embedded collection browsing

Embedded collection browsing options define how to navigate when a user clicks an item from an embedded collection placed in the form defined for a business entity.

  1. In the Business View editor, scroll down to the Transition table.

  2. Select the business entity in the table.

  3. In the Properties view, select the Embedded Collections finger tab.
    This table lists the embedded collections of the browsing form selected for the business entity.

  4. Click the Refresh configuration Refresh Configuration button in the Properties view toolbar to refresh the list of embedded collections.

  5. For each collection listed, select a Browsing Target:

    • Not Browsable makes embedded collection items not navigable.

    • Form opens a popup with the selected form when the collection item is clicked.

    • Business View opens the selected target business view in the same editor.

Advanced transitions

Configure infinite hierarchies

It is possible to create hierarchies with an infinite depth by creating a transition from a business entity to itself.

For example, to create a hierarchy of cost centers, create a business view with a Cost center as the root business entity (call it CostCenterBusinessEntity) and a root filter selecting only the cost centers with no parents (e.g., ParentCostCenter is null). Then add a transition using the self-relationship linking parent and child cost centers, and select the existing CostCenterBusinessEntity.

Use lineage navigation in transitions

Transitions allow browsing relationships created in the model, including lineage relationships. For example, you may create a transition showing the master records consolidated into a golden record, or the history of a golden record.

All lineage navigations are listed in Data access views, attributes, and lineage.

Depending on the view type (golden record, master record, etc.) used to browse a business view, irrelevant transitions are automatically hidden. For example, a golden-to-master-records transition does not apply when browsing a source record and does not appear.

When using a transition from a golden record to its master records or history, matching values in the attached master or history records are automatically highlighted (with a blue or yellow background) in the collection or form. Note that this background does not replace any field background configured in the collection or form itself.

In an MDM application, historical data and changes related to a golden record over time can be displayed in the Golden History Records view. While navigating this view, Oracle database users may notice that long text and binary attributes are not highlighted in yellow. This is due to a limitation in Oracle’s handling of character large object (CLOB) and binary large object (BLOB) data types, affecting the colorization of long text and binary attributes.