Scenarios -v- Automation

breathwork

What are the principal differences between these two methods? When would I choose to use one rather than the other?

jvstratum

Hi,

Automations are single events. They have a trigger, actions and action targets. Once the Automation has been triggered, everything will be executed and the process is done. If you want to perform some actions on the outcome of another automations you will have to create a secopnd aitomation. As soon as you will have lots of these the list of Automations is growing and you don't have an overview on how the Automations are related to eachother.

This is where Scenario's come in view. You can have multiple automations in a single scenario and the whole process will be presented in a tree diagram. That way you alway have a clear overview of your process.

Screnario's are documented here: https://docs.acymailing.com/main-pages/scenario

tarhunbek

Unfortunately, the new service also does not detect data changes on the fly.

If we set user_modification as a trigger, and the value of some field as an execution condition, then the action will be executed for the old value of this field, before saving the changes.

Let's say the user changes the data in the profile, but the action does not occur. It is enough to save the profile again, without changing the data, then the action will be executed.

This is not logical, the action should be executed based on the new data. What is user_modification for then?

jvstratum

tarhunbek

Hi,

You would need to comntact our developers about this, they do not activly monitor this forum. In order to best assist you with your query, I kindly request that you submit a support ticket through our website at https://www.acymailing.com/support/. This will enable our team to efficiently and effectively provide you with the assistance you need.