FlexRule version 2.0.0 has been released.

We have learnt a lot from version 1.X of product and we tried to apply most of our experiences from the past in this new version. This would be a starting of new generation of rule engines. There are big changes have happened in this version. First of all an architectural refactoring has happened in order to make engine more scalable. And second there are new engines and command in this release.

To highlight changes I can categories them in two sections:

New Engines and Commands:

  1. Validation Engine to validate a hierarchical structure
  2. Database read/select functionality
  3. Notification mechanism for all engines: Procedural, Flow, Validation
  4. Evaluation permission validation

Fixes and enhancements:

  1. Rule as a rule feeder for procedural tester
  2. Bug fix: CallProc, Var, Define
  3. NewArray command for procedural engine
  4. Variables name can be only alphabetic, numeric and _
  5. Some samples for new engines and commands

Please note it has backward compatibility with existing rules. However if you have some custom commands they require some changes because of the new design of framework.

Validation Engine to validate a hierarchical structure

This is a new engine to allows a hierarchical structure be validated dynamically. It can be used as a stand alone engine and it can be integrated into the existing engines: Procedural and Flow.

Also, the logic of this type can be divided logically into different sections and be reused inside the validation rule itself. There engine at the end of validation would have all the notifications related for validation failures.

Database read/select functionality

This set of commands allows rule read data from different databases: MsSql, ODBC, Oracle and Access. They should be used in the procedural engine. If these functions are required in other engines they can be integrated into Flow using an custom activity.

Notification mechanism

There is not a built-in mechanisms to capture condition failure during rule execution. And after execution of rules has been finished, the notification is available through the engine itself and can be collected in the application.

Evaluation permission validation

Application sensitive’s data and functions can be protected from rules execution now. So no malicious rule can be coded to retrieve sensitive data from your backend system.

To find more information please check the technical document.

Last updated September 22nd, 2020 at 11:38 am, Published June 21st, 2012 at 11:38 am