Use the Condition Node to build conditional decision making into a workflow process.  Decisions can be based upon process data, fields, and searches. Each condition node supports simple boolean logic or complex logic that allows for multiple outputs.

Open

Condition Node

Start by a Condition Node from the Nodes Pane to the Design Canvas.

Open

Drag a Condition Node to the Design Canvas

Condition Node Settings

Types of Rules

Process Property - Process properties are properties collected by the system about every document moving through a workflow. These properties represent information about the workflow such as Page Count, Batch ID, Original File Name, etc. These properties can be access and used for conditional routing.

Process Field - Process Fields are user created fields and table fields in GlobalCapture that can be used to store data. These fields can be used in a wide variety of ways such as: storing data extracted from the document, keeping a count of the number of loops executed, storing workflow tracking information, table data, etc.

Field (GlobalAction Only) - Fields are only available in GlobalAction and are a list of fields, including table fields, in the GlobalSearch database to which the GlobalAction workflow is associated.

Batch Search - Batch Searches are GlobalCapture Searches. When using a Batch Search in your Basic Condition node configuration, if the search returns results, the document moving through the workflow will follow the True path. If the Batch Search returns no results, it will follow the false path.

Search (GlobalAction Only) - Searches are GlobalSearch Searches. When using a Search in your Basic Condition node configuration, if the search returns results, the document moving through the workflow will follow the True path. If the Search returns no results, it will follow the false path.

Basic Settings

Basic settings allow for simple boolean logic. The condition is evaluated as True or False and follows the appropriate path.

Configure a Basic Condition Using a Process Property

4. Click Save.

Configure a Basic Condition Using a Process Field

Configure a Basic Condition Using a Field

Configure a Basic Condition Using a Batch Search

1. Select a Search from the Based on Search drop down list. This is a list of available GlobalCapture Searches to which you are secured.

Configure a Basic Condition Using a Search

1. Select a Search from the Based on Search drop down list. This is a list of available GlobalSearch Searches to which you are secured.

Basic Condition Table Data

Conditions can be applied to Table Fields, allowing you to make routing decisions based on individual line items.  Apart from Contains All, Empty, and Is Not Empty, all other Table Field conditions are evaluated on a per row basis.

Empty/Is Not Empty

Empty and Is Not Empty evaluate the entire column.  For Empty, ALL cells in the column must be empty.  For Not Empty, ALL cells of the column must contain data.  This is only applied to the selected column, whether other columns in the table contain data or not does not impact the evaluation.

Contains All

Contains All is a condition that only applies to Table Fields.  When selected, you are prompted to select a Target Table Field and a column within the Target Table Field for the value.  This will compare the values in the Target Table Field column to the values in the Based On Table Field column. 

If all the values in the Target Table Field column are present in the Based On Table Field column, the condition evaluates as True.  If anything exists in the Target Table Field column that does not exist in the Based On Table Field column, it will evaluate as False.  If the Based On Table Field column contains values that are NOT in the Target Table Field column, it will evaluate as True.

Basic Condition Examples

A basic condition is useful when there are only 2 possible outcomes, True or False, and a single parameter to check against.

• Checking if an Amount field exceeds a specific value.

• Determining if a field contains a value.

• Checking for an expiration date or a past due date.

Advanced Settings

Advanced settings allows you to configure the Condition node to accommodate more than just 2 outputs (True and False). While conditions are still evaluated as True or False, multiple conditions can be configured to create a path for the document to follow when the condition is evaluated as True. A single False path (No Conditions Met) is automatically created to be followed when no conditions evaluate as True.

When the Advanced tab is selected any available links are displayed. From here, you can rearrange the order of the links, create new links, or edit, copy, and delete links.

Conditional Links Pane

1. Priority - Indicates the order in which the conditions will be evaluated. Conditions are always evaluated from top to bottom in the Conditional Links list. The Priority can be changed by moving the link up or down the list using Reorder or by changing the Priority in the Conditional Link Builder.

2. Reorder ( ) - When multiple conditions are available, Reorder the priorities of the links by dragging the Reorder icon for the selected condition up or down the Conditional Links list.

3. Title - The Title of your path. This is what is displayed in your workflow when making the connection to the next node. Ensure your title is clear to improve ease of workflow construction and maintenance.

4. Edit ( ) - Opens the Conditional Link Builder to make changes to an existing condition.

