Configuring Application Mapping from LeanIX into Collibra

The integration allows you to map your Applications from LeanIX to Collibra.

Filtering Applications

To enable the synchronization of LeanIX Applications to Collibra, first you need to activate the mapping. To do so, navigate to the Application Mapping tab and set this mapping to active.

You can either map all Application Fact Sheets or a subset by configuring the filters.

Choosing Inbox Domain and Asset Type

For the synchronization to work, you first need to choose the target Inbox Domain and Asset Type.

For each Application Fact Sheet, the integration will create an asset of the selected Asset Type within the selected Inbox Domain.


Moving Applications into different Domains

If necessary, you can move the Assets into different Domains at a later time. The integration will still update the name, fields and responsibilities, but will not change back the Domain of the Assets.

Mapping Fields

The integration allows you to map the fields of your Application Fact Sheets from LeanIX into attributes on your assets in Collibra.
The integration supports mapping various Field types in LeanIX into different Attribute Types in Collibra. For more details, please refer to this table.
In case you select a Selection on both ends, you can also define how the values are to be mapped.

When selecting Attribute Types for Collibra, the options are grouped by the scopes/assignments. Default/Global scope attributes are grouped under "Global" and other Attribute Types under their respective scope (e.g. "Data Privacy").

Responsibilities of the Technology Assets

You have the option to map any subscription of the Responsible type that the integration will find on your Application Fact Sheet into Responsibilities on the corresponding asset in Collibra. To do so, you may choose any of the roles that are applicable to the subscription type Responsible for the Application Fact Sheet Type in LeanIX and map it to any role that is available within Collibra. You may also choose to create the users of LeanIX which are not present in Collibra, however, as mentioned in the warning, if you create responsibilities for new or existing users, depending of the license requirement of the selected role (e.g. AUTHOR), it might cause additional license costs for your Collibra usage!

Mapping the Relation to Data Objects

The integration allows you to map the Relation relApplicationToDataObject between your Applications and the Data Objects of your Conceptual Data Layer from LeanIX into Collibra.

The relation mapping can be done by either of the following strategies:

  1. Complex Relation
    Complex Relations will be created on the Application assets in Collibra.
  2. "Intermediate" Asset
    An "intermediate" asset will be created in Collibra for every relation on the Applications.
  3. Simple Relation
    A Simple Relation would be created on the Application assets in Collibra.

Simple Relation Strategy

To configure this strategy, you first need to select Simple Relation . Once selected, you will see the Relation Type field which you will have to select. Please note that, the Relation types shown in the dropdown are the relations that are configured on the selected "Application Mapping Asset Type".

Below you can see the example of Factsheet relations in LeanIX would be created in Collibra:

Complex Relation Strategy

To configure this strategy, first choose a Complex Relation in Collibra that is assigned to the Technology Asset type that you have chosen to be used for mapping the Applications. Make sure that this Complex Relation type is configured in a way that allows it to reference the Business Assets of your Conceptual Data Layer.

Please read the official documentation of Collibra to find more information on what a Complex Relation is and how you configure them.

Next, you can configure a Field Mapping for the fields that exist on the Relation within LeanIX to be mapped into attributes on the Complex Relation within Collibra.

Below you can see an example of an actual relation being mapped from LeanIX to Collibra.

"Intermediate" Asset Strategy

To configure this strategy, you first need to select Asset Mapping Inbox Domain and the Asset Type. The "intermediate" assets will be created in the selected Inbox Domain with the selected Asset Type.

Next, you need to select the Relations to which the Applications (Technology Assets in Collibra) and the related Data Objects (Business Assets in Collibra) should be mapped.

Now, you can also configure Field Mapping to map the fields on the relations in LeanIX to the
"intermediate" asset in Collibra

Below you can see an example of an actual relation being mapped from LeanIX to Collibra.

Support for "Archiving" of Applications

When you archive an Application Fact Sheet in LeanIX, the integration will by default then delete the mapped Asset in Collibra. To change this behavior, you can enable the "Soft Delete" flag.

When the "Soft Delete" flag is enabled, the integration will not delete the Asset in Collibra. Instead, it will add a tag called "deleted-in-leanix" to the Asset. This means that if a Fact Sheet is archived, the mapped Asset will have this tag to indicate that it has been deleted. Here's an example of what the Asset would look like with this tag:

Resource Backlink on Mapped Applications

All mapped Application Fact Sheets will contain a resource backlink to corresponding Collibra asset.
:warning: The backlink on the Application is only created on the next run, after the Application has been successfully mapped to Collibra.