RulesEngine | Json based Rules Engine with extensive Dynamic expression | Rule Engine library

The expectation for the RulesEngine(string[], ILogger, ReSettings) constructor is that each element of the string array is a complete JSON object. In your case, you've provided just a single line per array element.

Given that your text file already contains a collection of rules, you should deserialize it yourself, and pass the deserialized collection into the constructor accepting a WorkflowRules[]:

That looks like something I'd do by:

Summarising, no and yes!

To get to how, you have to understand that as long as a variable is present as a Fact or somehow it is present in MVEL context, it can be resolved.

Here's detailed answers-

Use rule name, description inside actions?

No. You can't use Rule's name and description inside an Action. To use external variables inside rules, you'll have to add them as facts. If you want that ability, use drools which is much more feature rich and heavy framework.

Use a variable under actions?

This you can do, however not the way you have. def has a special meaning inside MVEL. So to use variables, you can do either of these things-

1. Define variable as separate action item:

As by documentation, Phoenix.PubSub.subscribe/3 has the following spec:

First of all, consider whether you actually need all this flexibility. Code.eval_string runs the code without any checks or restrictions whatsoever, so this potentially opens a security hole in the code. I would do something like this instead: