Join

join action is used to unify (bring back together) 2 or more branches in one branch after a decisional action after join only one action can be connected as a successor a branch coming out from a decisional can be connected to any action, including to another join action on canvas, no matter if the join action is used before or after the branch when branches are unified in a join, we only need one of them to be executed in order to start executing the “join” action the process then continues how to configure the join action? go to process designers section and open a new or an existing process actions configuration can be performed once they are dragged and dropped on canvas using join action in a process flow join action is used to unify (bring back together) 2 or more branches in one branch after a decisional action a join action can have multiple connectors that come from multiple predecessor actions, but only 1 connector that goes to a successor action step 1 drag the join action from toolbar and drop it on canvas step 2 connect previous actions to join action in order to unify branches coming out from a decisional action