Michael Anstis commented on JBRULES-821:
(1) I think Steve's interpretation is different to mine. I was thinking that the use
of "from" in the GUI allows for the LHS to select against a dynamic list (as it
would if you'd written the DRL); whereas I think Steve is wanting the rule author to
select from a descriptive set of options that relate to shorter codes used within the
object model (in addition to his example; choices "Tea, no sugar", "White
coffee, no sugar" and "White coffee, with sugar" might map to codes
"TNS", "WCNS" and "WCWS"). Or I've misunderstood too!
(2) In response to Michael N's comment - I saw the JBRMS as a tool to be used by our
customers (to the JBoss-Rules team, developers are customers; to us our customer is
normally a business representative who wants to do everything graphically). Therefore the
more function that can be achieved graphically the better. DRL is great but I wouldn't
want our customers to have to use it. Business users thrive on "tediousness"
I think my comments have muddled the original JIRA. I am happy to step down from this as
Michael N and Steve B seem to be (almost) agreeing. I think Michael N's example
"eg Person.sex = [Male, Female, Undefined]" would need to expand to
"Person.sex = [Male, M, Female, F, Undefined, U]" with the verbous shown to
users and the code used internally.
ValueList in rule model
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Michael Neale
Assigned To: Michael Neale
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira