CMIS ID Property Definition

The 'Id' is a system-assigned identifier that uniquely distinguishes this property within the CMIS repository. It is used internally for mapping, querying, and integration scenarios. This value is typically not user-editable.

Example

The 'Display Name' is a user-friendly label shown in user interfaces, reports, and configuration screens. It is intended to be descriptive and easily understood by end users. This value is provided by the CMIS repository and may be localized or customized by repository administrators.

Changing the display name in the repository will update how the property appears in Grooper.

The 'Query Name' is used in CMIS queries (such as SQL-like statements) to reference this property. It is typically a concise, system-friendly string and may differ from the display name.

Use this value when constructing custom queries or filters against the CMIS repository.

The 'Local Name' is the repository-specific name for the property, which may be used for integration or advanced configuration scenarios. It is often similar to the query name but may reflect repository-specific conventions.

The 'Local Namespace' provides the XML namespace or logical grouping for the property within the repository. This is relevant for advanced integration, custom queries, or when working with repositories that use custom namespaces.

The 'Description' offers additional information or guidance about the property’s purpose, usage, or constraints. It is typically provided by the repository administrator and may include instructions, formatting rules, or business context.

Displayed as a tooltip or help text in configuration screens.

The 'Type' indicates the data type of the property, such as String, Integer, Boolean, etc. If the property supports multiple values, the type is shown with [] (e.g., String[]).

This affects how values are entered, validated, and displayed in Grooper.

Can be one of the following types:

The 'Inherited' property is true if the property is inherited from a base CMIS content type or secondary type, rather than being defined directly on the current type.

Inherited properties may have restrictions on editing or removal.

Specifies the value automatically assigned to the property if no other value is provided.

Usage

• The default value is used when creating new objects or updating properties where a value is not explicitly set.
• If the property is multi-valued, only the first default value is shown here.

Example

If the default value is default-id-123, new documents will have this ID unless another is specified.

Provides a set of allowed ID values that can be selected for the property.

Usage

• If choices are defined, users can only select from these values (unless the property is configured as open choice).
• Choices help standardize data entry and enforce business rules.

Example

If choices are ID-001 and ID-002, only these values can be assigned (unless open choice is enabled).

Can be one of the following types:

The 'Updatability' setting determines if and how the property’s value can be changed. Possible values include read-only, read-write, or on-create only, as defined by the Updatability enumeration.

This affects whether the property can be edited in Grooper or during import/export operations.

The 'Choice' property is true if the property supports a predefined set of allowed values (choices). When enabled, users must select from the available options, unless 'Open Choice' is also enabled.

This is commonly used for dropdowns, picklists, or enumerated fields.

Can be one of the following types:

The 'Cardinality' specifies whether the property accepts a single value or multiple values.

• Single: Only one value is allowed.
• Multi: Multiple values can be assigned (e.g., a list or array).

This affects how values are entered and displayed in Grooper.

Can be one of the following types:

The 'Open Choice' property is true if users are allowed to enter values not present in the predefined choices. When false, only the listed choices are permitted.

This setting is relevant for properties with a fixed set of allowed values.

Can be one of the following types:

The 'Queryable' property is true if the property can be referenced in the WHERE clause of CMIS queries. This enables filtering and searching based on this property in repository queries.

Can be one of the following types:

The 'Orderable' property is true if the property can be used in the ORDER BY clause of CMIS queries. This allows sorting query results by this property.

Can be one of the following types:

The 'Required' property is true if a value must be provided for this property when creating or updating an object. Required properties cannot be left blank and must be populated to satisfy repository constraints.