The Split Join
-
Allows multiple subflows on the current work object to execute in parallel
-
Allows multiple subflows on any one work object to execute in parallel
-
Always resumes execution of the parent flow as soon as the first subflow completes
-
All of the above
The Split-Join shape in Pega enables parallel processing of multiple subflows on the current work object, improving performance for tasks that can run concurrently. It does NOT operate on arbitrary work objects, and it waits for ALL subflows to complete before resuming the parent flow.
In Pega BPM, the Split-Join shape (technically the Split-Join flow shape/utility) is used to launch multiple subflows on the SAME work object so they execute in parallel, then rejoins them once the specified completion condition (e.g., all, one, or a percentage) is met. It is scoped to the current work object's instance, not 'any' work object — that distinguishes it from Split-For-Each, which spawns subflows across multiple work objects/pages. It also does not always resume as soon as the first subflow completes; resumption depends on the configured join condition (could require all subflows, or a specific count). So the first option is correct because it precisely captures the 'current work object' and 'parallel execution' semantics, while the others either broaden scope incorrectly or hardcode a join behavior that isn't guaranteed.