Export Behavior

Defines a set of Export Definitions for a Grooper Content Type.

Remarks

The Export Behavior groups one or more Export Definitions that control how content is exported from Grooper for a specific Content Type.

Configuration and Usage

• Attach an Export Behavior to a Content Type to enable export to external systems such as file systems, content repositories, databases, or mail servers.
• Add one or more Export Definitions to specify the rules, mappings, and connectivity for each export scenario.
• Each Export Definition can target a different destination, content type, or mapping strategy.

Key Behaviors

• Supports multiple export definitions for complex scenarios (e.g., exporting to several destinations or with different mappings).
• Enables fine-grained control over how documents and folders are named, mapped, and processed during export.
• Behaviors are inherited by descendant Content Types, allowing for default export logic with local overrides.

Usage Scenarios

• Exporting documents to a file system, CMIS Repository, or other external system.
• Supporting multiple export destinations or content types within a single Content Type.
• Defining custom export logic for specialized document classes.

> Export Behaviors are typically configured by designers as part of a Content Model to automate and standardize content delivery.

Properties

Name	Type		Description
Content Type	Content Type	►	The content type to which this behavior is bound. EditorContent Type Editor
Export Definitions	Export Definition[]	►	The collection of Export Definitions that specify how content is exported for this Content Type. EditorObject Collection Editor ConverterCollection Converter Each Export Definition defines a destination, mapping, and rules for exporting documents or folders. Multiple definitions can be added to support different destinations, content types, or mapping strategies. The order of definitions may determine precedence when multiple definitions could apply. How to Use Add an Export Definition for each external destination or scenario you want to support. Configure the destination, content type, and property mappings for each definition. When exporting, Grooper will use the appropriate definition based on the destination and content type of the outgoing item. > Use multiple definitions to handle complex export requirements, such as exporting to several systems or supporting different document structures.

See Also

Export DefinitionContent CategoryContent ModelDocument TypeForm TypePage Type

Used By

Export