Settings overview of a type element

Settings overview of a type element

For creating and updating a type element (standard, derived, middle), various settings can be configured. Below all the settings of the dialog Type element settings are explained.

General settings for a type element

Setting Explanation
Icon An icon that helps to optically identify a type element and distinguishes it from other type elements.

Note:

  • Make sure the combination of the icon and the color is not used for other type elements.
Name A singular noun that best represents the model object. Example: ‘Requirement’.
Plural A plural noun that corresponds with the name. Example: ‘Requirements’.
Short name A three-lettered abbreviation from which a user can recognize the type element. As a result, the short name is used as a prefix for the auto generated IDs.
Display as The default type property of the corresponding type element that is presented in a tree, collection relation, the recycle bin and the history view. It helps a user to quickly identify what type elements it concerns.

Notes:

  • Only type properties can be used for Display as that have the data type ‘Single line text’.
  • The setting Display as can only be updated for an existing type element.

 

Advanced settings for a type element

Setting Explanation
Configuration The Configuration determines the behavior of the type element in the workspace:

  • Standard: The standard type element is autonomous by nature. Users can create elements without the existence of other elements.
  • Derived element: The derived type element derives its existence from another type element.
  • Middle element: The middle type element derives its existence from another type element. Complementary, the type element must also have a relation to a third type element.
Origin relation A type relation that represents the relation between the origin element and the derived or middle element.

Note:

  • A prerequisite is that the Configuration must be set to Derived element or Middle element.
Act as inner element An inner type element is not experienced by users to be part of the core of the SE model. By nature, an inner type element supports another type element that is part of the SE model. For example, the type element ‘Requirement’, could have a derived type element ‘Note’ which acts as an inner element as a ‘Note’ is not experienced as a core type element of the SE model.

Note:

  • A prerequisite is that the Configuration must be set to Derived element or Middle element.
  • The type element will not be presented in the type list.
  • The type element will not have its own detail view.
  • The type element can only be seen on the overview and detail view of the type element that it is derived of or for which it is a middle element.
  • An inner element can only have outgoing type relations.
Hierarchical A hierarchical type element is part of a hierarchical structures with other type element or with the same type element.

Note:

  • A prerequisite is that the Configuration must be set to Derived element.
Cardinality The cardinality allows to constraint the number of allowed relations between two elements. By default, the cardinality is set to Multi allowing an unlimited amount of relations. When the cardinality is set to Single, a maximum of one relation is allowed between the two corresponding elements.

Note:

  • A prerequisite is that the Configuration must be set to Derived element or Middle element.
Target relation The Target relation specifies what type element is the subject of the middle element. For example, a type element ‘Room’ can have a middle element ‘Specification’ which has a target relation to the type element ‘Inventory’.

Note:

  • A prerequisite is that the Configuration must be set to Middle element.
Require origin-target relation The Require origin-target relation specifies if the middle element should be restricted to only exist when another type relation exists.

Note:

  • A prerequisite is that the Configuration must be set to Middle element.
Required origin-target relation The Required origin-target relation specifies which other type relation is mandatory for the middle element to be valid. Imagine a type element ‘Requirement’ that has a middle element ‘Verification’ with a complementing relation to another type element ‘System Object’. In this case, the middle element ‘Verification’ can be configured to have a restriction on another relation that exists directly between ‘Requirement’ and ‘System Object’. In this way, a verification is only allowed to exists when it resembles a relation between a requirement and a system object.

Note:

  • A prerequisite is that the Require origin-target relation must be enabled.
Enforce uniqueness on origin-target combination The Enforce uniqueness on origin-target combination determines if only a single middle element is allowed to exist between a origin element and a target element.

Note:

  • The prerequisite is that the Configuration must be set to Middle element.
Enable positioning Enable positioning allows a user to rearrange the position of an element relative to another element. It can be used to position standard elements in a table or to position derived elements in a tree.

Note:

  • If positioning is enabled new elements can only be created in the ghost row.
Life cycle property The life cycle property determines how the type element should be evaluated according to its life cycle.

Note:

Use auto archive The Use auto archive property can be used to only show elements for the corresponding type element throughout the workspace that have a certain value. For example, you can use auto archive to hide all ‘Requirements’ that have the value ‘Expired’ for the type property ‘Status’. In this case the life cycle property should be configured pointing to the ‘Status’ property.

Note:

  • The prerequisite is that the Life cycle property must be configured for the type element.
Data ownership in The data ownership in determines whether the elements are owned by Relatics users or that ownership lies in another application. The owner can create and delete elements of this type element:

  • Relatics: A type element of which the corresponding workspace is the owner. Elements of the type element can only be created in the corresponding workspace.
  • External application: A type element of which an external application is the owner. Elements of the type element can only be created in the external application.

Permissions settings for a type element

Setting Explanation
[Role name] The role determines if a user with the corresponding role is allowed to edit or create the corresponding type element.
Back
Schakel JavaScript in je browser in om dit formulier in te vullen.

Download the whitepaper

Schakel JavaScript in je browser in om dit formulier in te vullen.

Download the whitepaper

Request a demo

Fill in the below information and we will contact you to schedule a demo.

Schakel JavaScript in je browser in om dit formulier in te vullen.
We will use this information to contact you.
Schakel JavaScript in je browser in om dit formulier in te vullen.
Schakel JavaScript in je browser in om dit formulier in te vullen.
Addresss

Neem contact op

Vul ons formulier in en een van de Relatics medewerkers neemt zo snel mogelijk contact met u op. Liever telefonisch contact? Bel ons op +31 (0) 180 413 047.
Schakel JavaScript in je browser in om dit formulier in te vullen.