Property specification

TypeScript type: PropertySpecification.

This specification allows overriding some attributes of specific ECProperty or define how it's displayed.

Attributes

Attribute: name

Name of the ECProperty to apply overrides to. A "*" may be specified to match all properties in current context. The current context is determined based on where the override is specified:

• When used in a content modifier, the properties of the ECClass specified by the class attribute are used.
• When used in one of the content specifications, properties produced by that specification are used.

Attribute: overridesPriority

There may be multiple property specifications that apply to a single property and there may be conflicts between different attributes. The overridesPriority attribute is here to help solve the problem - if multiple specifications attempt to override the same attribute, the override of specification with highest overridesPriority value is used. The order of overrides from specification with the same overridesPriority is defined by the order they appear in the overrides list.

// There's a content rule for returning content of given `bis.Subject` instance. In addition, the `UserLabel`
// property has a couple of property overrides which set renderer, editor and label. The label is
// overriden by both specifications and the one with higher `overridesPriority` takes precedence.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        overridesPriority: 1,
        labelOverride: "A",
        renderer: {
          rendererName: "my-renderer",
        },
      }, {
        name: "UserLabel",
        overridesPriority: 2,
        labelOverride: "B",
        editor: {
          editorName: "my-editor",
        },
      }],
    }],
  }],
};

Attribute: labelOverride

This is an attribute that allows overriding the property label. May be localized.

// There's a content rule for returning content of given `bis.Subject` instance. In addition, the `UserLabel`
// property has a label override that relabels it to "Custom Label".
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        labelOverride: "Custom Label",
      }],
    }],
  }],
};

Attribute: categoryId

The attribute allows moving the property into a different category. There are several options:

• Reference a category by ID used in PropertyCategorySpecification in the current context. The current context contains categories specified in the same content specification or the same content modifier, depending on where the property override is used.

• Move to DefaultParent category. This is useful when using with related properties, to avoid putting them inside a special related class category and instead show them next to properties of the source class.

• Move to Root category. This is useful when using with related properties, to avoid putting them inside a special related class category and instead show them in the root category.

See property categorization page for more details.

// There's a content rule for returning content of given `bis.Subject` instance. In addition, the `UserLabel`
// property is placed into a custom category by assigning it a `categoryId`.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyCategories: [{
        id: "custom-category",
        label: "Custom Category",
      }],
      propertyOverrides: [{
        name: "UserLabel",
        categoryId: "custom-category",
      }],
    }],
  }],
};

Attribute: isDisplayed

This attribute controls whether the particular property is present in the result, even when it is marked as hidden in the ECSchema. The allowed settings are:

• Omitted or undefined: property visibility is controlled by the ECSchema.
• true: property is made visible. Warning: this will automatically hide all other properties of the same class. If this behavior is not desirable, set doNotHideOtherPropertiesOnDisplayOverride attribute to true.
• false: property is made hidden.
• The value can be set using an ECExpression. Warning: this will automatically hide all other properties of the same class, no matter what the expression evaluates to. If this behavior is not desirable, set doNotHideOtherPropertiesOnDisplayOverride attribute to true.

// There's a content rule for returning content of given `bis.Subject` instance. In addition,
// the `LastMod` property, which is hidden using a custom attribute in ECSchema, is force-displayed
// using a property override.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "LastMod",
        isDisplayed: true,
      }],
    }],
  }],
};

Attribute: doNotHideOtherPropertiesOnDisplayOverride

This attribute controls whether making the property visible using isDisplayed should automatically hide all other properties of the same class. When true, this behavior is disabled.

// There's a content rule for returning content of given `bis.Subject` instance. In addition,
// the `UserLabel` property is set to be displayed with `doNotHideOtherPropertiesOnDisplayOverride` flag,
// which ensures other properties are also kept displayed.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        isDisplayed: true,
        doNotHideOtherPropertiesOnDisplayOverride: true,
      }],
    }],
  }],
};

doNotHideOtherPropertiesOnDisplayOverride: false	doNotHideOtherPropertiesOnDisplayOverride: true

Attribute: renderer

Custom property renderer specification that allows assigning a custom value renderer to be used in UI. The specification is used to set up Field.renderer for this property and it's up to the UI component to make sure appropriate renderer is used to render the property.

See Custom property value renderers page for a list of available renderers or how to register a custom one.

// There's a content rule for returning content of given `bis.Subject` instance. In addition,
// it assigns the `CodeValue` property a custom "my-renderer" renderer.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "CodeValue",
        renderer: {
          rendererName: "my-renderer",
        },
      }],
    }],
  }],
};

// Ensure the `CodeValue` field is assigned the "my-renderer" renderer
const content = (await Presentation.presentation.getContent({
  imodel,
  rulesetOrId: ruleset,
  keys: new KeySet([{ className: "BisCore:Subject", id: "0x1" }]),
  descriptor: {},
}))!;
expect(content.descriptor.fields).to.containSubset([{
  label: "Code",
  renderer: {
    name: "my-renderer",
  },
}]);

Attribute: editor

Custom property editor specification that allows assigning a custom value editor to be used in UI.

// There's a content rule for returning content of given `bis.Subject` instance. In addition,
// it assigns the `UserLabel` property a custom "my-editor" editor.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        editor: {
          editorName: "my-editor",
        },
      }],
    }],
  }],
};

// Ensure the `UserLabel` field is assigned the "my-editor" editor
const content = (await Presentation.presentation.getContent({
  imodel,
  rulesetOrId: ruleset,
  keys: new KeySet([{ className: "BisCore:Subject", id: "0x1" }]),
  descriptor: {},
}))!;
expect(content.descriptor.fields).to.containSubset([{
  label: "User Label",
  editor: {
    name: "my-editor",
  },
}]);

Attribute isReadOnly

This attribute controls whether the property field is read-only. If the attribute value is not set, the field is read-only when at least one of the properties is read-only.

// There's a content rule for returning content of given `bis.Subject` instance. In addition, the `UserLabel`
// property is made read-only.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        isReadOnly: true,
      }],
    }],
  }],
};

// Ensure the `UserLabel` field is read-only.
const content = (await Presentation.presentation.getContent({
  imodel,
  rulesetOrId: ruleset,
  keys: new KeySet([{ className: "BisCore:Subject", id: "0x1" }]),
  descriptor: {},
}))!;
expect(content.descriptor.fields).to.containSubset([{
  label: "User Label",
  isReadonly: true,
}]);

Attribute priority

This attribute controls the order in which property fields should be displayed. Property fields with higher priority will appear before property fields with lower priority. If the attribute value is not set, the field's priority will be the maximum priority of its properties.

// There's a content rule for returning content of given `bis.Subject` instance. In addition, the `UserLabel`
// property's priority is set to 9999.
const ruleset: Ruleset = {
  id: "example",
  rules: [{
    ruleType: "Content",
    specifications: [{
      specType: "SelectedNodeInstances",
      propertyOverrides: [{
        name: "UserLabel",
        priority: 9999,
      }],
    }],
  }],
};

priority: 0	priority: 9999

Last Updated: 30 November, 2023