[jboss-jira] [JBoss JIRA] (DROOLS-1815) [Guided Decision Table] Non intuitive binding of fields without operators
Michael Anstis (JIRA)
issues at jboss.org
Fri Oct 27 04:35:10 EDT 2017
[ https://issues.jboss.org/browse/DROOLS-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Anstis moved GUVNOR-2832 to DROOLS-1815:
------------------------------------------------
Project: Drools (was: Guvnor)
Key: DROOLS-1815 (was: GUVNOR-2832)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: Guided Decision Table Editor
(was: Guided Decision Table)
Affects Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta5)
> [Guided Decision Table] Non intuitive binding of fields without operators
> -------------------------------------------------------------------------
>
> Key: DROOLS-1815
> URL: https://issues.jboss.org/browse/DROOLS-1815
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Affects Versions: 7.0.0.Beta5
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: dtable_testday_preparation, qe-test-day, reported-by-qe
>
> There are situations when user wants to bind to variable field of a fact and he doesn't want to restrict the value of the field. Lets say that user wants to bind score of a player like this:
> {code:java}
> $p : Player( $s : score )
> {code}
> This is completely possible with BRL Condition fragment. However if this rule is defined via Simple Condition column then it is a little bit non intuitive.
> During Simple Condition definition user has to select Operator as *no operator*. But then in the table, to generate rule for this column there have to be filled some value in the corresponding cell, what is quite non intuitive. There should be just check box for cases, when we don't compare field with any value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list