Export

The 'Export Behaviors' property allows you to define one or more Export Behaviors directly on the Export activity. Each entry specifies the export configuration for a particular Content Type. When a document is exported, the behavior that matches the document's type (or a base type) is executed. If no local behaviors are defined, shared behaviors from the Content Type are used instead.

• To add a behavior, click the collection editor and select the Content Type and export settings.
• An entry with no Content Type acts as the default behavior for documents with no type or no matching behavior.

> Example:
Define a behavior for "Invoice" documents and another for "Contract" documents, each with different export destinations or formats.

Can be one of the following values:

The 'Shared Behavior Mode' property controls how shared Export Behaviors (those defined on Content Types) are used in conjunction with local behaviors. This determines the order of precedence and whether local or shared behaviors are executed first, or if one overrides the other.

> Tip: Choose the mode that best matches your export requirements and reuse strategy.

The 'Required' property determines what happens if a document is encountered for which no Export Behavior is defined.

• If set to true, an error is raised and processing stops.
• If set to false, the document is ignored and export continues for other items.

> Tip: Set to true to enforce strict export requirements, or false to allow flexibility for unconfigured types.

A combination of the following flags:

The Error Disposition property determines the system's response to errors that occur while executing the activity.

• Flag: The affected Batch Folder or Batch Page will be flagged for review.
• Log: The error will be written to the Grooper event log.
• Stop: Processing will halt, the Batch will be set to an error state, and all pending tasks will be deleted.

You can combine multiple options using the IssueDisposition flags.
Adjust this property to match your organization's error handling and escalation policies.

If the number of consecutive errors reaches this value, a critical stop will occur and the Activity Processing service will halt further processing.

• Use this property to prevent runaway failures and to ensure that persistent errors are escalated for review.
• Set to a higher value to allow more retries before stopping, or to a lower value for stricter error control.

Can be one of the following values:

The Concurrency Mode property determines whether the activity can be executed in parallel across multiple Batch Objects, or if it must run sequentially.

• This setting affects which Processing Queue the activity is submitted to and how tasks are distributed.
• Choose the appropriate mode based on the activity's thread safety and resource requirements.