Remove Level

The 'Level Count' property specifies how many levels of folders beneath the base folder will be removed.
For example, a value of 1 removes the immediate children, while a value of 2 removes the next level down. Increasing this value allows you to flatten deeper hierarchies in a single operation.

The 'File Extension' property allows you to limit the removal operation to folders whose attachments have a specific file extension. Enter one or more extensions, separated by commas (e.g., zip,pdf).
This is especially useful for removing folders created by unzipping files, while leaving other documents untouched. If left blank, all folders are considered regardless of extension.

Enable the 'Require Children' property to ensure that only folders containing child items are eligible for removal. This prevents empty folders from being considered, which can be useful when you want to avoid removing placeholder or empty nodes. This property is only applicable when 'Level Count' is set to 1.

The 'Filter Pattern' property lets you specify a regular expression to control which descendant items are promoted to the base folder when a level is removed. The pattern is matched against the relative path of each item (e.g., /0003/Images/Page (15)). Only items whose path matches the pattern will be moved; others remain in place.

If no filter is specified, all children of the deleted folders are moved to the root.

> Example:
To move only images and exclude previews, use a pattern like images.

Path Format

• Paths are relative to the Batch Folder on which the activity is executed.
• Use / as the path separator.

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.