Configure properties
Properties define the information collected for an asset type. Administrators and the Owner configure them; contributors' rights to enter values are managed separately. For values derived from other data, use a calculated property.
Add a property
- Open Organization settings > Metamodel > Assets and select the asset type.
- Under Properties, click Add a property.
- Enter Name, check Key, and add a description if useful.
- Choose the property type and configure its options.
- Set Optional according to whether this information should contribute to completeness.
- Click Create.
- Open an asset of this type to inspect the field, then create a new asset to check any default value.
To reuse a property from this type or another type, choose it in Start from an existing property at the top of the dialog. Boldo fills the form with its settings, which you can still change before creating. Properties shared by several types are listed first, under Common properties. This creates an independent definition: later changes do not synchronize the two properties or copy their recorded values.
Click the property's row or its pencil to edit it, then Validate. Arrange its position and category using property organization. Configure information belonging to a connection as a relationship property, rather than duplicating it on each asset.
Choose text and choices
| Type in the interface | Use and available options |
|---|---|
| Text | Short text; maximum length and default value |
| Long text | Multiline text; maximum length and multiline default |
| Rich text | Formatted content; default value in the editor |
| List | One choice; labels, keys, descriptions, colors, order and default |
| List multiple | Several choices; the same choice settings and multiple defaults |
| Unique key | A reference whose nonempty value must be unique among active assets of this type |
For a list, define at least one choice. Give each choice a distinct label and key. Use colors and order to make the list readable, and select only defaults that belong to its choices.
Add a description of up to 300 characters to explain when contributors should use each choice. It appears when choosing a value and in its tooltip. These descriptions also apply to relationship properties.
Changing a label is different from removing a choice. Removing a used choice clears the corresponding stored selections. Before saving a removal, check the listed choices and scenario impact, then confirm Remove and save. Removing choices affects real data and scenarios.
Renaming a choice key updates affected stored references and recognized formula references; review integrations that use that key outside Boldo. A formula comparing a choice key can prevent its removal until you adapt the formula. Merely displaying or counting a list does not block every choice change. Boldo still checks that calculated results remain compatible with their allowed choices.
Choose numbers and dates
| Type in the interface | Use and available options |
|---|---|
| Number | A quantity; minimum, maximum and default |
| Percentage | A percentage; minimum, maximum and default |
| Currency | A monetary amount; minimum, maximum, default and currency Code |
| Score | A rating; maximum chosen from 3 to 10 stars and default |
| Date | A date, with an optional default selected in the calendar |
| Boolean | Yes/no information; true, false or empty default |
For example, choose Currency for an annual cost and Percentage for an allocation. A currency code describes the amount; changing it is not a foreign-exchange conversion. Choose Boolean only when the answer genuinely has two states; use a list for several named stages.
Only configure the options available for the selected type. Date bounds and minimum text length are not offered as controls in this form.
Defaults, completeness and uniqueness
A default value prefills creation. Changing it does not replace values on existing assets or fill every empty historical field. Check a newly opened creation form after changing the default.
Optional means the property is excluded from the completeness score. Turning it off makes an empty value count as missing; it does not prevent every incomplete asset from being saved. Calculated and metamodel-hidden properties are also excluded from completeness.
Unique key checks active assets of the same type in the same context: the real repository or a particular scenario. It is not a global identifier across every type and scenario. Archived assets do not reserve their values against new active assets. Resolve any conflict before restoring an archived asset that would duplicate a current value.
Change or remove a property
Review existing values before tightening a constraint or removing a choice. A minimum or maximum incompatible with stored values can prevent the change, including values in archives and scenarios. Correct the affected values or choose a compatible bound; Boldo does not automatically trim every value to fit. Check representative assets and imports before retrying.
To change the property's type, follow property conversion. That procedure previews existing values and potential losses. If a calculated property depends on this property, changing its type or deleting it can be blocked until the formula is updated.
Deleting a property removes its values from current and archived assets and the affected historical fields. Read the scenario-impact warning. This is not a way to hide a field temporarily.
Open the property's editing form, click the trash button, read the confirmation and click Confirm. Afterwards, inspect the affected assets, calculations and visualizations, and update external import templates or integrations.
For an intermediate calculation that should not appear in ordinary forms, use the calculated property's visibility option. Visibility settings do not replace permissions for confidential data.