| Table of Contents | ||
|---|---|---|
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
The Condition node is available in GlobalCapture and GlobalAction. |
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.
Start by a Condition Node from the Nodes Pane to the Design Canvas.
Condition Node Settings
Title
A Title is required. A good Title is important because it shows up in the process history and can help with troubleshooting workflow errors. Your Title should be concise and informative.
Description
Provide a Description of your condition. Detail the purpose of the condition, the operations, etc. Description are helpful when revisiting the workflow in the future and by those who did not design the workflow but need to make modifications. The Description will appear in the process history.
Basic Settings
Basic settings allow for simple boolean logic. The condition is evaluated as True or False and follows the appropriate path.
Select a Type from the drop down list.
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.
Configure a Basic Condition Using a Process Property
Select the Property from the Process Property drop down list.
Select the appropriate operator from the Condition drop down list. The conditions will vary based on the process property selected.
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.
Click Save.
| Info |
|---|
To enter a variable into the Value field:
|
Process Field
Process Fields are user created fields in GlobalCapture and GlobalSearch 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, etc.
Configure a Basic Condition Using a Process Field
Select the Process Field from the Based on Process Field drop down list. This list will contain all Process Fields listed in the Process Field pane.
Select the appropriate operator from the Condition drop down list. The conditions will vary based on the process property selected.
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.
| Info |
|---|
To enter a variable into the Value field:
|
Field (GlobalAction Only)
Fields are only available in GlobalAction and are a list of fields in the GlobalSearch database to which the GlobalAction workflow is associated.
Configure a Basic Condition Using a Field
Select the Field from the Based on Field drop down list. This list will contain all Fields in the GlobalSearch database.
Select the appropriate operator from the Condition drop down list. The conditions will vary based on the process property selected.
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.
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.
| Note |
|---|
The number of results returned by the search and any data associated with those results is not considered. Using a Batch Search simply checks to see if any documents are returned. |
Configure a Basic Condition Using a Batch Search
Select a Search from the Based on Search drop down list. This is a list of available GlobalCapture Searches to which you are secured.
Any Search Prompts that are available in the search will appear below the Based on Search field. Enter data to narrow down the results that will be returned.
| Info |
|---|
Leaving the Search Prompts empty will return all documents for that search. |
Click Save.
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.
| Note |
|---|
The number of results returned by the search and any data associated with those results is not considered. Using a Search simply checks to see if any documents are returned. |
Configure a Basic Condition Using a Search
Select a Search from the Based on Search drop down list. This is a list of available GlobalSearch Searches to which you are secured.
Any Search Prompts that are available in the search will appear below the Based on Search field. Enter data to narrow down the results that will be returned.
| Info |
|---|
Leaving the Search Prompts empty will return all documents for that search. |
Click Save.
Basic Condition Examples
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.
| Note |
|---|
Links are evaluated from top to bottom in the order specified. Links can be re-ordered via drag and drop after more that one link is created. |
Conditional Links Pane
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.
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.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.
Edit (
) - Opens the Conditional Link Builder to make changes to an existing condition.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.Delete (
) - Deletes the Conditional Link. 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
Advanced Condition Examples
Conditions
Conditions are operators that compare the selected field or property to a value. The list of conditions will vary depending on the field type (Character, Numeric, Decimal, Date) of the process property.
Equals
Greater than or Equal To
Less than or Equal To
Does Not Equal
Is Empty
Is Not Empty
Regex Match
