Asset Properties


What is a Property?

A Property is a structured data field that you define to describe all Assets of a given Type. Each Property you create is automatically available in the creation and editing forms for every Asset of that Type.

Properties act as a standardisation system for your data: they ensure that all Assets of the same Type share the same informational structure, making it easier to search, filter, compare, and generate consistent reports.

Automatic inheritance: any Property added to an Asset Type is immediately available for all existing Assets of that Type, as well as for any new ones. This automatic propagation ensures consistency in your Inventory without requiring manual intervention.


PropertyTypes

1. Text Properties

1.1. Short Text

The Short Text Property Type is designed to capture concise textual information, such as names, identifiers, or brief descriptions.

Configurable constraints

  • Maximum length (optional): an upper limit to prevent oversized entries
  • Default value (optional): text automatically proposed when a new Asset is created

Recommended use cases
application names, technical references, software versions, business identifiers


1.2. Long Text

The Long Text Property Type provides an extended input area for detailed descriptions or substantial comments.

Advanced configuration

  • Maximum length (optional): an upper limit to avoid excessively long entries
  • Default value (optional): pre-filled templates or instructional text

Recommended use cases
detailed functional descriptions, documentation notes, technical specifications, audit comments


1.3. Rich Text

The Rich Text Property Type allows for the creation of formatted content with advanced styling, links, and visual structuring.

Features and constraints

  • Formatting: bold, italic, underline, bullet points
  • Structure: headings, paragraphs, separators
  • Links: hyperlinks to external resources
  • Default value (optional): predefined rich content

Recommended use cases
user documentation, procedure guides


2. Numeric properties

2.1. Number

The Number Property Type captures quantitative values with precise control over allowed ranges.

Constraint configuration

  • Minimum value (optional): lower bound for valid entries
  • Maximum value (optional): upper bound for valid entries
  • Default value (optional): number automatically proposed

Example use cases
number of users, storage capacity


2.2. Percentage

The Percentage Property Type is specialised for values expressed as percentages.

Available constraints

  • Minimum value (optional): custom lower limit (can be below 0%)
  • Maximum value (optional): custom upper limit (can exceed 100%)
  • Standardised display: % symbol automatically added
  • Default value (optional): configurable reference percentage

Common applications
usage rates, availability percentages, satisfaction levels, progress indicators


2.3. Currency

The Currency Property Type is designed for managing monetary amounts with multi-currency support.

Currency configuration

  • Currency code: selection from over 170 international currencies (EUR, USD, GBP, JPY, etc.)
  • Minimum value (optional): lower limit based on budget constraints
  • Maximum value (optional): upper limit to control spending
  • Formatted display: currency symbol automatically shown based on selected currency
  • Default value (optional): predefined reference amount

Business use cases
licence costs, project budgets, investments, operational expenses, purchase prices


3. Discrete properties

3.1. Single Select List

The Single Select List Property Type allows you to define a closed set of options, of which only one can be selected.

Option management

  • Value creation: at least one option must be defined
  • Custom colours (optional): assign distinctive colours to each option
  • Default value (optional): automatically preselected option

Practical applications
statuses (Active / Inactive / Maintenance), environments (Production / Test / Development)


3.2. Multi Select List

The Multi Select List Property Type allows multiple options to be selected simultaneously from a predefined list.

Constraint configuration

  • Options: at least one option must be defined
  • Custom colours (optional): assign distinctive colours to each option
  • Default values (optional): set of preselected options

Use cases
technologies used, deployment platforms, hosting types, multiple functional categories


To change the label of an existing option, simply edit the option's text directly. Do not delete the option to create a new one.
This approach preserves all values already entered on your Assets, unlike deletion, which permanently erases all data associated with that option.


4. Specific Properties

4.1. Date

The Date Property Type is used to manage time-related information with validation and range constraints.

Date configuration

  • Default value (optional): pre-filled date

Time-based applications
go-live dates, maintenance deadlines, end-of-support dates, project milestones


4.2. Boolean

The Boolean Property Type is a binary field used to capture true/false or yes/no states.

Simple configuration

  • Default value (optional): proposed initial state

Typical uses
active/inactive status, regulatory compliance, technical validation, process approval


4.3. Score

The Score Property Type is a numerical rating system used to standardise evaluations across Assets.

Scale settings

  • Mandatory scale: maximum score between 3 and 10 points
  • Default value (optional): predefined score within the allowed range

Evaluation use cases
business criticality (1–5), technical quality (1–10), user satisfaction (1–5), process maturity (1–4), risk level (1–3)


Manage properties

Only organisation administrators have the necessary privileges to manage an Asset’s Properties.

Create a New Property

To add a new Property to an Asset Type:

  1. Access the Asset Type
    Go to Organisation → Metamodel, then click the ‘pen’ icon next to the relevant Asset Type.
  2. Click "Add Property"
  3. Configure the Property
    • Name: enter a clear, descriptive name
    • Type: select the appropriate data type from the list
    • Description (optional): provide guidance for users
    • Type-specific fields: complete any additional fields based on the selected Property Type
  4. Click "Create" to add the Property



Creating a new Property is completely safe — it does not delete any existing data and does not affect your views, diagrams, or other existing components in Boldo.

Immediate propagation: the new Property becomes instantly available in the forms of all Assets of that Type.


Edit an Existing Property

To modify an already configured Property:

  1. Access the Property
    In the Properties tab of the Asset Type, click the ‘pen’ icon next to the Property you want to edit.
  2. Adjust the settings
    Make the necessary changes to the configuration.
  3. Save
    Click "Confirm" to apply the changes.

If you change the type of a Property (for example, from Text to Number), all previously entered values for that Property across all Assets will be permanently deleted. This action is irreversible.

Changes to the name, description, constraints, or options are immediately reflected across all forms and interfaces, but existing data is preserved as long as it remains compatible.


Delete a Property

To permanently remove a Property:

  1. Access the Property
    In the Properties tab of the Asset Type, click the ‘pen’ icon next to the Property you want to edit.
  2. Click the ‘bin’ icon
    This initiates the deletion process.
  3. Confirm the deletion
    Acknowledge and confirm the consequences before proceeding.

Irreversible consequences:

Data deletion: all values of this Property across all Assets will be permanently erased

Impact on Boldo components: any views, diagrams, charts, or nested maps using the deleted Property will be affected


Best Practices

Consistent naming

  • Use clear, explicit terms aligned with your organisation’s business vocabulary
  • Apply a uniform naming convention across all Properties
  • Avoid ambiguous acronyms or abbreviations
  • Prioritise clarity over brevity


Choosing the optimal type

  • Plan ahead: carefully analyse the data to be captured before selecting a Property Type
  • Scalability: favour types that can adapt to evolving needs
  • Consistency: use the same types for similar data across different Asset Types