Conditions

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.

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

Available conditions :

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

• Product category - checks if the product is assigned to at least one category.

• Product completness - checks the content completeness in a specific language.

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.

• Product completness set - checks if the required attributes defined in the assigned completeness set are filled within a specific template section.

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.

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

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

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 -> Language.