Properties

A property is a field that describes assets of a given type. Each created property becomes available for all assets of that type.

Access

1. Go to Organization → Metamodel
2. Click on an asset type
3. Select the "Properties" tab

Property types

The current metamodel supports these property types. The names below match the labels used in the metamodel interface.

Type	Accessible name	Typical use
Text	Short text	Names, identifiers, versions
Long text	Longer text	Notes, functional descriptions
Rich text	Formatted text	Documentation, guides
Number	Numeric value	User count, capacity
Percentage	Percent value	Usage rate, availability
Currency	Monetary value	Budget, license cost
Date	Calendar date	Go-live date, end of support
Boolean	yes/no	Active, critical, compliant
List	single-choice list	Status, criticality, environment
List multiple	multi-choice list	Technologies, platforms
Score	Rating scale	Criticality, maturity

Create a property

1. Click "Create property"
2. Configure:
   • Name: Displayed label
   • Type: Choose from types above
   • Description: Optional explanation
   • type-specific options such as Default value, Possible choices, Minimum, or Maximum
3. Click "Create"

tip

The property is immediately available in forms for all assets of the type.

Modify a property

1. Click the edit icon of the property
2. Modify parameters
3. Click "Validate"

Data loss

Changing the property type can invalidate existing values and must be treated as a destructive change.

Delete a property

1. Click the edit icon of the property
2. Click the delete icon
3. Click "Confirm"

Irreversible

All values of this property are permanently deleted for all assets.

Built-in attributes vs custom properties

The metamodel distinguishes custom properties from built-in attributes.

Attribute	Description
Name	Built-in identifier
Icon	Built-in icon attribute

Best practices

• Choose the simplest type that fits the need
• Use List or List multiple when users should pick from a controlled list
• Keep names explicit
• Avoid overloading one asset type with too many fields
• Document properties with descriptions when the expected meaning is not obvious