The Branch and Merge activities are grouped under the Subprocess activity.
The Subprocess activity has the following properties:
Table 10-26 Subprocess Activity Properties
|
Property Name |
Description |
|---|---|
|
Identifier |
A unique string value that identifies the activity. Workflow Builder auto-generates this value in Activity_<N> format, where <N> represents an alphanumeric value that contains 7 characters. |
|
Name |
Specifies a name for the activity. |
In a workflow that supports parallel processing, the Branch activity allows multiple users to act on different areas of the work item in parallel. After the users have completed their work, the Merge activity synchronizes the incoming branches in the flow.
A workflow can have multiple Branch activities, but each Branch activity must have an associated Merge activity. All flow paths leading out of a Branch activity will execute.
The Branch activity does not support synchronization between the branches while they are executing. Each branch must not depend on data being updated in another branch. The data synchronization is enforced by the Merge activity. After the Merge activity completes, all of the data set in the branches is available.
The Branch activity has the following properties:
Table 10-27 Branch Activity Properties
|
Property Name |
Description |
|---|---|
|
Identifier |
A unique string value that identifies the activity. Workflow Builder auto-generates this value in Branch_<N> format, where <N> represents an alphanumeric value that contains 7 characters. |
|
Name |
Specifies a name for the activity. |
Data items are not supported with this activity.
Email templates are not supported with this activity.
The Problems tab provides details of the errors and warnings associated with the activity in a workflow. For more information about validating workflow activities, see Validating a Workflow.
In a workflow that supports parallel processing, the Merge activity synchronizes the incoming branches in the flow. The Merge activity is used in conjunction with the Branch activity, which allows two users to act on different areas of the work item in parallel. After the users have completed their work, the Merge activity synchronizes the incoming branches.
A workflow can have multiple Branch activities, but each Branch activity must have an associated Merge activity.
The Merge activity has the following properties:
Table 10-28 Merge Activity Properties
|
Property Name |
Description |
|---|---|
|
Identifier |
A unique string value that identifies the activity. Workflow Builder auto-generates this value in Merge_<N> format, where <N> represents an alphanumeric value that contains 7 characters. |
|
Name |
Specifies a name for the activity. |
Data items are not supported with this activity.
Email templates are not supported with this activity.
The Problems tab provides details of the errors and warnings associated with the activity in a workflow. For more information about validating workflow activities, see Validating a Workflow.