Batch Transfer Batch TransferTransfers a Batch to another Grooper repository.
This activity is designed to facilitate distributed applications, providing a secure mechanism for moving batches between Grooper repositories over web protocols. To use this activity, the following prerequisites must be met:
Inherits from: Unattended Activity
The following 7 properties are defined.
| Property Name | Description |
|---|---|
| General | |
| Target Repository | Type: CMIS Repository
The Grooper repository to which the batch will be transferred. The CMIS Repository selected must represent a connection to a Grooper repository. |
| Target Step | Type: CMIS Folder
The Batch Process Step at which the Batch will be started. If a step is selected here, the batch will be launched into the associated Batch Process, starting at the specified step. |
| Target Batch Status | Type: BatchStatus, Default: Ready
The Batch status for target batches after transfer is complete. Can be one of the following values:
|
| Delete Batch | Type: Boolean, Default: False
Specifies whether the batch on the local system should be deleted after successful migration. |
| Processing Options | |
| Error Disposition | Type: IssueDisposition, Default: Flag, Log
Determines what happens when an error occurs processing an activity. |
| Maximum Consecutive Errors | Type: Int32, Default: 0
The maximum number of consecutive errors, after which a critical stop will be raised. A critical stop will cause services to stop running. |
| Concurrency Mode | Type: ConcurrencyMode, Default: Multiple
Specifies the parallel processing mode for this activity. Can be one of the following values:
|