Get In Touch
See what's new in Relatics in our webinar on January 28th 14:00 (UTC +1)

Summary of type element settings

Summary of type element settings

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-letter 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 constrains 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.
Existence of middle element The Existence of middle element is part of the quality assurance.

Select a value:

  • Not required: No relation between the origin and the target element is required.
  • Required for each relation of: When this value is applied to a middle element, a quality reminder is given if there is an origin element with a relation to a target element without a middle element.

Note:

  • A prerequisite is that the Configuration must be set to Middle element.
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 elements of the type element should be evaluated according to their life cycle. Depending on the life cycle, an element is evaluated in quality assurance, included in the My to-do’s, or is given an archived status.

Note:

  • Only one type property, of data type List, can be selected as the life cycle property for a type element.
To-do definitions The To-do definitions reduce the view to show the elements that comply with a defined to-do for the current user.

Note:

  • The prerequisite is that the Life cycle property must be configured for the type element.
  • The prerequisite is that a linked user element is configured.
  • The prerequisite is that a relation To the linked user element exist.
Auto archive The Auto archive property can be used to hide elements that are at the end of their life cycle and have served their purpose.

Note:

  • The prerequisite is that the Life cycle property must be configured for the type element.
Ownership in 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.
Note The Note field can be used to leave text that is visible to all users in the workspace. This setting can be used to convey additional information.

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

ISO 27001 badge

Contact

Ridderpoort 32
2984 BG Ridderkerk
The Netherlands

+31 180 413 047
info@relatics.com

Linkedin Youtube

Relatics updates

Subscribe to stay informed about feature releases, major service status updates and interesting content.

Request a demo

Fill in our form and one of our colleagues will contact you as soon as possible to schedule a demo.

Please enable JavaScript in your browser to complete this form.
Please enable JavaScript in your browser to complete this form.

Download the whitepaper

Please enable JavaScript in your browser to complete this form.
Addresss

Get in touch

Fill in our form and one of the Relatics members will contact you as soon as possible. Do you prefer contact by phone? Please call us at +31 180 413 047.
Please enable JavaScript in your browser to complete this form.