Some important things that are lacking with the PaperUi created rules that I’ve found so far that IMHO makes it not yet ready for general use include:
- Cron time based triggers, in particular triggers that occur more than once a day
-Member of triggers. There is a works around for Member of changed and Member of updated (though this is currently broken) but no way to do Member of received command.
global variables or any way to create a variable that can be used across multiple rules or multiple runs of the same rule. The renders the bulk of the use case for Timers impossible. Expire binding could be a work around but it’s only a 1.x version binding and one cannot set custom amounts of time for the timer.
there are a ton of improvements that need to be made to the UI including: add all enum type commands to the drop down lists, make it more clear that any arbitrary value can be entered for state fields, sizing problem on the script entry dialog when first creating a new script action or but only if script, and syntax highlighting and checking in the script entry (off the top of my head).
None of these are problems with the rule engine itself since JSR223 rules can do all of these. But the PaperUi doesn’t let me do any of these. And all of theses are things those transitioning from Rules DSL will expect.
I’ve not yet created issues for these pending my completion of that initial set of users guides. The JSR223 file are providing a lot of help too, helping me figure out some things and steering me right when I go wrong.
But having spent the last few weeks experimenting with paper UI created rules I can say it can be a pretty painful process. I can see the potential and even if the engine itself is stable, usability is not.