Deploying derived relation types
This topic explains how to deploy derived relation types (DRTs) to end users by assigning the derived relation types to asset types and integrating them into asset type layouts.
Assigning a DRT to an asset type
Once you define a derived relation type, the rest of the process is similar to that of an explicit relation type. The next step is to assign your derived relation type to an asset type. The ways in which you can assign a derived relation type to an asset type depend on the asset type layout, which can be dynamic, out-of-the-box, or custom.
With a dynamic asset layout
If the asset type to which you want to assign your derived relation type has a dynamic asset layout, you only need to add the derived relation type to the Characteristics page. Doing so automatically updates the layout, meaning that the derived relation type you added becomes visible on the asset pages.
-
On the main toolbar, click
→
Settings.
The Settings page opens. - Click the Operating model tab.
Operating Model settings are shown. - On the Asset types page, click the name of the asset type corresponding to the head, tail, or subtype of your derived relation type.
- On the asset type page, in the left pane, click the relevant assignment and click Characteristics.
- On the Characteristics page, click Add a Characteristic.
- In the Add a Characteristic dialog box, select the DRT to assign to the asset type.
The DRT appears at the bottom of the table on the Characteristics page.
With an OOTB or custom asset layout
If the asset type to which you want to assign your derived relation type has an OOTB or published asset layout, you have the following two options.
Option 1: Add the DRT to the Characteristics page and asset layout
-
On the main toolbar, click
→
Settings.
The Settings page opens. - Click the Operating model tab.
Operating Model settings are shown. - On the Asset types page, click the name of the asset type corresponding to the head, tail, or subtype of your derived relation type.
- On the asset type page, in the left pane, click the relevant assignment and click Characteristics.
- On the Characteristics page, click Add a Characteristic.
- In the Add a Characteristic dialog box, select the DRT to assign to the asset type.
The DRT appears at the bottom of the table on the Characteristics page. - Click Edit layout.
- On the Edit layout page, drag the derived relation type from the left pane to the layout and click Publish.
Your derived relation type is shown on the asset pages.
Option 2: Add the DRT directly to the asset layout
-
On the main toolbar, click
→
Settings.
The Settings page opens. - Click the Operating model tab.
Operating Model settings are shown. - On the Asset types page, click the name of the asset type corresponding to the head or tail of your derived relation type, or a subtype of the head or tail.
- On the asset type page, in the left pane, click the relevant assignment and click Characteristics.
- On the Characteristics page, click Edit layout.
- On the Edit layout page, in the left pane, click Add a Characteristic.
- In the Add a Characteristic dialog box, select the derived relation type to assign to the asset type, select the Add directly to layout checkbox, and click Add.
- On the Edit layout page, click Publish.
Your derived relation type is shown on the asset pages.
Showing a derived relation on an asset page
Now that your derived relation type is assigned to the head or tail asset type, the asset page is ready to show derived relations. When you open an asset page whose asset type assignment has a layout that contains your derived relation type, the derived relation appears on the Summary tab. It may take a while for the derived relation to appear, depending on the complexity of the derived relation and the number of assets involved in the relation paths.
A derived relation appears as a relation table or list on the asset page, with to indicate that the relation is derived. You can click
to see the derived relation type diagram.


- A maximum of 50 derived related assets are shown per derived relation type section.
- Filtering and search are not available.