Create and manage relationships

A relationship connects two assets using a type defined in the metamodel. Its direction and properties describe the connection; they are distinct from each asset's own properties.

For example, an application can support a business capability. Viewed from the capability, the same connection appears in the opposite direction. This does not create a second relationship.

Link two assets from an asset form

1. Open the source asset and select Edit.
2. Open the Relationships tab.
3. Find the intended relationship group. Check its label, the linked asset type and the direction shown.
4. Select Add asset in that group.
5. Search for and select the asset to link.
6. If the relationship offers properties, open Variables (tooltip Edit properties) on that occurrence, enter the appropriate values, then select Apply to return to the asset form.
7. Review the Relationships tab, then select Validate on the asset form.
8. Check the result in the asset's Related assets tab.

The groups offered depend on the metamodel. You cannot use this form to invent an arbitrary relationship type. Ask an administrator to configure a relationship type if the connection you need is missing.

Apply in the embedded relationship-properties dialog prepares a change in the parent form. It does not write it to the knowledge base. Cancelling the parent asset form discards that pending change too.

The same relationship can be managed from its other endpoint when permissions allow it. Always read the direction: the asset whose form is open is not necessarily the relationship's source.

Understand properties and parallel relationships

A relationship can have properties such as allocation percentage, responsibility or validity dates. Their names and available values follow the relationship type configured by your organization.

When that type supports properties, it can also support several distinct relationships between the same two assets. For example, two allocations may refer to different periods or activities. Each occurrence has its own properties and identifier.

1. In the asset form's Relationships tab, locate the existing connection.
2. Select Add another relationship to this asset on that occurrence.
3. Enter properties that distinguish the new occurrence from the existing one.
4. Select Apply in its properties dialog.
5. Review both occurrences and select Validate on the asset form.

Two active relationships of the same type between the same endpoints must differ in at least one entered property. A calculated value does not distinguish them. Leaving values empty or changing the order of a multiple-choice selection does not make a separate relationship.

If Boldo reports identical relationships, compare their entered values before retrying. A unique-key property also has its own uniqueness constraint. Do not repeatedly add the same target hoping to bypass those rules.

Change or remove one occurrence

To change properties from the asset form, open Variables (tooltip Edit properties) on the correct occurrence, update its values, select Apply, then Validate the asset form.

To remove a link, use its Delete control in the Relationships tab, check the remaining occurrences, then validate the asset form. This archives the relationship; it does not delete either endpoint asset. With parallel relationships, select the intended occurrence rather than relying on the target name alone.

When you open a standalone relationship-editing dialog outside an asset form, Validate submits its changes directly. There is no parent asset form to validate afterward. If Suggest is offered, the values are submitted as suggestions for review; see suggestions.

Use the relationship inventory

1. Open an asset-type inventory.
2. Open the selector currently showing the asset type's name.
3. Choose a relationship type. Show empty relationships is enabled by default, so types without current occurrences are also listed.
4. Inspect the resulting relationship rows. Select a relationship's name, in Name, for its full page, or Preview at the end of the row for a panel; Actions → Open also leads to the page of an active row. The assets in Source and Target open their own preview.

The selector offers standard relationship types even when their properties are disabled. Process-flow connections are managed through the process editor.

A relationship page contains Information and, depending on the plan, Comments, Rights and Activity log. Edit changes that occurrence's properties; it does not move its source or target to another asset.

The Activity log groups changes saved together when sorted by date. Expand a row to compare its values, as in the asset activity log.

For several property changes, use the inventory's cell-editing workflow. From an Editor account, use Select multiple relations to select editable relationships, then Update to set a shared property value. A disabled checkbox means the relationship itself is not editable.

The update dialog distinguishes directly editable property values, readable values that require a suggestion, and values left unchanged. Suggestion sends eligible changes for review instead of applying them directly. Check the counts, then choose Update or Send suggestions, as offered. Suggestions are attached to each relationship's actual source asset.

The selection also offers lifecycle actions according to context. Boldo processes large selections in batches; wait for the final report and inspect modified, skipped and failed counts. A partial result does not mean that every selected relationship changed.

Restore or permanently remove a relationship

Actions → Delete on an active relationship row, followed by Confirm, archives that occurrence and preserves its endpoints.

To restore it:

1. Enable View archives in the relationship inventory.
2. Find the intended occurrence and open Actions → Restore.
3. Select Restore in the confirmation.
4. Check its properties and endpoints in the active list.

This archive list contains relationships archived directly, with both endpoint assets still active. Links deactivated by an asset's archiving are handled through asset restoration, rather than this list.

Restoration can fail if a relationship, identical occurrence or unique-key value now conflicts with the archived one. Resolve the conflict before retrying; restoration reactivates the existing instance rather than creating a new identifier.

In real data, Delete permanently is available on eligible archived rows. Read the confirmation, check the irreversible-action acknowledgment and confirm with Delete permanently. This removes the relationship and its associated history and comments, and cleans up dependent references. It does not delete its endpoint assets and cannot be undone with Restore.

Check permissions and context

Directly applying changes, archiving, restoring or permanently deleting a relationship requires an Editor account type or higher, in addition to the necessary permissions. You must be able to read both endpoints and the relationship type. Changing the connection requires the appropriate relationship permission for the actual source asset's domains. Relationship properties have their own read and write permissions.

The relationship's Rights tab shows the domains used for access and groups members by roles and effective permission. Filter by access level, search a property or filter property levels to locate the restriction. The report does not change rights or reveal properties hidden by the metamodel.

This explains why you may see a link without being able to modify it, or see different controls when working with another source. Being an asset owner does not by itself grant these permissions.

The current real data or scenario context also matters. A change in a scenario affects that scenario until its changes are applied through the scenario workflow.

A freely drawn arrow in a diagram is not automatically a relationship in the knowledge base. Likewise, transitions in a process flow follow the process editor's rules.