Fact Sheet Relations

Configure relations between fact sheets.

You can configure relations between fact sheets as well as fields on relations.

Creating a Relation

In addition to creating regular subsections, you can create new relations by clicking the + Add relation button. You are then able to configure the relation based on the following attributes:

  • Target fact sheet type: Dropdown with all available fact sheet types on your workspace.
  • Multiplicity: Allows you to define the cardinality of the relation, e.g., “Many to Many” or “Many to One”.
  • The section in target fact sheet type: Allows you to define which section of the target fact sheet type the relation should be visible.

When creating an additional relation to an already related fact sheet type, one more attribute is required:

  • Descriptor: This allows you to provide a unique identifier to differentiate between the already existing relation and the new relation.

Deleting a Relation

When a relation becomes obsolete, you can delete this permanently from your workspace by clicking the “Delete” button on the relation configuration view. Currently, relations can not be deleted under the following circumstances:

  • The relation is part of the Naming Rule of a fact sheet type
  • The relation has all fact sheet types as target fact sheet types e.g., Parent/Child relation
  • The relation is a constraining relation or is constrained by another relation
  • The relation has the same target fact sheet type as the source fact sheet type

This is because the above relations currently can not be reconfigured. Further updates to the functionality aim to cover those exceptions.

646

🚧

Deleting relations

Deleting a relation will remove the relation and all attached data from both sides of the relations. This is non reversible.

Please acknowledge that deleting fields or field values from your workspace will temporarily put your workspace in a read-only mode. No Fact Sheets can be modified while these changes are processed. Usually, the workspace should be in read-only mode not longer than 15 minutes.

Self-Referencing Relations

Self-referencing relations enable you to create relations between fact sheets of the same type. These relations work like regular relations between fact sheets, with the exception that both ends of the relation target the same fact sheet type.

When you create a self-referencing relation, two subsections are generated on a fact sheet to represent both ends of the relation. Like with regular relations, you can create fields on self-referencing relations.

With self-referencing relations, you can create relations between subtypes of the same fact sheet type, for example, between business applications and deployments, which are subtypes of the application fact sheet. After you’ve created a self-referencing relation, make the relation conditional by using conditional attributes. This allows you to ensure that only the relevant relation appears on a specific fact sheet subtype. For more information, see Creating a Conditional Relation Between Subtypes of the Same Fact Sheet Type.

To create a self-referencing relation, follow these steps:

  1. In the Meta Model Configuration section of the administration area, select a fact sheet type. If needed, select a subtype to create a relation for.

  2. On the fact sheet configuration page, select a section, then click Add relation.

  3. In the sidebar, in the Target Fact Sheet type list, select the same fact sheet as the target for the relation. As an example, we’re creating a self-referencing relation for application fact sheets.

  4. Identify the relation from both directions by entering descriptors in the Descriptor to and Descriptor from fields. These descriptors form part of the unique identifiers (keys) for the relation. Descriptive names help users differentiate between the two sides of the relation when working with fact sheets through the API.
    For example, if Using and UsedBy are the descriptors, the keys representing both sides of the relation appear as follows:

    • relUsedByApplicationToUsingApplication
    • relUsingApplicationToUsedByApplication
  5. Select the multiplicity for the relation, decide whether you want to make the relation visible, then save the changes.

    Creating a Self-Referencing Relation for the Application Fact Sheet

    Creating a Self-Referencing Relation for the Application Fact Sheet

A self-referencing relation generates two new subsections on a fact sheet, representing both ends of the relation. Each end of the relation has a unique identifier (key).

The translations for both ends of the relation are prefixed with the descriptors you provide. You can move subsections within a fact sheet and edit translations independently.

Subsections on a Fact Sheet Representing a Self-Referencing Relation

Subsections on a Fact Sheet Representing a Self-Referencing Relation

Creating Conditional Relations Between Fact Sheet Subtypes

You can create a relation between specific fact sheet subtypes by using conditional relations. To learn more about conditional attributes, see Conditional Attributes.

You can create a conditional relation between:

  • Subtypes of different fact sheet types
  • Subtypes of the same fact sheet type

