Import Behavior

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

Remarks

The Import Behavior groups one or more Import Definitions that control how external content is brought into Grooper for a specific Content Type.

Configuration and Usage

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

Key Behaviors

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

Usage Scenarios

• Importing documents from a CMIS Repository and mapping their properties to Grooper fields.
• Supporting multiple import sources or content types within a single Content Type.
• Defining custom import logic for specialized document classes.

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

Properties

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

See Also

Import DefinitionContent CategoryContent ModelDocument TypeForm TypePage Type