Page History
| Page properties | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
| UI Text Box | ||||
|---|---|---|---|---|
| ||||
Build individual expressions to be evaluated. Boolean conditions use all the features made available by the powerful expression parser. You add as many conditions to a rule as needed. The boolean condition will either return Read more about boolean or logical expressions. |
Boolean condition configuration
Below you will find a detailed description of each parameter needed to configure the condition.
Expression*
Enter a logical expression that will be checked. Field codes and parser expressions can be entered as well.
| UI Text Box | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
A very common example would be a simple field value check:
followed by an action: For example: Add comment Add comment "Please start work" Adding additional conditions checking for other statuses and combining them with different actions is a common example of a nested condition rule. |
Additional options
| UI Expand | ||
|---|---|---|
| ||
If the condition is fulfilled (returns |
| UI Expand | ||
|---|---|---|
| ||
When selected, the condition's logic will be inverted.
|
Use cases
| Page properties report | ||||||
|---|---|---|---|---|---|---|
|
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
