...
Bulking of data can only be performed for data being sent in the ConsumeCycleUDR and not for the states that are sent in the state-specific UDRs.
Bulk forwarding is not performed when the Workflow Bridge agents are executing on the same EC.
...
The Workflow Bridge collection agent requires that all Workflow State UDRs are returned before the next Workflow State UDR are is forwarded into the workflow. The only exception to this is that the collection agent accepts to have several ConsumeCycleUDRs outstanding at the same time. However, all ConsumeCycleUDRs must have been returned before the next type of Workflow State UDRs are is forwarded. If the forwarding workflow is a batch workflow, this means that all ConsumeCycleUDRs must be returned before the DrainCycleUDR is forwarded into the workflow.
...
Load balancing can be used to direct different UDRs to different workflow instances using a static load-balancing strategy (see Workflow Bridge Profile Configuration General Tab). Each workflow instance in the collection workflow is assigned a LoadId by adding this field to the workflow instance table in the Workflow Properties , and then entering specific Ids for each instance. In the APL code, it is possible to determine specific UDRs that can have the forwarding workflow routed to a designated LoadId.
...
| Option | Description |
|---|---|
| Transport | Select the transport protocol that you prefer for the best performance. |
| Scroll ignore | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
The section contains the following subsections: |
...