Conditions
Overview
Conditions allow you to specify additional prerequisite requirements for Triggers and some Transitions.
They are a set of optional parameters that can be added to the macros (listed below) to impose additional limits on when the macro is active.
In addition, due to support for Value References, you can even create custom conditions by comparing metadata values.
Basic example
{workflow:name=Conditions}
{state:Editing|approved=Done|rejected=Editing}
{approval:Review|group=confluence-administrators|assignable=true}
{state}
{state:Done|final=true|updated=Editing}
{state}
{workflow}
In the example above, only a user who is a member of the confluence-administrators group can review the content.
Compatible Macros
If a macro has a parameter with the same name as a condition, the parameter as defined in the macro takes precedence. For example, |
Conditions
Condition | Value | Notes | Ver |
---|---|---|---|
A specific value. This must be a valid datatype for the value reference.
| Does the value of a value reference match the specified value? For example, Conditions using value references can also be set when using a third-party app: |
| |
If used in a trigger macro that's listening for the | |||
One invalid parameter in a list of users in a condition disables the transition for the other listed users. The non-existent parameter value is a blocker for an approval or a state-selection transition. | |||
| A comma-separated list of group names
| Is the current user a member of one or more of the specified groups? |
|
When applied to the approval macro, it is a parameter of the approval macro - it is not used as a condition. For example, you can prefix the list (not items in the list) with | |||
| Name of an approval | Has an |
|
When applied to an approval macro in a state with multiple | |||
| A comma-separated list of content labels. | Does the content have one or more of the labels specified? |
|
|
| Is this action only for the initial occurrence of the named state for the content?
|
|
The use of The primary use of the | |||
| Title of required ancestor page.
| Does the current page have a parent or ancestor page of the specified page title? |
|
|
| Is this page set as the space home page? Filter by labelThere are no items with the selected labels at this time. See also: How to set space home page |
|
|
| Did the content editor uncheck the "Notify watchers" checkbox (indicating a "minor change") before updating the content? The |
|
This condition can only be used in a trigger macro when listening to either the | |||
|
| Is the page an orphan (no parent page)? Filter by labelThere are no items with the selected labels at this time. |
|
| A comma-separated list of content labels. | Does the parent (or any ancestor pages) have one or more of the labels specified? |
|
|
| Has an individual reviewer undertaken an Approve/Reject decision?
This condition acts as a filter to tell the trigger to act on each individual Approve or Reject decision, rather than waiting on all reviewers to agree for the named content review. |
|
The use of | |||
|
| Does the user have the specified permission for the content? See also: Roles and Permissions |
|
† Irrespective of additional view restrictions resulting from Publishing. ‡ Additional administrator that is defined via the | |||
| A space key.
| Is the page or blog post in the space defined by the space key? The space key is usually shown in URLs or on the Space Tools → Space Overview screen. |
|
| A state name. | Is the workflow for this content currently in the named state? |
|
| A state name. | Is there an unpublished version of this content in the corresponding Draft Space? |
|
This condition requires the installation of the Comala Publishing app. | |||
|
| Has an error occurred in the action(s )of a workflow trigger?
This condition acts as a filter for the trigger and looks at whether the actions of the parent trigger for the custom event encountered any errors. |
|
The use of | |||
| Name of the page | Does the current page have the page name? This condition does not support the use of value references for its value. You can use the |
|
| A comma-separated list defines one or more users via their usernames or user groups.
| Is the current user one of the users listed? You can include One invalid parameter in a list of users in a condition disables the transition for the other listed users. The invalid user parameter value is a blocker for an approval or a state-selection transition. |
|
When applied to the approval macro, it is a parameter of the approval macro - it is not used as a condition. You can prefix the whole list (but not an item in the list) with | |||
| Comma-separated list of Value References | Does the value reference define users? This is useful when using workflow parameter macro to create editable value references – use this parameter to check that the entered values are valid user accounts. | 4.1 |
metadata reference | Reference to a metadata value (including a workflow parameter reference) | When comparing metadata (value references), a metadata reference can only be compared against one specific value or a value reference. |
|
Denotes conditions that can only be used on pages, not blog posts. † Conditions are evaluated as AND conditions, with the exception of user and group. When both conditions are used, an OR clause is applied, i.e., (user or group), and either one of those parameters is required for the condition to be true. |
| ||
Denotes a parameter in a trigger macro that acts as a filter. The use of these is unique to specific events. |
|
Negation
Conditions are compared to values. Values can optionally be negated with a !
(exclamation mark) symbol:
{...|condition=value|...} -- value must match
{...|condition=a,b,c|...} -- one or more of the values must match
{...|condition=!value|...} -- value must not match
{...|condition=!a,b,c|...} -- none of the values must match
Comparing metadata values
A metadata reference can only be compared against one specific value or a value reference.
An exception is that multiple values can be compared when using a metadata reference with the following conditions
user
group
haslabel
When comparing the metadata value against multiple values, you should also use the following format
@MetaOne@=!1|@MetaOne@=!2|@MetaOne@=!3
For example
The condition is evaluated as an OR condition.
Invalid workflow parameter for a user
One invalid parameter in a list of users in a condition disables the transition for the other listed users. The non-existent parameter acts as a blocker for other users.
Invalid workflow parameter for a user in a condition for a select transition
If a workflow parameter is used to specify a user for a state-select
transition, the transition is disabled If the user set in the parameter is invalid (deleted or non-existent).
The transition becomes active if the parameter becomes valid by adding a valid value or is deleted.
For example, if the workflow parameter @myParam@
has an invalid user value, the transition button in the workflow popup is disabled.
If the invalid workflow parameter is one of the users for the state-select
transition, the transition is disabled for the other users listed in the condition. The non-existent parameter blocks the transition.
A message displays an error in the workflow definition regarding the list of users who can undertake the transition.
Invalid workflow parameter in a condition for an approval
If a workflow parameter is used to specify a single user for an approval, the Approve and Reject buttons in the workflow popup are disabled if the user set in the parameter is invalid (deleted or non-existent).
The transition will become active if the parameter becomes valid by adding a valid value or is deleted.
The non-existent user defined in the parameter blocks the approval.
A message displays an error in the workflow definition regarding the list of users who can approve.
The approval becomes active for each defined user if the parameter becomes valid by adding a valid value or is deleted.