Creating a Conditional Relation Between Subtypes of Different Fact Sheet Types

Because relations between base fact sheet types are available in the meta model by default, you don’t need to create them. You only need to make the relation conditional on both ends for specific subtypes.

Follow these steps:

  1. Create a conditional relation on the source fact sheet.

    1. In the meta model configuration, select a fact sheet, then navigate to the Conditional Attributes tab.

    2. Click Add New Condition.

    3. In the When filling out this field list, select Subtype.

    4. In the If the value selected is list, select a fact sheet subtype.

    5. In the Then display these attributes list, select a fact sheet type to link to. You will select a specific subtype when creating a conditional relation on the second fact sheet.

    6. Save the condition by clicking the checkmark icon.

      The following image shows a conditional attribute for the team subtype on the organization fact sheet and the business context fact sheet.

      Conditional Attribute for the Team Fact Sheet Subtype and the Business Context Fact Sheet

      Conditional Attribute for the Team Fact Sheet Subtype and the Business Context Fact Sheet

  2. Create a conditional relation on the target fact sheet.

    1. In the meta model configuration, select a fact sheet, then navigate to the Conditional Attributes tab.

    2. Click Add New Condition.

    3. In the When filling out this field list, select Subtype.

    4. In the If the value selected is list, select a fact sheet subtype.

    5. In the Then display these attributes list, select a fact sheet type for which you’ve created a conditional relation in the previous step.

    6. Save the condition by clicking the checkmark icon.

      The following image shows a conditional attribute for the business product subtype on the business context fact sheet and the organization fact sheet.

      Conditional Attribute for the Business Product Fact Sheet Subtype and the Organization Fact Sheet

      Conditional Attribute for the Business Product Fact Sheet Subtype and the Organization Fact Sheet

A conditional relation is created. When you create a new fact sheet of a specific subtype, you can link it to the corresponding fact sheet subtypes. In the example, we created a relation between the following subtypes:

  • Team subtype on the organization fact sheet
  • Business product subtype on the business context fact sheet

Creating a Conditional Relation Between Subtypes of the Same Fact Sheet Type

You can create a conditional relation between subtypes of the same fact sheet type, for example, between business applications and deployments, which are subtypes of the application fact sheet. A relation between subtypes of the same fact sheet type is known as a self-referencing relation.

To learn how to create fact sheet subtypes, see Fact Sheet Subtype Management.

To view fact sheet subtypes recommended for the meta model v4, see Add Fact Sheet Subtypes to Several Fact Sheet Types.

Follow these steps:

  1. Create a self-referencing relation between fact sheet subtypes. For details, see Self-Referencing Relations. Use meaningful names for descriptors to reflect the subtype names. For example, if BusinessApp and Deployment are the descriptors, the keys representing both sides of the relation appear as follows:

    • relBusinessAppApplicationToDeploymentApplication
    • relDeploymentApplicationToBusinessAppApplication
  2. Make the self-referencing relation conditional on one end:

    1. On the fact sheet configuration page, navigate to the Conditional Attributes tab.
    2. Click Add New Condition.
    3. In the When filling out this field list, select Subtype.
    4. In the If the value selected is list, select a fact sheet subtype, for example, business application.
    5. In the Then display these attributes list, under Relations, select a fact sheet subtype for which you’ve created a self-referencing relation, for example, deployment.
    6. Save the condition by clicking the checkmark button.
  3. Make the self-referencing relation conditional on another end:

    1. Still on the Conditional Attributes tab, click Add New Condition.

    2. In the When filling out this field list, select Subtype.

    3. In the If the value selected is list, select a fact sheet subtype that represents another end of the relation, for example, deployment.

    4. In the Then display these attributes list, under Relations, select the corresponding subtype, for example, business application.

    5. Save the condition by clicking the checkmark button.

      The following image illustrates two conditions for a self-referencing relation.

      Self-Referencing Relation Between Two Subtypes of the Same Fact Sheet Type

      Self-Referencing Relation Between Two Subtypes of the Same Fact Sheet Type

Once you’ve created a conditional relation between two fact sheet subtypes, you can follow the same steps to create relations between other subtypes.