I am really excited about our new product ‘Rule Designer’, especially version 1.0.26. This is a truly interactive development environment that makes rule design and development much easier. There is no need to worry about dealing with rule languages any more. Our rule designer allows rules to be designed and implemented using visual elements simply by dragging and dropping different commands from a tool box into a rule document.
The story of our rule designer does not finish here, but before continuing on the business rule designer let me remind you that our business rule engine is fully extensible on different levels: Language level, rule repository and location, rule execution, etc.
This means that by using our business rule engine you are not limited to using its built-in commands. You can extend its commands and reuse them in the same way you use built-in commands to extend the rule behavior.
One of the benefits of our business rule designer is the ability for it to be extended based on your own customized business rule commands. That means when you define a new command in the rule engine, now is the time to extend the visual aspect of the new command and let designer represent a visual element in the rule document for your new custom rule command.
To do that there are three simple steps:
- Create your own builder strategy
- Create your own command builder
- Create your own Toolbox initializer
And what will happen when you load a rule document that has your own custom rule command is as follows:
- Command will appear in the toolbox in a group
- PropertyWindow will display the properties of commands
In the next post I will show you the code and describe it step by step.