Decisional

the decisional action will execute one of the many branches configured, depending on whether a specified condition is met if no condition is met, you have the option to define a default path for the action you can add several actions after a decisional and build as many cases as you need a case configuration consists in defining the condition and its successor branch (called "target") a target action is an action connected to the decisional as a successor connecting a target action to the decisional will automatically generate a case that requires configuration the outcome of a case can be true or false , depending on how the condition is evaluated the value of the evaluation determines the next action target to be processed within the flow the process will only consider the first true evaluation, continuing the process on the correspondent target branch all other cases will be ignored once the first true evaluation of a case is met how to configure the decisional action? go to the process designer section and open a new or an existing process actions configuration can be performed once they are dragged and dropped on canvas from the toolbar step 1 drag the decisional action onto the canvas and click on it to open the properties panel step 2 you can edit the action name step 3 if there is at least one target action connected, you will see in the properties panel a case generated that requires configuration (not set) click on it to go to the case configuration steps if there are no target actions connected to decisional , you will see a message displayed in properties panel guiding you to "please connect one or more actions to start configuring your cases " step 4 case configuration name set a name for you case; it will be also displayed on the connector going to this case's target action to easily identify the branches advanced filtering builde r here you can add either a condition or a group adding a condition once you press add condition , an expression will be displayed where you will need to define first operand (left) click on the + icon and a process variables list will open select the process variable to be compared or input a value manually operator click to select the operator second operand (right) you can either fill in a hard coded value (e g 1000, name etc ) or select another process variable to be used as an operand; logical operators you can also use logical operators to join together multiple expressions and build complex conditions on click , you can switch between and to or operators when adding a condition or a group, please note that and has priority over or in evaluation please see below the variable/conditions matrix for dynamic conditions adding a group once you have created a group, you can rename it add new conditions to the group or drag & drop previously created conditions add a subgroup ungroup this action will delete the group, but the conditions will be kept and placed outside the group delete group this action will delete the group and the conditions contained in the group 3 target select from the list the go to action that will be processed within the flow when the specified condition is met the target list will include only the actions connected to the decisional as successors the actions already assigned as target in previous cases will no longer be available in the list when configuring a case to have multiple actions reach the same path, consider using a join action step 5 defining a default case is essential when configuring a decisional when none of the conditions defined in other cases is met, two things can happen the flow stops this will be the default behaviour if no default case is defined 2 the flow follows the default path by setting a default path (a target action that will be processed only when no above condition is met), you can make sure your logic can handle cases that were not considered at first the target action for the default path must be connected on canvas to decisional as shown below once the target action for default path is connected it will be automatically displayed in configuration this is an example of how the decisional action looks on the canvas