[jboss-jira] [JBoss JIRA] Updated: (JBRULES-1194) Extending data enumerations to DSLs in guided rule editor

[Mark Proctor (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBRULES-1194?page=all ]

Mark Proctor updated JBRULES-1194:
----------------------------------

    Fix Version/s: FUTURE

> Extending data enumerations to DSLs in guided rule editor
> ---------------------------------------------------------
>
>                 Key: JBRULES-1194
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1194
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> Would it be possible to extend the data enumeration functionality in the BRMS version 4.0.1 to work with domain specific language (DSL) sentences in the guided editor?
> At present the data enumerations work with simple data fields only (JIRA  JBRULES-1090). However, I think the combination of defining rules with a DSL and being able to provide a drop-down list of choices for parameters in a DSL sentence would provide a very business friendly front end for non-technical business users, especially in scenario in which business users want to be able to tweak parameters in existing rules rather than define rules themselves.
> The kind of thing I'm thinking of can be illustrated with a DSL like the following:
> [condition][]There is a Customer=c: Customer()
> [condition][]- who is {value} value=value == "{value}"
> Suppose you create the following "when" condition, where [ ] represents the text box the guided editor creates to enter a value for the {value} placeholder:
>  
> There is a Customer
> - who is [ ] value
>  
> I'd like to be able to specify a set of values for the [ ] drop down list. For example, the possible "values" could be one of the following ['High','Medium','Low'].
> Syntactically this might be done in some modified from of DSL definition. For example, borrowing from the existing data enumeration syntax, it might look something like the following:
>  
> [condition][]- who is {value: ['High','Medium','Low']} value=value == "{value}"
> The above modification would also not tie the data enumeration to an object attribute. For example, the DSL may define a consequence that is not related to an object:
> [consequence][] Report the status as {status} =System.out.println("The status is {status}");  
> Here we would like a drop down list for the {status} placeholder to be "Good" or "Bad" (i.e. the literal is a not an object attribute value).
> Thanks
> Shahad

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira