Re: [rules-users] How to allow non-programmers/non-Drools programmers to define rules

DSL is essentially just templates which map phrases (which may look a bit like natural language) to DRL. DSLR is the actual rules and looks a bit like normal DRL, except that inside the ‘when’ and ‘then’ sections you tend to find phrases based on the DSL. This is the bit which could possibly be written by a fairly technical business user. However it’s worth pointing out that it’s pretty easy to make a mess of it. To help avoid problems, if you have Guvnor/Workbench, then the guided editor supports building rules based on DSL phrases. This means that users are forced to pick valid phrases and use text boxes and (assuming you set them up properly) drop-down menus to populate many of the variables. I have had operations and legal teams using this quite comfortably, given a little bit of training and some decent documentation. As an alternative, Paul King has done a number of presentations on using Groovy DSLs to build business rules. By using Groovy DSLs and an IDE, you get context sensitive help to generate the rules. It makes it easier to build up business-readable rules, although it’s probably not a solution for business users to write the rules themselves. You could take a look at his slides here: http://www.slideshare.net/paulk_asert/groovy-rules But as Rich mentions, if you can express the rules in a table structure, then spreadsheets and (in Guvnor/Workbench) web decision tables are the way to go where possible. Steve On 21 Mar 2014, at 10:11, ankit3j <ankit3j(a)gmail.com&gt; wrote: