CMIS Type Definition - Generate Local Type

Select the source CMIS content type whose schema and properties will be used to generate a new Content Type and Data Model in Grooper. This property determines the structure, available fields, and base type (document or folder) for the generated type.

Changing this value will update the list of available properties and secondary types that can be included in the generated Data Model.

How to Use

• Choose a CMIS content type from your connected repository that best represents the document or folder structure you want to import.
• The selected type's schema, including its property definitions and base type, will be mirrored in the generated Grooper Content Type.

Impact

• The available options for 'Secondary Types' and 'Included Properties' are determined by the selected CMIS type.
• If you change this property after configuring other options, you may need to reselect secondary types and included properties to match the new schema.

> Tip: Use this property to ensure your Grooper configuration aligns with the external system's structure, making import/export seamless.

Use this property to select one or more secondary CMIS types whose properties should be incorporated into the generated Content Type. Secondary types allow you to extend the schema with additional fields defined in the external repository.

When to Include Secondary Types

• If your CMIS repository uses secondary types to add metadata or classification to documents, include them here to ensure all relevant fields are available in Grooper.
• Secondary types are often used for compliance, workflow, or custom metadata scenarios.

Configuration Guidance

• Click the editor to browse and select from available secondary types in the connected repository.
• The properties from selected secondary types will appear as additional fields or sections in the generated Data Model.
• You can include multiple secondary types as needed.

Example

> If the primary CMIS type represents an invoice, and a secondary type defines compliance metadata, include the secondary type to > capture all relevant information in Grooper.

> Note: If you change the primary CMIS type, review your secondary type selections to ensure they are still relevant.

Select which CMIS properties from the primary and any included secondary types should be mapped to fields in the generated Data Model. Only the selected properties will be available for extraction, validation, and export in Grooper.

How to Configure

• Review the list of available properties, which is determined by the selected CMIS type and any secondary types.
• Check the properties you want to include in the generated Data Model. These will become fields or sections in Grooper.
• Duplicates are not allowed; each property must have a unique display name.

Impact

• Only included properties will be available for mapping, extraction, and validation in Grooper.
• Excluding unnecessary properties helps keep your Data Model concise and easier to maintain.

Example

> For an invoice type, you might include properties such as InvoiceNumber, InvoiceDate, and TotalAmount.

> Tip:
> Review the list of available properties and select only those that are relevant for your solution to keep the Data Model concise > and maintainable.

> Validation: If you select duplicate properties (by display name), you will be prompted to resolve the conflict before saving.

Choose a property to store the name of the document type in the generated Content Type. This is typically used when importing or exporting documents to ensure the correct type is referenced in the external system.

When to Use

• Set this property if your integration scenario requires Grooper to track or set the document type name as a field value.
• This is especially useful for solutions where the document type is used for routing, classification, or downstream processing.

Configuration Guidance

• Only list fields with a string type can be selected.
• If set, the selected property will be used to map the document type name during import and export operations.
• When this property is set, Grooper will generate child Document Types for each possible value (choice) of the selected property.

Example

> Select a property such as cmis:documentType to store or retrieve the type name for each document.

> Note: If you do not set this property, the generated Content Type will be created as a Document Type or Content Category based on the CMIS base type.

Specify the parent Content Type or Content Model under which the generated Content Type will be created. If left blank, a new Content Model will be created at the root of the project.

How to Use

• Select an existing Content Model, Content Category, or Document Type as the parent location for the generated type.
• If you do not specify a location, a new Content Model will be created using the value of 'Content Model Name'.

Impact

• Organizing your generated types under an existing model helps maintain a logical structure in your Grooper repository.
• If you are importing multiple types from the same repository, consider grouping them under a single Content Model for consistency.

> Tip: Use this property to align imported types with your existing Grooper hierarchy, or leave it blank to create a new model for imported types.

Enter the name for the new Content Model if you are not placing the generated Content Type under an existing model or type. This property is required when no location is specified.

How to Use

• Provide a descriptive name for the new Content Model that reflects the source or purpose of the imported types.
• The Content Model will be created at the root of your Grooper project and will serve as the parent for the generated Content Type and Data Model.

Impact

• The name must be unique within the project.
• If you later import additional types from the same repository, you can reuse the same Content Model to group related types.

> Note: This property is only required if 'Location' is not set.

Specify the name for the generated Content Type. This name will be used to identify the type within Grooper and in any import or export definitions.

How to Use

• Enter a unique and descriptive name that reflects the purpose or source of the type, such as Invoice, Contract, or HR Document.
• The name must be unique within the selected location or Content Model.

Impact

• The Content Type name is used throughout Grooper for configuration, mapping, and reporting.
• Choose a name that will be easily understood by users and administrators.

> Tip: Use consistent naming conventions for imported types to simplify management and integration.