Skip to main content

Automations: Can I create conditions combining different modules?

Discover how to create automation conditions by combining different modules and entities in Sage Sales Management, allowing you to define more precise and flexible rules.

Training avatar
Written by Training
Updated this week

Can I create conditions combining different modules?

You can narrow down an automation using conditions from the same module. For example:

  • If a text field contains or does not contain a specific text, or if it is filled in or empty.

  • If a picklist field contains or does not contain certain options, or if it is filled in or empty.

  • If a numeric field is equal to, different from, greater than or lower than a specific value, or if it is filled in or empty.

  • If a date is equal to or different from today, yesterday, tomorrow, and so on.


You can also narrow down an automation using conditions that combine different entities, for example by comparing fields from different modules, as long as the relationship is upward.

Example 1

This condition checks whether the Postcode of the newly created opportunity is different from the Postcode of the main account linked to the opportunity.


Example 2

This condition checks whether the Expected close date of the newly created opportunity is equal to a custom date fieldon the main account linked to the opportunity.


You can also create advanced numeric conditions by comparing fields across different related entities.

For example, you can check whether a numeric field is lower than, greater than or equal to the value of another field belonging to a related entity.

In addition, it is possible to define conditions where a value must fall within a range, whose limits are dynamically calculated by combining fields from different entities using mathematical operations.

Advanced example

In the following example, the condition checks whether the Value of the newly created opportunity falls within a range defined by two different calculations:

  • Initial value: the sum of two custom fields, one from the main account and one from the intermediary accountlinked to the opportunity.

  • Final value: the result of multiplying a custom field from the main account by a field from the opportunity itself.

In this way, the automation checks whether the opportunity value falls between both dynamically calculated limits, taking into account data coming from several related entities.

Did this answer your question?