October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1838) Referencing condition literals in action columns in Web based decision table

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1838?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1936 to DROOLS-1838: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1838 (was: GUVNOR-1936) 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) > Referencing condition literals in action columns in Web based decision table > ---------------------------------------------------------------------------- > > Key: DROOLS-1838 > URL: https://issues.jboss.org/browse/DROOLS-1838 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Roman Novak > Assignee: Michael Anstis > > The use case is to avoid reduncancy in entering data in the web based decision table. > The redundance occurs, when a "not" condition is used in the LHS of a rule, and exactly the entered condition (in the example rule below it is "demo") should be used/referenced on the RHS of the rule. > The solution proposal is: > * it is already possible to reference binding variables in Guvnor decision tables via "=". e.g. set the default value of an action column by "=$p.name" (again with the example below in mind).l > * it should be possible to reference the actual column content via the mandatory "Column header (description)" field in a way, so that during the generation of the rule code the content of the column in the editor is placed into the action field. > * suggestion for (de-)referencing the column: ={<column header>} > Example rule to illustrate the problem: > declare Address > streetName : String > end > > declare Person > name : String > end > > rule "Using a declared Type" > when > $p : Person( name == "Bob" ) > not Address(streetName == "demo") > then > // if the address does not exist, we create it... (just for example) > Address addr = new Address(); > // how can the streetName "demo" from above be referenced ? in a normal rule it is not possible! (scope delimiter "not") > addr.setStreetName("demo"); > insert( addr ); > end -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1839) Guided Decision Table V&V - Unused attributes

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1839?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2197 to DROOLS-1839: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1839 (was: GUVNOR-2197) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Table V&V - Unused attributes > --------------------------------------------- > > Key: DROOLS-1839 > URL: https://issues.jboss.org/browse/DROOLS-1839 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > We check if a field "status" has the enum values WAITING or DECLINED in the LHS, but never if it is OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1840) Guided decision table: Round-tripping: Export of Guided decision table as XLS

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1840?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1833 to DROOLS-1840: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1840 (was: GUVNOR-1833) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided decision table: Round-tripping: Export of Guided decision table as XLS > ----------------------------------------------------------------------------- > > Key: DROOLS-1840 > URL: https://issues.jboss.org/browse/DROOLS-1840 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > XLS Decision tables can be converted to Web Guided Decision Tables. We need to add the ability to export the resulting Web Guided Decision Table as XLS. Ideally the export should maintain the formatting of the original XLS decision table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1828) [Guided Decision Table] New Toolbar

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1828?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3463 to DROOLS-1828: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1828 (was: GUVNOR-3463) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [Guided Decision Table] New Toolbar > ----------------------------------- > > Key: DROOLS-1828 > URL: https://issues.jboss.org/browse/DROOLS-1828 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Ivo Bek > Assignee: Guilherme Carreiro > Labels: UX > Fix For: 7.5.0.Final > > Attachments: Decision Table 1.png, Decision Table 2.png, DecisionTableColTab.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We need a new toolbar of the buttons and tabs which contains the most commonly used actions and options, hide the advanced actions, remove unneeded buttons, and add new buttons such as "Add Row". > As part of the JIRA: > -Rename "otherwise" action in Edit menu to "All other" ([~stetson.robinson] did you come up with anything else?)- > [Moved to https://issues.jboss.org/browse/GUVNOR-3462] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1829) Guided Decision Table Editor: Individual BRL Variable Columns cannot be movable

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1829?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2887 to DROOLS-1829: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1829 (was: GUVNOR-2887) 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.Beta6 (was: 7.0.0.Beta6) > Guided Decision Table Editor: Individual BRL Variable Columns cannot be movable > ------------------------------------------------------------------------------- > > Key: DROOLS-1829 > URL: https://issues.jboss.org/browse/DROOLS-1829 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta6 > Reporter: Michael Anstis > > It is possible to drag and drop columns in a Guided Decision Table to re-order them; however it is currently impossible (and arguably should remain impossible) to re-order individual "BRL Variable Columns" because their order is determined by the underlying BRL definition, which is based on {{RuleModel}}. For example > {code} > Person( age == @{age} ) > Income( bonus > @{bonus} ) > {code} > It should not be possible to re-order "age" and "bonus" since the {{IPattern}} objects would need re-ordering in the {{RuleModel}}. Obviously the scenario gets more complicated with more complex BRL definitions. > This all said and done; when hovering over a "BRL Variable Column" header the mouse pointer still changes to a "hand" suggesting the column can be moved. The flag for "movable" columns exists at the column-level whereas it needs to be moved to the column header meta-data. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1830) Verification & Validation: Management for the issue reporting

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1830?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2569 to DROOLS-1830: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1830 (was: GUVNOR-2569) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Verification & Validation: Management for the issue reporting > ------------------------------------------------------------- > > Key: DROOLS-1830 > URL: https://issues.jboss.org/browse/DROOLS-1830 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > #1 issue: Reports keep popping up after each edit. > #2 issue: Depending what the dtable goals are, some issues are known and should happen. Reporting these over and over again is just useless noise. > Ideas for keeping the noise down: Make it possible to minimize the verification result panel to the side and only open when needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1831) Guided decision table: When the operator is "in" or "not in" values should be created with list widget rather than separating with commas

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1831?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1857 to DROOLS-1831: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1831 (was: GUVNOR-1857) 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.Beta2) > Guided decision table: When the operator is "in" or "not in" values should be created with list widget rather than separating with commas > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1831 > URL: https://issues.jboss.org/browse/DROOLS-1831 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Minor > > When the operator is "in" or "not in" the list of values (for types other than enums) are defined by typing literal values separated by commas into a TextBox. This should be changed to use a new widget that allows a list of values to be created, with the value editor being correct for the field's data-type. This widget will also need to be used to define Default Values, the Wizard and Limited Entry types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1832) Guided decision table: Round-tripping: Improve version control of converted assets

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1832?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1832 to DROOLS-1832: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1832 (was: GUVNOR-1832) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided decision table: Round-tripping: Improve version control of converted assets > ---------------------------------------------------------------------------------- > > Key: DROOLS-1832 > URL: https://issues.jboss.org/browse/DROOLS-1832 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Converting an XLS decision table into a Web Guided Decision Table creates numerous assets. If a new version of the XLS decision table is uploaded and subsequently converted the initial additional assets created should be checked out and updated instead of creating new. This requires the XLS decision table to maintain details of the assets created as a result of the conversion and, on subsequent conversions, these should be checked out and updated. > AssetItem needs to be enhanced (like ModuleItem) to store a list of "dependent assets". This requires the guvnor-repository rule_node_type.cnd file having "drools:dependencies" added and further methods to AssetItem added to handle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1833) Guided decision table: Pluggable editors for (Business) Model Fact Types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1833?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1463 to DROOLS-1833: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1833 (was: GUVNOR-1463) 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) > Guided decision table: Pluggable editors for (Business) Model Fact Types > ------------------------------------------------------------------------ > > Key: DROOLS-1833 > URL: https://issues.jboss.org/browse/DROOLS-1833 > Project: Drools > Issue Type: Feature Request > Components: Data Model Oracle, Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Only pop-up editors for a small range of data-types are currently supported (e.g. numeric, Date, Boolean, String, enum). Add support for pluggable "pop-up" editors (possibly look at integrating WorkingSets' custom forms?). An example would be "Post Code", "National Insurance Number", "email address" etc where they are "single-field" but require their value to follow a well defined pattern. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1822) [Guided Decision Table] Set Field value With Work Item is too strict in Type Comparison

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1822?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3170 to DROOLS-1822: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1822 (was: GUVNOR-3170) 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] Set Field value With Work Item is too strict in Type Comparison > --------------------------------------------------------------------------------------- > > Key: DROOLS-1822 > URL: https://issues.jboss.org/browse/DROOLS-1822 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > Lets say you have in your GDT column that executes work item. Next assume this work item returns Float result. Next assume you want to set value of a string field with this Float result (You will use _Set the field value with Work Item column_). Currently user is not able to do this. Currently user is allowed just to do assignments like String -> String, Float -> Float in the _Set the field value with Work Item column_. > Reproducer submitted as: https://github.com/kiegroup/drools-wb/pull/528 > Once the issue is fixed, please unignore the ignored test from PR. -- 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