]
Michael Anstis moved GUVNOR-1954 to DROOLS-1851:
------------------------------------------------
Project: Drools (was: Guvnor)
Key: DROOLS-1851 (was: GUVNOR-1954)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: Guided Decision Table Editor
(was: Guided Decision Table)
Affects Version/s: 5.5.0.Final
(was: drools-5.4.0.Final)
Guided Decision table: Multiple 'otherwise' for sub-group
support
-----------------------------------------------------------------
Key: DROOLS-1851
URL:
https://issues.jboss.org/browse/DROOLS-1851
Project: Drools
Issue Type: Feature Request
Components: Guided Decision Table Editor
Affects Versions: 5.5.0.Final
Reporter: Toshiya Kobayashi
Assignee: Michael Anstis
Attachments: otherwise.png, repository_export_otherwise.xml
If you set 'otherwise' for a cell, it equals to the rest of all defined values in
the column. The request is accepting multiple 'otherwise' and it equals to the
rest of all defined values in the sub-group. What is 'sub-group'? The intuitive
approach is that Guvnor recognizes 'sub-group' from left to right. So if you have
the same value cells (= so you can merge) in the left next column, it is the one sub-group
for the 'otherwise'. It might be easier to understand with the image (See attached
otherwise.png).
Words from a customer:
=====
1. I think the simplest approach to defining sub-groups will be to evaluate conditions
from Left to right. So for the example I have provided Flight# will be the first
sub-group, Airline the next sub-group. However if a different approach can be provided to
create the sub-groups that would be acceptable as long as it is easy to create and
visualize the sub-groups, specially for the Business Users.
2. I think the sub-groups could be the default behavior. When multiple otherwise would be
supported for a column an approach would be needed to understand the sub-group to which
one otherwise applies, and the sub-group to which the 2nd otherwise applies within the
same column. However from a backward compatibility perspective a toggle could be created
(since currently otherwise can be on any row in the column).
=====
I think the key part is if we can implement it without newly introduced meta-data. If you
think we need to be more specific, please let me know.