Property members
To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through user group policies.
The Sitecore Content Hub data model (the schema) is made up of entity definitions (for example, M.Asset, M.PCM.Product, M.Project.Task, and so on). Each entity definition is made up of members that contain various properties and relations. When you create a property member, you are adding information about the entity in the form of a new property of a certain data type (String, Boolean, Integer, and so on).
Before filling in the property member fields, you must select one of the following data types from the list:
|
Data type |
Description |
|---|---|
|
String |
Alphanumeric value. For example, a set of letters and symbols. |
|
Boolean |
True or False. |
|
Integer |
Number with no fractional part. |
|
Long |
Number with a larger range than an integer. |
|
Decimal |
Number including one or more decimal places. |
|
Datetime |
Time stamp including both date and time. |
|
Datetime offset |
Datetime value combined with an offset indicating the difference between the datetime and coordinated universal time (UTC). |
|
Option list |
Array of string values for users to choose from. |
|
JSON |
Object defined by JavaScript Object Notation. |
After you select a data type, you must fill in various other fields related to that type. These fields are organized on the following tabs.
General information
A property member contains the following general fields. Unless otherwise stated, all of these fields are optional.
|
Field |
Description |
|---|---|
|
Name |
Name of the member. This is a mandatory field. |
|
Type |
Read-only field representing the data type. |
|
Label |
User interface label of the member. |
|
Help text |
Visual hint that displays under the field in edit mode. |
|
Multilanguage |
Allows content translation for different cultures. |
|
Unique |
Validates the property value entered for this member to prevent duplicates. A unique property is unique across all definitions defined for this member. Important Values longer than 512 characters are not validated. |
|
Include in content |
Allows full-text search of this data value on the content page. |
|
Include in autocomplete |
Enables the data value in the suggestion API. |
|
Allow updates |
Turn this switch off to prevent the value of this member being updated after it is first entered, such as for the creation time of an entity. |
|
Boost |
If a search keyword matches multiple entity members, any that have this switch turned on rank higher in the search results than those that have it turned off. |
|
Secured |
Allows member security on the property. |
|
Content type |
For String members only, this field determines the type of text the member will hold, which affects the way it is displayed:
|
|
Regex validation |
Provide a regular expression to validate input for this member. Regex validation is case-sensitive. Note Regex validation for components rendered in React is case-sensitive whereas for components rendered in Knockout, validation in the API and scripting framework backend is case-insensitive. The application will transition to case‑sensitive validation as the standard. For additional information, see Migrating to React. |
|
Multi-value |
For option lists, allows users to select more than one option. |
You cannot edit the Multilanguage or Multi-value properties after they are created. If you want to modify these fields for an existing member, you must create a new member and use it instead of the old one.
If you use the same property member name with different data types, the error message Property is already used in the system with another data-type displays and you cannot proceed. This happens even if the property members were deleted earlier. To resolve this, delete the property. Go to support.sitecore.com and log in to the Sitecore Support and Self-Service Portal. Then, click Create Service Requests and request that the Ops team run the harmonization command.
Conditional
A member that has one or more conditions will only be displayed if at least one of those conditions is true. Conditional members appear in details pages, but they do not appear in inline preview, grid, or table views.
Required fields always have a red asterisk. Conditional required fields have a red asterisk only if the condition is met. If a triggering field changes, the asterisk is recalculated immediately to reflect the new required status.
If a triggering field makes another field required and that field is in a different member group without a value, the member group will automatically enter edit mode, allowing you to fill in the required field and save the entity.
To add a condition, on the Conditional tab, select a property from the list and click Add. Then, click 
Add and select the related property. For example, setting AssetTypeToAsset to Poster means this field will be visible only if the asset type is a poster.
Required
To specify that a member is mandatory, turn on the Required switch.
To add a validation condition, click Add filter . In the Conditional validation section, select either Property or Relation, select a field name (for example, AssetTypeToAsset), select an operator (any, all, or none), and then click Add. For example, setting AssetTypeToAsset to Product Asset means this field will be mandatory if the asset type is a product asset.
To find empty required fields, use the Validation component.