October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1823) [Guided Decision Table] Preserve values during column definition change

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1823?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2927 to DROOLS-1823: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1823 (was: GUVNOR-2927) 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] Preserve values during column definition change > ----------------------------------------------------------------------- > > Key: DROOLS-1823 > URL: https://issues.jboss.org/browse/DROOLS-1823 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: reported-by-qe > > There are cases when it would be worth to preserve cell values during column definition change. > For example if there is column like: *$p : Person (age == $value)* and it is changed to *$p : Person (name == $value)* where *age: Integer* and *name: String* then if there was cell value *10* it could change to *"10"*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1824) Guided Decision Table V&V - Make the V&V pick up salience & activation-group

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1824?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2855 to DROOLS-1824: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1824 (was: GUVNOR-2855) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table V&V - Make the V&V pick up salience & activation-group > ---------------------------------------------------------------------------- > > Key: DROOLS-1824 > URL: https://issues.jboss.org/browse/DROOLS-1824 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > Either the one set in the table or the ones added with code generation based on Hit Policy. > Made the ticket, but not sure if salience changes anything with what we resolve at the moment. It does affect loop detection, but we do not handle that at the moment > * If two rules are subsumptant. The order of the rows does not matter, they are still subsumptant > * If two rules are in conflict. The order does not matter. > Saliance with activation-group however does change things. > * If a rule's LHS with a higher priority subsumes a rule with a lower priority. The lower row never fires. > * We do not care about conflicting rows in activation-group > Due to PHREAK, we always have top to down salience or a salience set by the user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3199 to DROOLS-1825: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1825 (was: GUVNOR-3199) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 7.1.0.Beta2 (was: 7.1.0.Beta2) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1826) Guided Decision Table V&V: Overlaps

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1826?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2797 to DROOLS-1826: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1826 (was: GUVNOR-2797) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table V&V: Overlaps > ----------------------------------- > > Key: DROOLS-1826 > URL: https://issues.jboss.org/browse/DROOLS-1826 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > This will be needed by Unique hit to resolve if table is in fact Unique Singe hit. > We already resolve subsumption. Meaning all the possible values that row A can take also satisfy B. > Subsumption does not cover overlapping rows. Where a set of given values that fire A also fire B, but both rules have a range of given values that only fire A or B. > h6. For example > || Person.age || Application.approve || > | 0 - 50 | yes | > | 40 - 100 | no | > If age is between 40 and 50 both rules fire and it is impossible to say if the rule is approved or not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1827) [Guided Decision Table] Remove support for in-pattern eval

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1827?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3548 to DROOLS-1827: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1827 (was: GUVNOR-3548) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > [Guided Decision Table] Remove support for in-pattern eval > ---------------------------------------------------------- > > Key: DROOLS-1827 > URL: https://issues.jboss.org/browse/DROOLS-1827 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > See https://issues.jboss.org/browse/GUVNOR-3432?focusedCommentId=13474867&pag... > {quote} > Also, please note that eval() inside patterns should not be used. The parser actually strips out all the eval()s inside patterns that it finds. Only top level evals are still useful. > {quote} > Support for "predicate" columns in the Guided Decision Table Editor need to be removed. Support in the UI and model-DRL conversion can be removed. We would also need to write a conversion routine converting predicates to BRL Condition Column {{RuleModel}} expressions. There may be a limitation to what the Expression Editor can support; so we'd need to fall back to Free From Lines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1817) [Guided Decision Table] Fields can not be bound in the wizard

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1817?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2823 to DROOLS-1817: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1817 (was: GUVNOR-2823) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Steps to Reproduce: (was: # Open existing guided decision table # Edit some condition column of this table # You will be able to bind filed name # Now start guided decision table wizard # Define some condition on _Add Constraints_ page ** {color:red}There is no way to bind the field name{color}) Affects Version/s: 7.0.0.Beta5 (was: 7.0.0.Beta5) > [Guided Decision Table] Fields can not be bound in the wizard > ------------------------------------------------------------- > > Key: DROOLS-1817 > URL: https://issues.jboss.org/browse/DROOLS-1817 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Screenshot from 2017-01-04 14-56-18.png, Screenshot from 2017-01-04 14-56-35.png > > > In the Guided Decision Table editor, the user is able to bind column field to some name. This option is completely missing in the Guided Decision Table Wizard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1818) Guided Decision Table V&V reporting - Analysis panel visual improvements

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1818?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2235 to DROOLS-1818: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1818 (was: GUVNOR-2235) 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 - Analysis panel visual improvements > ------------------------------------------------------------------------ > > Key: DROOLS-1818 > URL: https://issues.jboss.org/browse/DROOLS-1818 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Labels: reported-by-qe > > The part of the panel with the issue description has a 60px padding - this is a bit too much. It leaves less space for the actual text, which then often has to be scrolled. > There is also an unusual line-height of 30px for a font-size of 18px. This makes the text hog even more space, quite unnecessarily. > The 'Affected rows' line blends in with the description itself. It could do with a pixel or two (or 5) more of space underneath - together with the removal the 30px line-height, this could set it nicely apart without disrupting anything else. > There are only 5 rows of issues displayed in the top part of the Analysis panel, but even in small guided DTs, there can easily be many more issues. Giving this part more space should be easier after resolving the points above. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1819) GDT Editor - Column wizard - Improve wizard `PluginHandler` to infer the plugin based on pattern matching

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1819?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3300 to DROOLS-1819: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1819 (was: GUVNOR-3300) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > GDT Editor - Column wizard - Improve wizard `PluginHandler` to infer the plugin based on pattern matching > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1819 > URL: https://issues.jboss.org/browse/DROOLS-1819 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Minor > > The current `PluginHandler` implementation infers the plugin based on the column type. Improve that by to inferring based on pattern matching. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1820) Renaming a rule should update related test scenarios

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1820?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2060 to DROOLS-1820: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1820 (was: GUVNOR-2060) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor Impact Analysis (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) (was: Impact Analysis) Affects Version/s: 5.5.0.Final (was: drools-5.3.0.Final) > Renaming a rule should update related test scenarios > ---------------------------------------------------- > > Key: DROOLS-1820 > URL: https://issues.jboss.org/browse/DROOLS-1820 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor, Impact Analysis > Affects Versions: 5.5.0.Final > Environment: JBoss BRMS 5.3.1 - Jboss EAP 6.1.1 > Reporter: Valentijn Scholten > Labels: renaming, testscenario, user_experience > > Current behaviour: > - Create a rule with name "test-rule". > - Create a test scenario with an expect clause "test-rule" should fire at least once. > - Populate the test scenario and test-rule in such a way that the test scenario runs succesfully with this expect clause. > - Rename the rule from "test-rule" to "test-rule-renamed". > - Run the test scenario again. > - Observe the test scenario will fail because it expects a rule with name "test-rule" to be fired at least once. This rule no longer exists because it is renamed. > Expected behaviour: > - When the rule is renamed from "test-rule" to "test-rule-renamed", all test scenarios referring to this rule (in an expect clause or otherwise) should be updated transparently. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1821) Guided Decision table Wizard: Use lists and default selections

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1821?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3514 to DROOLS-1821: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1821 (was: GUVNOR-3514) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision table Wizard: Use lists and default selections > -------------------------------------------------------------- > > Key: DROOLS-1821 > URL: https://issues.jboss.org/browse/DROOLS-1821 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > > Went through this a few times today and my carpal tunnel syndromized wrists suggested this. > To add a column I need to: > # Click Add Column > # Click select "Add simple column" > # Click Next > # Click "Select pattern" > # Click the selection > # Click Next > # Click "Literal Value" > # Click Next > # Click "Select a field" > # Click the selection > # Click Next > # Click "please choose" > # Click selection > # Click Next > # Click Next > # Click Header textbox > # Fill in "Age less than" > # Click Finish > What this could be: > # Click "Add Column" > # Click "Add a simple condition" this also moves me to next tab > # Click the Pattern I want from a listbox (the previous tab had a listbox, this has dropdown) > # Click Next (There is more than pattern selection here so I need to do this) > # Click Literal value and this moves me to next (listbox would work here too or we keep the radio button and default the first selection, selecting any other moves to next tab) > # Click an item from field listbox > # Click an operator from operator listbox > # Click Next > # Preselect Header toolbox, but also fill it with field name + operator > # Click Finish -- 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