CMIS Export

Select the target CMIS Repository where documents and folders will be exported.

• This property determines the destination system for all exported content.
• Only repositories that have been imported into Grooper are available for selection.
• Changing the repository will reset related properties such as 'Target Folder', 'Object Type', and mappings.

Example:
Choose a repository named HR Documents to export all HR-related content to that system.

The 'Link Name' property determines the label assigned to the Content Link created during export.

• This name is used to identify the exported content link on the Batch Folder or document.
• If not set, a default value such as "Export" is typically used.
• You can use different link names to distinguish between multiple export destinations or export runs.
• The link name appears in the Grooper UI and can be referenced in downstream activities or scripts.

Example:

• Set 'Link Name' to "CMIS Export" to clearly indicate that the link references a CMIS Repository export.
• Use different names like "Archive Export" or "Cloud Export" if exporting to multiple systems.

<em>Tip: Use a descriptive link name to make it easier for users and automation to identify the correct exported content, especially when multiple links are present on a Batch Folder.</em>

Specifies the base export folder in the CMIS Repository.

• Use the 'Subfolder Path' property to define additional subfolder levels inside this folder.
• If the repository supports unfiled documents and 'Object Type' is document-based, this value may be left blank to export documents in an unfiled state (not visible in the folder tree).
• If items are always exported as children of an exported folder, this value can be left blank.

Example:
Set to /Invoices/2024 to export all documents to the "2024" subfolder under "Invoices".

• Use this property to dynamically create subfolders based on document data or expressions.
• If the specified path does not exist, new folders will be created as needed.
• If not set, files are exported to the root of the 'Target Folder'.

Example:
Use an expression like $"{Department}/{Year}" to organize exports by department and year.

• Determines the CMIS Type Reference used for any subfolders created by the 'Subfolder Path' expression.
• The selected type should not have required properties other than cmis:name.
• If not set, the default type cmis:folder is used.

Example:
Select a custom folder type to apply specific metadata or behaviors to exported subfolders.

Can be one of the following values:

Duplicate name conflicts can occur when adding, moving, or renaming CMIS documents, if the parent folder already contains a child with the same name.

• Determines the CMIS type to be assigned to exported objects.
• Can be a document-based or folder-based type.
• Writable properties of the selected type are available in 'Write Mappings'; all properties are available in 'Read Mappings'.
• If a document-based type is selected, a CMIS Document is created for each Grooper document.
• If a folder-based type is selected, a CMIS Folder is created, and the batch structure is exported as a folder hierarchy.

Example:
Select a custom document type to map Grooper fields to specific repository metadata.

• Secondary types allow you to attach additional metadata schemas to exported documents or folders.
• Only available if the repository supports secondary types and a primary 'Object Type' is selected.
• Use this to add custom fields or behaviors beyond the primary type.

Example:
Add a "Retention Policy" secondary type to all exported HR documents.

• Use 'Write Mappings' to map Grooper data fields to CMIS properties for the exported object.
• Only writable properties of the selected 'Object Type' and any secondary types are available.
• Supports expressions and value transformations.

Example:
Map the Grooper field "Invoice Number" to the CMIS property cmis:invoiceNumber.

• Use 'Read Mappings' to retrieve values from the exported CMIS Object and update the source Grooper document.
• Commonly used to capture repository-generated IDs, URLs, or other post-export metadata.
• Only properties available on the exported object can be mapped.

Example:
After export, read the repository-assigned document ID and store it in a Grooper field for future reference.

• Supports exporting each document in one or more file formats (e.g., PDF, TIFF, native).
• Each format is exported with the same name, type, properties, and location, but with a different file extension.
• At least one export format must be defined for document-based exports.

Example:
Add both "PDF" and "TIFF" formats to export each document in both file types.