The other day I was writing a rule using FlexRule and I thought why I should bother about the DLL files, handlers and variable types!
It should just work without defining all those noises out-of-the-box. Although, if someone has a custom command, that is another story. But why does it need to have all those definitions? Well, I started working on it and trying to find a way to get rid of unnecessary noises in the rule definition.
Take a look at the following logic picture as an example:
The good news is that I succeeded! Now, in new version, you can write like this instead:
During the creation of the the model (procedural, validation, flow, etc.), objects runtime loads the required module (handlers) automatically. Also, no type definition is required on variable definitions.
Also, after releasing this part I will need to fix the designer to preclude those when generating new templates. Designer validation has to be changed as well.
Last updated September 22nd, 2020 at 11:36 am, Published December 5th, 2012 at 11:36 am
CEO and the founder of FlexRule – He is an expert in architecture, design, and implementation of operational decisions, business rules, and process automation. Created Decision-Centric Approach, a methodology that brings People, Data, Rules, and Processes together to automate operational business decisions.
This approach is recognized by Gartner as the missing link to provide business value to organizations.