Merge

Can be one of the following types:

Determines the output file type for the merged result.

• Select a Merge Format to control the file type and structure (e.g., PDF, TIFF, ZIP).
• The available options depend on the installed Export Formats.
• The chosen format affects downstream compatibility and features (such as bookmarks or compression).

> Tip: Choose a format that matches your export or archival requirements.

Use this property to define a dynamic filename for the merged attachment using a Path Expression.

• If not set, a default filename will be generated automatically.
• The expression can reference Data Elements from the associated Content Type for personalized or structured naming.
• To enable intellisense for Data Elements, set the 'Content Type' property before editing this property.

> Example:
> $\"Invoices\\{InvoiceNumber}_{Date:yyyyMMdd}\"

> Note: If 'Custom Filename' is set, this property is ignored.

Set this property if you want to reference Data Elements in the 'Attachment Name' expression.

• Assigning a Content Type enables intellisense and validation for field references in the Path Expression.
• This is especially useful when filenames should include extracted or classified data.

> Tip: Always set 'Content Type' before configuring 'Attachment Name' for best editing experience.

When set to true, this option will automatically remove all child Batch Folders and Batch Pages from the current folder after the merged file is created.

• Use this to clean up the batch structure and retain only the merged output.
• This is useful in scenarios where the original documents or pages are no longer needed after merging, such as archival or export workflows.
• If set to false, the original folder structure and its contents are preserved.

> Warning: This action is irreversible. All child content will be permanently deleted from the batch. Ensure you have exported or backed up any required data before enabling this option.

Example:

• Enable 'Clear On Completion' to keep only the merged PDF and remove all original pages after combining scanned pages into a single document.

Specifies a custom file name for the merged output, saving it as a separate file rather than as an attachment.

• If set, the merged file is saved with this name and is not treated as the folder's attachment.
• Any existing file with the same name will be overwritten.
• Use this to generate files for later export or for use in custom Activities or Object Libraries.
• Custom files saved in this way can be exported using the Attached File Export Format, or accessed from custom code.
• If this property is set, the 'Attachment Name' property is ignored.

> Note: Use 'Custom Filename' to generate output files for downstream processes without affecting the current attachment.

Example:

• Set 'Custom Filename' to "MergedDocument.pdf" to save the merged output as a file named "MergedDocument.pdf" in the folder.

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.