5. Copy ( ) - Duplicates the existing condition. The duplicated conditional will open in the link builder and default to the bottom of the list unless the priority is changed.

6. Delete ( ) - Deletes the Conditional Link.

7. Add Conditional Link ( ) - Creates a new Conditional Link. The new link will open in the link builder and default to the bottom of the list unless the priority is changed.

When a new link is created, or an existing link is copied or edited, the Condition Link Builder appears.

Conditional Link Builder

Title - The Title of your path. This is what is displayed in your workflow when making the connection to the next node. Ensure your title is clear to improve ease of workflow construction and maintenance.

Understanding Rules and Groups

Each condition link is constructed of Rules. Rules can be combined into Groups to construct more advanced boolean conditions. Rules can be constructed of any Type and joined using AND and OR logic. The rules within each group must all have the same operator but subgroups can have a different operator then the parent.

Each Rule and Group are joined by that operator selected for the Group.

Rule Color Codes

When creating Advanced Conditions, each rule in the condition is given a color code. This color code corresponds to the Type of value being used.

• Gray - Process Property

• Blue - Process Field

• Red - Field (GlobalAction Only)

• Yellow - Batch Search

• Green - Search (GlobalAction Only)

Adding a Rule to the Rule Pane

1. From the Condition Link Builder, select the desired operator ( ) and click the add rule ( ) button.

2. Select the Rule type.

Process Property, Process Field, and Fields

1. For Properties and Fields, select a Property or Field from the list.

2. Select the appropriate operator from the Condition drop down list. The conditions will vary based on the process property selected.

3. Enter the Value to compare the select property to. This value can be another Process Property, a Process Field, a Field, or a hardcoded value. For conditions where a Value is not needed, such as Is Empty, the Value input will disappear.

4. Add additional Rules and Groups or click Save if finished.

Batch Searches and Searches

1. For Searches, select a search.

2. Select the Condition.

   1. Returns Results - Will evaluate as True if the search returns any results.

   2. Returns Nothing - Will evaluate as True if the search returns no results.

3. To modify the search prompts, click the Search icon ( ) to display the list of search prompts. Configure the search prompts to return the desired results.

4. Add additional Rules and Groups or click Save if finished.

Adding a Group

1. To add a group, click the Add Group ( ) button. The Group is added to the bottom of the rule list for the selected group but can easily be moved within and outside of the group using the Priority icon ( ).

2. Select the desired operator ( ) and click the add rule ( ) button. Continue to add rules as needed.

3. To add another group a the Primary Group, click the Add Group ( ) button at the top of the Primary Group container. To add another group into another group, click the Add Group ( ) button in the Group container.

Understanding Table Fields Rules and Groups

Conditions can be applied to Table Fields, allowing you to make routing decisions based on individual line items.  Apart from Contains All, all other Table Field conditions are evaluated on a per row basis. 

Empty and Is Not Empty operators with Tables

The Empty and Is Not Empty operators will behave differently depending on the configuration of the Condition. 

If only a Single Column of the table is part of the condition, Empty and Is Not Empty will evaluate the entire column.  For Empty, ALL cells in the column must be empty.  For Is Not Empty, ALL cells of the column must contain data.  This is only applied to the selected column, whether other columns in the table contain data or not does not impact the evaluation.

Fender Invoice Data

If Multiple Columns of the table are part of the condition, the Empty and Is Not Empty conditions will be evaluated based on the cell within the row.

Contains All

Contains All is a condition that only applies to Table Fields.  When selected, you are prompted to select a Target Table Field and a column within the Target Table Field for the value.  This will compare the values in the Target Table Field column to the values in the Based On Table Field column. 

If all the values in the Target Table Field column are present in the Based On Table Field column, the condition evaluates as True.  If anything exists in the Target Table Field column that does not exist in the Based On Table Field column, it will evaluate as False.  If the Based On Table Field column contains values that are NOT in the Target Table Field column, it will evaluate as True.

Advanced Condition Examples

Advanced Conditions are useful when more than 2 possible outcomes are needed or when more complex decision making is needed.

• Routing to different departments - Route a document to any one of 5 departments and have a process to handle if no department is selected.

• Checking multiple conditions - Check to see if an invoice for a specific department exceeds a specific amount. Each department can have different thresholds or multiple thresholds for routing.

Conditions