Context

The configuration of command change is in JCR and is used to "concatenate atomic actions"

e.g.:

When an action in the UI is triggered can lead to several "sub-actions"

Publishing is publishing the content from one environment to another

In addition an notification is sent to the user "The Content has been published)

Currently in Magnolia 6.2. relies on this functionality to launch the notification to the webhook service

Problem

In Magnolia 6.2 is possible because still relies in JCR but in Magnolia SaaS (6.3) is not possible because we don't have JCR to store such a configuration

We would need a different mechanism to "concatenate the granular actions" 

Requirement

• Find a mechanism to group several "atomic actions" into a bigger one
• Actions might need to respect a given order of execution
• This configuration needs to be out of JCR