At Serverboards 17.04 we had simple rules that just executed one action when there was a state change. But was not enough.
For once, it relied on a lot of login on the trigger itself, as it had to keep track of the status changes, but that was not enough for complex situations where you want more information than a status change. How many days until expiration? For which domain? These details could not be delivered to the actions to for example properly fill the notifications or issues.
With the new rules v2 we plan to have complex pipelines, where it is possible to trigger the pipeline (similar as before) but then run some login, as if contiionals, and perform more than one action. Also pass along information about the status. For the previous example that would be an object with the name of the service, how many days until expiration, and what expiration.
We have screenshots too!
There is code for automatic translation of old rules, and support rules as per Semantic Versioning until 18.04.
I will keep you informed as we progress on this! Also leave your comments and remarks!