October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3507 to DROOLS-1795: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1795 (was: GUVNOR-3507) 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.Final (was: 7.x) Fix Version/s: 7.0.0.Final (was: 7.x) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1796) Guided Decision Table Does Not Use Correct Dropdown List When Using BRL Fragment

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1796?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2634 to DROOLS-1796: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1796 (was: GUVNOR-2634) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 6.3.0.Final 6.4.0.Final (was: drools_6.3.0.Final) (was: drools_6.4.0.Final) > Guided Decision Table Does Not Use Correct Dropdown List When Using BRL Fragment > -------------------------------------------------------------------------------- > > Key: DROOLS-1796 > URL: https://issues.jboss.org/browse/DROOLS-1796 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 6.3.0.Final, 6.4.0.Final > Environment: Drools 6.4/6.3 workbench on Wildfly 8.1.0Final on Windows 8.1 Enterprise > Reporter: Paul Cotten > Assignee: Guilherme Carreiro > > Guided decision table cell produces a single-selection dropdown list instead of a multiple-selection dropdown list when using "is contained in the (comma separated) list" operator only when using BRL fragment, and therefore does not allow for the creation of lists from the enumerated values. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1797) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1797?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2663 to DROOLS-1797: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1797 (was: GUVNOR-2663) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 6.4.0.Final (was: drools_6.4.0.Final) > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-1797 > URL: https://issues.jboss.org/browse/DROOLS-1797 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 6.4.0.Final > Reporter: Anton Giertli > Assignee: Toni Rikkola > Attachments: 6iOx.png > > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1793) [Guided Decision Table] Validation is not successfull if an unused DSL sentence is present

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1793?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3455 to DROOLS-1793: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1793 (was: GUVNOR-3455) 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) > [Guided Decision Table] Validation is not successfull if an unused DSL sentence is present > ------------------------------------------------------------------------------------------ > > Key: DROOLS-1793 > URL: https://issues.jboss.org/browse/DROOLS-1793 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.2.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > > There is problem with validation of the guided decision table if the table has defined DSL column (BRL column that is using DSL internally) and some row of the table is not using this column. For more details see the steps to reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1787) [Guided Decision Table] Change of BRL condition fragment discards column width

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1787?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2846 to DROOLS-1787: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1787 (was: GUVNOR-2846) 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] Change of BRL condition fragment discards column width > ------------------------------------------------------------------------------ > > Key: DROOLS-1787 > URL: https://issues.jboss.org/browse/DROOLS-1787 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > > Width of decision table columns can be adjusted. However the width is reset to default value after the definition of BRL condition fragment has changed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1788) [Guided Decision Table] "Entry point" and "Binding" cannot be updated

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1788?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3163 to DROOLS-1788: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1788 (was: GUVNOR-3163) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > [Guided Decision Table] "Entry point" and "Binding" cannot be updated > --------------------------------------------------------------------- > > Key: DROOLS-1788 > URL: https://issues.jboss.org/browse/DROOLS-1788 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Attachments: bug-1.gif > > > It's impossible to update the "Entry point" and "Binding" fields in a "Condition Column". See: > !bug-1.gif|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1789) Unexpected results in GDST when using enumerations with commas

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1789?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2894 to DROOLS-1789: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1789 (was: GUVNOR-2894) 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: 7.0.0.Beta6 (was: 7.0.0.Beta6) > Unexpected results in GDST when using enumerations with commas > -------------------------------------------------------------- > > Key: DROOLS-1789 > URL: https://issues.jboss.org/browse/DROOLS-1789 > Project: Drools > Issue Type: Bug > Components: Data Model Oracle, Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 7.0.0.Beta6 > Reporter: Michael Anstis > Assignee: Michael Anstis > > When using enumerations where the values itself contain a comma, the rules generated by a GDST are unexpected, as the "contains in" operator splits those values in the enumerations. Example enumeration: > {noformat} > fact: person > field: city > context: ['paris','london','new york,boston'] > {noformat} > Note: see the 'new york, boston' sample. > The code generated will be: > {noformat} > rule "Row 1 personGDT" > dialect "mvel" > when > p : person( city in ( "new york", "boston" ) ) > then > end > {noformat} > Basically "paris" and "new york,boston" will be treated by the DSL parser as 3 strings in the DRL generation and will produce someting simiular to > p : person( city in ( "paris", "new york", "boston" ) ) > But what the customer expects is the following > p : person( city in ( "paris", "new york,boston" ) ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1790) [Guided Decision Table] Row Expander page throws NPE with dependent enumerations

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1790?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3376 to DROOLS-1790: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1790 (was: GUVNOR-3376) 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.Final (was: 7.1.0.Final) > [Guided Decision Table] Row Expander page throws NPE with dependent enumerations > -------------------------------------------------------------------------------- > > Key: DROOLS-1790 > URL: https://issues.jboss.org/browse/DROOLS-1790 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > If you have a model with "dependent enumerations" defined the "Row Expander" page of the "New Guided Decision Table" Wizard throws a NPE. The workaround is to untick the "Expand all" checkbox before clicking "Finish". The "New Guided Decision Table" Wizard should ideally expand correctly for dependent enumerations or, at the very least, not throw the NPE! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1791) ConditionInspectors for guided DT editor don't do checks for all allowed operators

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1791?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2234 to DROOLS-1791: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1791 (was: GUVNOR-2234) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > ConditionInspectors for guided DT editor don't do checks for all allowed operators > ---------------------------------------------------------------------------------- > > Key: DROOLS-1791 > URL: https://issues.jboss.org/browse/DROOLS-1791 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe > > For String fields, guided DT editor allows the following operators: > ==, !=, <, >, <=, >=, matches, soundslike, == null, != null, in, not in > StringConditionInspector pretty much only checks if the operator is ==, != or 'in'. > This means that some issues won't be detected (Validation and Verification for Decision Tables). E.g. for rules/conditions like 'str > "a"' and 'str > "c"', the subsumption won't be detected (but a fact instance with str == "x" will fire both rules). > ComparableConditionInspector checks for ==, !=, <, >, <=, >= ops, but: > for Dates, guided DT editor allows: > ==, !=, <, >, <=, >=, == null, != null, in, not in, after, before, coincides > for numerical types, guided DT editor allows: > ==, !=, <, >, <=, >=, == null, != null, in, not in -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1792) [Guided Decision Table] Default value of a column is not validated with the field data type

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1792?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2815 to DROOLS-1792: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1792 (was: GUVNOR-2815) 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) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [Guided Decision Table] Default value of a column is not validated with the field data type > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1792 > URL: https://issues.jboss.org/browse/DROOLS-1792 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Jozef Marko > Labels: dtable_testday_preparation, qe-suggest-pre-7.0.0.Final, qe-test-day, reported-by-qe > Fix For: 7.5.0.Final > > > During definition of a condition or an action column, user has possibility to specify 'Default value' for this column. The problem is that the default value is not validated with the field data type. In practice it means that even when the column expects only _Integer_ values (because of the field data type), the default value still can be some _String_ value. The 'Default value' inputs should be validated like particular cells of the guided decision table. In those cells the user is not able to put _String_ value into the cell where are expected only _Integer_ values. -- 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