I know it will be a difficult development, but an advanced workflow structure plugin can bring the product to a great point. What I am talking about is actually a structure like Zapier, but it can be matched with the data inside… There is an interface structure etc. in the Elsa-Workflow project, but it is very open-ended how creative development can be done with Squidex. I wanted to add a note in case something comes to mind for you.
I have actually thought many times about that. In my opinion most existing workflow solutions are too complicated for what I would like to have in Squidex and building something from scratch is super complex. I am also not sure how much people would use it, because a simple webhook is much easier in most cases.
The webhook side definitely works in many areas. But when it comes to developing complex applications on Squidex, a lot of coding is actually required. My goal with my recommendations is to bring the product to a more low-code structure. This is somewhat related to where you want to go… If you say you want to develop, I can share my recommendations and experience on what can be done.
I was working on the feature from time to time (as it was often intercepted by other stuff).
But finally I was able to start with the UI part:
Hi,
I use Rules in my app to trigger Algolia index operations whenever something gets published, deleted etc
Im wondering if there are any breaking changes in 7.19 because this sounds like a huge rework of the entire Rules module.
Thanks
The only breaking change is that the events are not taken over. So you will nto see old records in the logs.
Okay, that’s fine; not seeing old records in the logs 
Thanks, Sebastian.