CMIS Folder

The 'Object Name' property displays the current name of this CMIS Object in the external repository.

Purpose

• Identifies the object in user interfaces, expressions, and automation.
• Used when searching, filtering, or referencing items in Grooper.

Configuration

• The value is synchronized with the cmis:name property in the repository.
• Renaming the object in Grooper (using the Rename command or by editing this property) updates the name in the external system, subject to permissions.

Impact of Changes

• Changing the name may affect links, references, or automated processes that rely on the object's original name.
• Ensure that the new name complies with repository naming rules and does not conflict with existing items.

Example

The 'Base Type' property shows the fundamental type of the CMIS Object as defined by the repository.

Purpose

• Distinguishes between folders (which can contain other objects) and documents (which represent content items).
• Used to control available actions, display icons, and automate workflows.

Configuration

• The value is determined by the cmis:baseTypeId property in the repository.
• Common values are Document and Folder.

Impact of Changes

• The base type is set when the object is created and cannot be changed after creation.
• Determines which commands and behaviors are available for the object.

Example

The 'Object Type' property displays the display name of the content type assigned to this object.

Purpose

• Identifies the specific content type or schema applied to the object.
• Used for mapping metadata, configuring import/export, and automating processes.

Configuration

• The value is derived from the cmis:objectTypeId property and resolved to its display name.
• Content types are defined in the external repository and may include custom types.

Impact of Changes

• Changing the object type (where supported) may alter available properties, validation rules, and behaviors.
• Not all repositories allow changing the object type after creation.

Example

The 'Secondary Types' property lists any additional content types applied to the object, as defined in the CMIS Repository.

Purpose

• Enables the object to inherit additional properties, behaviors, or metadata from multiple types.
• Supports advanced scenarios such as tagging, categorization, or compliance.

Configuration

• The value is a comma-separated list of display names for all secondary types assigned to the object.
• Secondary types are managed in the repository and may be added or removed as needed.

Impact of Changes

• Adding or removing secondary types may expose or hide additional properties and affect validation.
• Ensure that changes comply with repository policies and do not conflict with automated processes.

Example

The 'Allowed Actions' property lists all operations currently permitted for this CMIS Object in the external repository.

Purpose

• Informs users and automation about which actions (such as update, delete, move) are available.
• Used to enable or disable commands in the UI and to validate automation steps.

Configuration

• The value is a comma-separated list of action names, as reported by the repository.
• Actions are determined by repository permissions, object state, and content type configuration.

Impact of Changes

• The set of allowed actions may change dynamically based on user permissions or repository policies.
• Attempting a disallowed action will result in an error from the repository.

Example

The 'Created By' property displays the user account or identity that originally created this object in the external CMIS Repository.

Purpose

• Provides audit and traceability information for compliance and review.
• Useful for filtering, reporting, or automating processes based on object ownership.

Configuration

• The value is synchronized with the cmis:createdBy property in the repository.
• It is typically set automatically by the repository at the time of object creation.

Impact of Changes

• This property is read-only and cannot be changed from Grooper.
• The value may be blank if the repository does not track creator information.

The 'Creation Date' property shows the timestamp when the object was first created in the external CMIS Repository.

Purpose

• Supports auditing, reporting, and lifecycle management.
• Can be used to filter or sort objects by age in queries and automation.

Configuration

• The value is synchronized with the cmis:creationDate property in the repository.
• It is set automatically by the repository and uses the repository's time zone or UTC.

Impact of Changes

• This property is read-only and cannot be changed from Grooper.
• The value is guaranteed to be set for all objects that support creation tracking.

The 'Last Modified By' property displays the user account or identity that most recently updated this object in the external CMIS Repository.

Purpose

• Enables tracking of changes for compliance, review, or troubleshooting.
• Useful for identifying responsible users in collaborative environments.

Configuration

• The value is synchronized with the cmis:lastModifiedBy property in the repository.
• It is updated automatically by the repository whenever the object is modified.

Impact of Changes

• This property is read-only and cannot be changed from Grooper.
• The value may be blank if the repository does not track modification information.

The 'Last Modification Date' property shows the timestamp of the most recent update to this object in the external CMIS Repository.

Purpose

• Supports auditing, version control, and process automation.
• Can be used to detect stale or recently changed objects in queries and workflows.

Configuration

• The value is synchronized with the cmis:lastModificationDate property in the repository.
• It is updated automatically by the repository on each modification and uses the repository's time zone or UTC.

Impact of Changes

• This property is read-only and cannot be changed from Grooper.
• The value is guaranteed to be set for all objects that support modification tracking.