Logical Branch Operations in Workflow 2

🎯 Objective

Learn how to configure and use logical operations in netLex's Workflow 2. This article explains how to automatically and parallelly route your documents, ensuring that each process follows the correct path based on its properties.

This article contains the following sections:

• How Branching Works
• Types of Logical Operations
• Special Conditions
• The Exception Branch
• Best Practices and Maintenance
   

👉 How Branching Works

Logical branches allow you to create flexible flows by defining conditions that the system automatically evaluates when the document reaches a specific point. 

In Workflow 2, a key feature is parallel execution: the document will proceed through all branches whose conditions are met simultaneously. If the conditions of two or more branches are true, the workflow will start the steps of all those paths at the same time.
 

🛠️ Types of Logical Operations

The available operations vary according to the type of selected property:

1. List and Status

For selection properties, the system allows comparisons with pre-configured values. The logic's integrity is ensured even if the option name is changed in Management.

• Is equal to: The property value in the document must be unique and exactly the selected one.
• Is one of: Met if the value is any of the chosen options, even in multi-option fields.
• Is none of: Met if the value is different from all options. This condition is also true if the property is empty.

2. Text

Evaluate the content written in free text fields:

• Text contains: Checks if the specified snippet is part of the content.
• Text does not contain: Checks if the snippet is not part of the content. Important: this condition is false if the property is empty.

3. Date and Number

Allow defining quantitative and chronological ranges:

• Operations such as Greater than, Less than, Equal, or Different.
• Note: The different condition results in false if the property is empty.

4. Filled Property Check

• Is set: True if the property is filled.
• Is not set: True if the property is empty or does not exist.
  
  Any comparison with properties not found in the document results in the condition not being met (false result), including is none of (list/status), text does not contain (text), and different (date/number). The property must exist in the document for comparisons. Only the is not set operation is considered met (true result) for non-existent properties.

Tip: Use this comparison to prevent undefined properties from leading the flow to undesired paths.

🌟 Special Conditions

• "Always" Condition: Used for mandatory paths that do not depend on variables.
  
  
   
• Document Changed: Evaluates if the document has been edited after creation, ideal for directing to legal validation. For details on how this rule works, access: Conditions with Document Changed in Workflow 2.
  
  

🛡️ The Exception Branch

Every branching must mandatorily have an Exception Branch. It functions as a safety route: the document will follow it only if none of the other logical conditions are met. This ensures that the workflow never becomes "stuck." The administrator can create a new exclusive branch for the exception or use an existing branch.

💡 Best Practices and Maintenance

• Naming: Name branches clearly. These names are internal and essential for organization by other administrators.
• Importing between environments: When moving workflows (e.g., from Staging to Production), netLex identifies properties by ID. If an option is not found, the system will display a "Not found" alert.