Simple Rules Decision

The Simple Rules Decision plugin in Joget DX 8 offers a straightforward, no-code approach to defining routing and actions within a process. 

Configure simple rules

To configure Simple Rules, drag and drop the Route element onto the canvas in Process Builder,  click on it, and select Mapping.

When adding Simple Rules in field Plugin, you will see the following fields available for configuration:

• Rules: Here, Rules properties are defined.
  • Add Rule: Add a Rule. Below, see Add Rule properties.
  • Add Action: Adds an Action within the ELSE THEN statement. Below, see Add Action properties.

Add Rule 

Add Rule allows you to define rules based on conditions. Users can specify whether conditions check for equality or inequality and set up multiple conditions to be evaluated using AND or OR logic. This feature ensures that workflows follow precise, user-defined criteria.

Allows you to define rules based on conditions.

• Toggle between EQUAL and NOT EQUAL: Determines whether the condition checks for equality or inequality.
  
• Split Type: Specifies how multiple conditions within a rule are evaluated.
  
  • AND
  • OR
    
• Add Condition: Adds specific conditions within the IF statement.  Below, see Add Condition properties.
• Add Group: Adds a Group within the IF statement. Properties will be similar to Add Rule properties.
• Delete Rule: Removes a defined rule.
  
• Sort: Allows reordering of rules.
  
• Add Action: Adds an Action within the THEN statement.

Add conditions

You can configure specific conditions within the IF statement. Users can define conditions using operators such as Equal, Greater Than, Less Than, and more to tailor the workflow logic to their specific needs.

When you select + Add condition, you will see the following fields available for configuration:

• Toggle between EQUAL and NOT EQUAL: Determines whether the condition checks for equality or inequality.
  
• Variable: The user inputs the variable name.
• Operation:  
  • Equal: 

    Check if the workflow variable is equal to the specified value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable country value is USA, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Greater Than:
    

    Check if the workflow variable is greater than the specified value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable price value is greater than 2, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.
    

  • Greater Than Or Equal To:
    

    Checks if the workflow variable is greater than OR equal to the specified value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable price value is greater than OR equal to 2, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Less Than:
    

    Check if the workflow variable is less than the specified value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable price value is less than 2, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Less Than Or Equal To:
    

    Checks if the workflow variable is less than OR equal to the specified value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable price value is less than OR equal to 2, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Is True:
    

    Check if the workflow variable matches with the value 1 or true.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable isUrgent value is true, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Is False:
    

    Check if the workflow variable matches with the value 0 or false.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable isUrgent value is false, based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • Contains:
    

    Check if the value of a field contains a specified substring in a value.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable country value contains the substring US (e.g., USA, USSR), based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

  • In:
    Check if the country field matches any of the values in a specified list of values.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    
    
    A ";" must be added between items of specified value to work. (Item1;Item2;Item3)
    Based on the workflow above, if the workflow variable country value matches any values in the specified list (USA, Canada, or Mexico) based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.
  • Regex Match: 
    

    Evaluate whether a field's value matches a regular expression (regex) specific pattern.
    Simple Rules example configuration as shown:
    
    The following workflow design is used:
    
    Based on the workflow above, if the workflow variable email matches the pattern of a valid .com email address (^[\\w.%+-]+@[\\w.-]+\\.com$), based on conditions configured in the decision plugin, it will direct to Activity 1. For any other value, it will follow the Else Then condition and route to the otherwise transition to Activity 2.

• Value: User to input the value of the Variable.
• Delete Condition: Removes a defined condition.
  

Add actions

Add Actions defines the actions to be taken if the conditions in the IF statement are met. Users can specify whether the action affects transitions or workflow variables, ensuring the workflow responds appropriately to different scenarios.

When you select + Add Action, you will see the following fields available for configuration:

• Type: Specifies whether the action affects transitions or workflow variables.
  • Transition: This will display a selection of all available transitions based on the route selected as part of the process flow.
    This field will be displayed if Transition is selected in the Type field.
  • Workflow Variable: Will display a selection of all available workflow variables based on the current Process.
    This field will be displayed if Workflow Variable is selected in the Type field.
• Value: Input field for specifying transition or workflow variable values.
  This field will be displayed if Workflow Variable is selected in the Type field.
• Delete Action: Removes a defined action.
  

Download sample app