<< Click to Display Table of Contents >> Navigation: NITRO™ Workflows > Configuring Workflows > Conditions, Placeholders & Functions > Conditions |
Conditions
Conditions allow you to restrict the execution of your workflow so that it only runs when specified data conditions are met. Conditions support the following value types for a list column:
•Literal/Custom values
•Another field value
1.Single Line of Text
Possible Values |
Example |
Column Value - Fixed value |
CCSTest |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Status|RequestStatus] |
Function |
$Strcat $formatvalue |
Query List Value - QueryListName##[ColumnDisplayName|ColumnInternalName] |
GetProblem##[Title|Title]. Note: Can not use this in workflow condition. you can use this in gateway condition. |
Sample example:
2.Person or Group
Possible Values |
Example |
Column Value |
- Pavan Kumar |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Requester|Requester] |
Function |
- parseuservalue Ex- $parseuservalue(John Smith) - usercollection |
Query List Value - QueryListName##[ColumnDisplayName|ColumnInternalName] |
GetConfiguration##[Approver|Approver]
|
|
|
3.Date Time
Possible Values |
Example |
Column Value |
01/01/2018 |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Due Date|DueDate] |
Function |
- subtract - add - calcbusinesstime - addmonths - datediffhours - datediffbusinesshours
|
Query List Value - QueryListName##[ColumnDisplayName|ColumnInternalName] |
AssetItem##[ExpiryDate|ExpiryDate] |
Placeholder |
{Today} |
4.Choice
Possible Values |
Example |
Column Value |
High |
Another Column name – |
[Priority|Priority] |
Function |
Strcat xpath
|
Query List Value - QueryListName##[ColumnDisplayName|ColumnInternalName] |
TicketItem##[Priority|Priority] |
5.Multi Choice
Possible Values |
Example |
Column Value |
Marketing;#Computers |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Priority|Priority] |
Function |
Strcat |
Query List Value |
TicketItem##[Priority|Priority] |
NOTE: It is not necessary that multiple choice values specified in the item field and condition value be in same order. As long as both contain the same set of choices, condition will evaluate to true. For instance in the condition it can be either Choice1;#Choice2 or Choice2;#Choice1.
6.Lookup
Possible Values |
Example |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Assigned Staff|AssignedStaff] |
Column Value |
Calendar |
Query List Value - [ColumnDisplayName|ColumnInternalName] |
TicketItem##[Assigned Staff|Assigned staff] |
7.Multi Lookup
Possible Values |
Example |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Text|Text] |
Column Value |
Spam;#Calendar |
Query List Value |
TicketItem##[Text|Text] |
8.Yes/No
Possible Values |
Example |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[HasAttachmentDocs|HasAttachmentDocs] |
Column Value |
- True - No |
Query List Value |
TicketItem##[SendForApproval|SendForApproval] |
9.Number or Currency
Possible Values |
Example |
Another Column name – [ColumnDisplayName|ColumnInternalName] |
[Cost|Cost] |
Column Value |
100 |
Query List Value |
PurchaseItem##[Price|Price] |
Refer this article for more detail on placeholder with expression builder: Syntax For Expressions In NITRO Workflows