Split Join:
You use the Split Join shape to call multiple independent processes that operate in parallel and then later rejoin. For example,a mortgage application process may require that a user validates the home buyer's credit history. At the same time,another user must perform a title search. Both of these processes are unrelated and can be performed in sub processes that proceed independently and in parallel. When the sub processes are complete,the main mortgage application process can continue. This is similar to a parallel process in the case life cycle — when all the processes in a stage are completed,the case enters the next stage or is resolved. However,the Split Join shape gives you the flexibility to use join conditions that determine when the primary process can continue. The join condition may iterate over a when condition or a count to determine when to resume the flow. For instance,a Split Join may include three separate approval sub processes. You can specify that only two of the three approvals must be completed before resuming the main flow.
Split For Each:
Split For Each shape allows you to run one sub process multiple times by iterating through a set of records stored in a page list or page group. When the items on the list have been processed,the main flow continues. For example,you can use a Split For Each to iterate over a list of vendors and send a quote request from each vendor on the list. Like the Split Join,you can use a join condition to control when the primary process resumes. If you use an iterate join condition,you can start flows for elements of the Page Group or Page List property one by one,and configure testing conditions to determine whether to continue
Spinoff:
When a work object advancing through a flow reaches the Spin-off shape, Process Commander starts execution of a different flow, using the current or a different work object. Processing in the current flow rule continues in parallel, without waiting for the other flow to complete
You use the Split Join shape to call multiple independent processes that operate in parallel and then later rejoin. For example,a mortgage application process may require that a user validates the home buyer's credit history. At the same time,another user must perform a title search. Both of these processes are unrelated and can be performed in sub processes that proceed independently and in parallel. When the sub processes are complete,the main mortgage application process can continue. This is similar to a parallel process in the case life cycle — when all the processes in a stage are completed,the case enters the next stage or is resolved. However,the Split Join shape gives you the flexibility to use join conditions that determine when the primary process can continue. The join condition may iterate over a when condition or a count to determine when to resume the flow. For instance,a Split Join may include three separate approval sub processes. You can specify that only two of the three approvals must be completed before resuming the main flow.
Split For Each:
Split For Each shape allows you to run one sub process multiple times by iterating through a set of records stored in a page list or page group. When the items on the list have been processed,the main flow continues. For example,you can use a Split For Each to iterate over a list of vendors and send a quote request from each vendor on the list. Like the Split Join,you can use a join condition to control when the primary process resumes. If you use an iterate join condition,you can start flows for elements of the Page Group or Page List property one by one,and configure testing conditions to determine whether to continue
Spinoff:
When a work object advancing through a flow reaches the Spin-off shape, Process Commander starts execution of a different flow, using the current or a different work object. Processing in the current flow rule continues in parallel, without waiting for the other flow to complete