Batch Transfer

The 'Destination Repository' property specifies the remote Grooper repository that will receive the transferred batch. This must be configured in the Root node with a valid API key. Select the appropriate repository from the drop-down list. If the repository is not available or cannot be connected, check your API Services configuration and network connectivity.

The 'Target Process' property determines which Batch Process the transferred batch will be assigned to on the destination repository. Select a process that matches your workflow requirements. The available processes are retrieved from the remote system after a successful connection.

The 'Target Step Name' property specifies which step of the selected Batch Process the transferred batch will begin at. Choose a step that aligns with your intended workflow. This ensures the batch resumes processing at the correct point after transfer.

Enable 'Start Paused' to have the transferred batch enter a paused state on the destination repository. This is useful if you want to review or configure the batch before processing resumes. If disabled, the batch will be ready for immediate processing.

Enable 'Dispose Batch' to automatically delete the source batch after a successful transfer. This helps prevent duplication and reduces storage requirements. Use with caution, as deletion is permanent and cannot be undone.

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.