October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1811) [Guided Decision Table] Column Wizard usability improvements

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1811?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3429 to DROOLS-1811: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1811 (was: GUVNOR-3429) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 7.2.0.Final (was: 7.2.0.Final) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [Guided Decision Table] Column Wizard usability improvements > ------------------------------------------------------------ > > Key: DROOLS-1811 > URL: https://issues.jboss.org/browse/DROOLS-1811 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.2.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Fix For: 7.5.0.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > > On the _BRMS 7.0 - Getting Started Experience_ meeting, there were mentioned these points that could improve the column wizard: > - Placement of input fields > -- *Field binding* should be on the same page as *Field* > -- Pages like *Operator* and *Field* could be merged or at least recapitulate what was selected on previous pages of the wizard > - Input fields should be explained somehow. For newbies it is really hard to understand what is the *Calculation Type* or *Value List*. I liked concept of small _i_ in blue circle that shows hint after mouse is over this info sign. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1812) [Guided Decision Table] Edit multiple cells at once

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1812?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2926 to DROOLS-1812: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1812 (was: GUVNOR-2926) 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.Beta7 (was: 7.0.0.Beta7) > [Guided Decision Table] Edit multiple cells at once > --------------------------------------------------- > > Key: DROOLS-1812 > URL: https://issues.jboss.org/browse/DROOLS-1812 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The user of guided decision table editor is not able to edit values of multiple cells at once. > User is able to select multiple cells as belonging to same columns so belonging to different columns. For the case when the selected cells belong to the same column (the have the same data type) user should be able to edit all selected cells by one action. > Tried ways how to edit multiple cells: > * Select cells -> Menu -> Edit - there is appropriate menu item > * Select cells -> Right click to one of selected cells - invoked context menu only for one cell > * Select cells -> Double left click to one of selected cells - similar as above > * Select cells -> Hit key Enter - only the last selected is edited -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1813) Guided Decision Table Editor: Add support for sorting columns

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1813?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2483 to DROOLS-1813: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1813 (was: GUVNOR-2483) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table Editor: Add support for sorting columns > ------------------------------------------------------------- > > Key: DROOLS-1813 > URL: https://issues.jboss.org/browse/DROOLS-1813 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1814) Guided Decision Table V&V reporting - detect redundancy for rows differing only in bound vars

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1814?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2249 to DROOLS-1814: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1814 (was: GUVNOR-2249) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table V&V reporting - detect redundancy for rows differing only in bound vars > --------------------------------------------------------------------------------------------- > > Key: DROOLS-1814 > URL: https://issues.jboss.org/browse/DROOLS-1814 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe > > The following 2 rows/rules from one GDT are redundant but not detected as such. The reason is that one operates with a fact bound to variable 'p', the other binds the same fact to variable 'q'. It would be nice, if things like this were detected as well. > rule "Row 1 asd" > when > p : Person( age > 0 ) > then > p.setSth( 0 ); > end > rule "Row 2 asd" > when > q : Person( age > 0 ) > then > q.setSth( 0 ); > end -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1815) [Guided Decision Table] Non intuitive binding of fields without operators

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1815?page=com.atlassian.jira.plugi... ] 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)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1816) Guided Decision Table: for boolean values, it is not clear if the cell is not set or is set to false

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1816?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2252 to DROOLS-1816: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1816 (was: GUVNOR-2252) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table: for boolean values, it is not clear if the cell is not set or is set to false > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1816 > URL: https://issues.jboss.org/browse/DROOLS-1816 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Guilherme Carreiro > Labels: reported-by-qe > > A cell that represents a boolean field uses a simple checkbox to set the value to either true or false. Until the user first sets the value, the box is unchecked, but the value is not set. If the user checks and unchecks the box, the box looks just like at the beginning but the value is set to false. > If you want to determine if the cell value is not set yet or is set to false, you have to look into the source of the GDT. This is quite bothersome for larger tables. > Please consider some way of distinguishing these two different states in the guided dt editor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1806) [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1806?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3133 to DROOLS-1806: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1806 (was: GUVNOR-3133) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Data Model Oracle Guided Decision Table Editor (was: Data Model Oracle) (was: Guided Decision Table) Affects Version/s: 7.1.0.Beta2 (was: 7.1.0.Beta2) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-1806 > URL: https://issues.jboss.org/browse/DROOLS-1806 > Project: Drools > Issue Type: Bug > Components: Data Model Oracle, Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > If the guided decision table uses fact field that has form 'xXxxx' then the generated getters and setters are incorrect. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1807) Verification & Validation: Add three states for running the validation

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1807?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2662 to DROOLS-1807: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1807 (was: GUVNOR-2662) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Verification & Validation: Add three states for running the validation > ----------------------------------------------------------------------- > > Key: DROOLS-1807 > URL: https://issues.jboss.org/browse/DROOLS-1807 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Anton Giertli > Assignee: Toni Rikkola > > The statuses would be managed with system properties and extend the current on/off switch we have. > It will be possible to change the status for each validation check type. Check types are for example redundancy, range, missing columns. > > * Reactive > The "normal way" you make a change and the verification runs instantly > * Off > Verification is disabled > * On demand > Verification only runs when requested. Can be useful for large dtables where you for example change every value in a column and just really care about the verification status after all the changes. > Few ideas to think about: > # Might be worth it to also store the state per dtable. > # If V&V runs for over X amount of seconds. Ask if the user wants to change the setting from "Reactive" to "On Demand" for this table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1808) Inherited Rules' LHS variables in sub-rules KIE WORKBENCH 6.3.0

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1808?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2499 to DROOLS-1808: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1808 (was: GUVNOR-2499) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Data Model Oracle Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Data Model Oracle) (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Affects Version/s: 6.3.0.Final (was: drools_6.3.0.Final) > Inherited Rules' LHS variables in sub-rules KIE WORKBENCH 6.3.0 > --------------------------------------------------------------- > > Key: DROOLS-1808 > URL: https://issues.jboss.org/browse/DROOLS-1808 > Project: Drools > Issue Type: Enhancement > Components: Data Model Oracle, Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 6.3.0.Final > Reporter: Marius Lazar > Priority: Minor > > I found that when I have 2 rules, second one inheriting from the first one in KIE Workbench 6.3.0, I can't use in the second rule the variable declared in the first rule. > {code:java} > rule "rule1" > dialect "java" > when > patientSheet : Sheet( RE > 0 && HER2 < 0 && ( KIE67 > 14 || RP < 20 || grad == 3 )) > then > end > rule "rule2" extends "rule1" > dialect "java" > when > Sheet( RP >= 50 && RE >= 50 && tumorDimension <= 2 && ( pN == "pN0" || pN == "pN1mic" )) > then > patientSheet.setTreatment( "Therapy1" ); > end > {code} > In the example above, I can't refer to the "patientSheet" declared in the rule that I extend. Also, on the RHS of the second rule I have to write free DRL to set a property of "patientSheet". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1809) Dependent Enumerations: Add support to span Conditions (THEN) and Actions (WHEN)

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1809?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1914 to DROOLS-1809: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1809 (was: GUVNOR-1914) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Data Model Oracle Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Data Model Oracle) (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Affects Version/s: 5.5.0.Final (was: drools-5.4.0.Final) > Dependent Enumerations: Add support to span Conditions (THEN) and Actions (WHEN) > -------------------------------------------------------------------------------- > > Key: DROOLS-1809 > URL: https://issues.jboss.org/browse/DROOLS-1809 > Project: Drools > Issue Type: Enhancement > Components: Data Model Oracle, Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: mahmood lebbai > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017