> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/workflow/information/designer/conditions.md).

# Conditions

Choose the conditions a product must meet before a workflow transition can happen, on the transition's Conditions tab in the Designer.

This tab allows you to select conditions that need to be met before a product can make the transition. These conditions come from a predefined list.

If you add more than one condition, they will be connected with the AND logical operator, which means all conditions present must be met for a product to make the transition. No other operators are currently possible.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2Fqz0UO6uqFylPGKpWN6mx%2Fa27c4be41f03.png?alt=media&amp;token=c7098fbb-f2cc-451d-92f0-0b7ad6baaf66" alt=""><figcaption></figcaption></figure>

You can choose from the 6 conditions or leave the transition without any of them.

To add a condition, drag it from the ***Conditions*** list on the left and drop it in the area marked ***Drag & drop the item here***. Then click on ***Save changes***. If you need more space for conditions, click on ***Add 10 rows***.

Available conditions :

* **Attribute has value** - checks if the specified attribute contains any value.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FPbUH5UU3PQFBtFOUkXlh%2Fb982ad099057.png?alt=media&amp;token=3c6f339b-90c4-4cd8-8636-c34a7b6241c6" alt=""><figcaption></figcaption></figure>

* **Product category** - checks if the product is assigned to at least one category (***belongs***) or to none (***does not belongs***), as chosen in ***Operator***.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FG1Cf5sfq0n033URyHkh6%2F10985f3f362e.png?alt=media&amp;token=1d79acbb-7eae-4a6d-bf38-47177dc1e610" alt=""><figcaption></figcaption></figure>

* **Product completeness** - checks if the product content is complete (***is complete***) or not (***is not complete***); each language is checked on its own.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2F9DDl1bQwmYRfh4tOZ80E%2F2431ab414caf.png?alt=media&amp;token=3c6cddec-d126-4ef7-ab7d-c5b2454074f0" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
During product work and status changes, setting this condition means that each language will be treated separately.

**Example:**\
\
In the system, there are two active languages — English and Italian — assigned to the same workflow.\
In this workflow, at the final stage, there are two statuses defined: **approved → published**.\
The transition condition is only one - **product completeness**.

The product **SKU\_01** in English has already reached full completeness (100% of required attributes are filled) – the status can be changed to **published**.\
\
The same product **SKU\_01** in Italian has reached only 80% completeness – for the Italian version, the status cannot be changed to **published**, because the completeness condition for the product in this language has not been met.
{% endhint %}

* **Product completeness set** - checks if the required attributes defined in the assigned completeness set are filled within a specific template section. Choose the set in ***Completeness set name*** and the state in ***Completeness***: ***is completed***, ***is not completed*** or ***is completed or not applicable***.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FPZQYKJcRZmUB6UKXyWRI%2F19eb11c16e71.png?alt=media&amp;token=7cd0b65d-fd68-4b39-bc59-3a89a7ff546b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When configuring the ‘Product Completeness Set’ condition, you have the option to select

***is completed or not applicable***. By choosing this option, you ensure that the transition will be available under two conditions:

1. If the specific completeness set is present on the product template and it is 100% completed.
2. If the completeness set is **not** present on the product template, indicating that the product is still suitable for the transition.
   {% endhint %}

* **User** - allows defining which user(s) can change the status (more than one user can be selected from the list).

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2F5laLxwwx5wWR06nEYXIu%2F5719fc1a5132.png?alt=media&amp;token=be17f48e-aeab-4a68-8f8f-f030a9805571" alt=""><figcaption></figcaption></figure>

* **User role** - allows defining which user role(s) can change the status (more than one role can be selected from the list).

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2Fnebwwk4ehfZ8u4oHZ1wF%2F71cbfc2a0d7a.png?alt=media&amp;token=2640e25d-539e-4231-8700-53e0b12bda4f" alt=""><figcaption></figcaption></figure>

Once you have set up all the statuses and transitions between them to your needs and satisfaction, your workflow is complete, but before it becomes usable, it needs to be connected to a language. That can be done from System -> Settings -> [Languages](https://usermanual.ergonode.com/system/settings/languages).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://usermanual.ergonode.com/workflow/information/designer/conditions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
