Dispose Batch

The 'Delete Batch' property controls whether the batch is permanently deleted after processing.
Enable this option to remove batches that are no longer needed, freeing up storage and reducing clutter. If enabled, all other disposition options (such as moving or migrating) are ignored. > Warning: Deletion is permanent and cannot be undone. Use with caution, especially in production environments.

The 'Remove Job History' property deletes all job and task history associated with the batch.
This reduces database size and improves performance, especially in environments with high batch volumes. Enable this option if you do not need to retain processing history for completed batches.

The 'Move to FileStore' property allows you to migrate all files associated with the batch to a different File Store. This is useful for implementing tiered storage, such as moving completed batches from high-speed production storage to lower-cost archival storage.

• Select a File Store to which files should be moved.
• Ensure the target File Store is properly configured and accessible.
• Migration is performed after any rules or folder moves are applied.

> Example: Move completed batches to a network share or cloud storage for long-term retention.

The 'Move to Folder' property specifies a Folder where the batch should be moved after processing. This is typically used to archive completed production batches to a test or archive branch.

• Select a destination Folder for archiving.
• If 'Group By' is set, subfolders will be created based on date.
• Use this to organize batches for future reference, compliance, or audit.

> Tip: Use in combination with 'Group By' for chronological organization.

Can be one of the following values:

The 'Group By' property enables automatic creation of subfolders under the target folder, based on the selected date part (e.g., year, month, day). This helps organize archived batches chronologically for easier retrieval and management.

• Choose a grouping such as Year, Month, or Day.
• Subfolders are created as needed during the move operation.

> Example: Set to Month to archive batches in folders like 2024/06.

The 'Rules' property allows you to specify one or more Data Rules to be executed on the batch's root node before final disposition. Use this to perform last-minute data normalization, validation, or business rule enforcement.

• Add Data Rules to the collection as needed.
• Rules are executed in the order listed.
• Any changes are saved before the batch is moved, migrated, or deleted.

> Tip: Use rules to ensure data quality or compliance before archiving or deleting batches.

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.