Dispose Batch

When enabled, this task will delete the batch.

If a File Store is selected here, the content files for the batch will be migrated to the indicated file store. This feature is intended to allow a tiered storage architecture, where production batches are stored on high-speed solid state drives, for example, while completed batches are archived to less expensive, slower storage. In such cases, please note the following general guidelines:

• The primary File Store should be configured to use high-speed speed storage, as all new production batches are written here.
• The final step in the batch process should include a Dispose Batch action configured to migrate the batch to a file store which uses standard storage.
• It is recommended that tiered storage configurations use a dedicated Grooper repository for production batches, segregating test batches to a repository configured to use standard storage.

If a folder is selected here, the batch will be moved to this location. This is intended to support archiving production batches to a folder in the test branch upon completion. If this property is set, then the Dispose Batch action should be the final step in the Batch Process.

Determines what happens when an error occurs processing an activity.

The maximum number of consecutive errors, after which a critical stop will be raised. A critical stop will cause services to stop running.

Specifies the parallel processing mode for this activity. Can be one of the following values:

• Multiple - Multiple instances can run concurrently.
• PerMachine - Only a single instance can run per machine.
• Single - Only a single instance can run per Grooper repository.