October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1841) Want to know how to delete the boolean cell from the KIE guided decision table rules.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1841?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3396 to DROOLS-1841: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1841 (was: GUVNOR-3396) 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) > Want to know how to delete the boolean cell from the KIE guided decision table rules. > ------------------------------------------------------------------------------------- > > Key: DROOLS-1841 > URL: https://issues.jboss.org/browse/DROOLS-1841 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Final > Reporter: Dinesh Pandey > Assignee: Michael Anstis > Attachments: Screen Shot 2017-08-07 at 3.34.49 PM.png > > > Want to know how to delete the boolean cell from the KIE guided decision table rules. > By default it is adding all the boolean variable as false. Even if you don't need for that rule. > Screen shot attached. > Raised question in google groups > https://groups.google.com/forum/#!searchin/drools-usage/boolean%7Csort:re... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1842) Verification & Validation: V&V has special treatment for Integer types, Long & BigInteger should have the same

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1842?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2576 to DROOLS-1842: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1842 (was: GUVNOR-2576) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Verification & Validation: V&V has special treatment for Integer types, Long & BigInteger should have the same > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1842 > URL: https://issues.jboss.org/browse/DROOLS-1842 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > For example for Integers x > 0 and x >= 1 are considered equal. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1843) Support for empty condition columns on decision tables. Error when converting to guided decision tables.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1843?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2626 to DROOLS-1843: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1843 (was: GUVNOR-2626) 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) > Support for empty condition columns on decision tables. Error when converting to guided decision tables. > -------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1843 > URL: https://issues.jboss.org/browse/DROOLS-1843 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 6.4.0.Final > Reporter: Stathis Politis > Attachments: ReasonCodesShortAndLong.xls, ReasonCodesShortAndLong_correctXLS.xls, exception.txt > > > There is a need to support columns with single data in the decision table and with no conditions. For this reason, we added a dummy condition eval("$param" == "$param") to be able to convert to the guided decision tables. In cases though, where a condition exists with no $param inside (e.g in the attached Excel at cell C32 not(exists ReasonCodeType(reasonCode== ReasonCodeTypeEnum.LT) ) we are obliged to append eval("$param" == "$param") in the front of the condition,so the parser can convert it to the guided decision table. If we use quotes "$param" we get the attached exception, otherwise it works. Why there is inconsistent behavior with the quotes and how can I deal with the fact that each condition requires $param inside? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1844) Column Filter like in xls file

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1844?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2876 to DROOLS-1844: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1844 (was: GUVNOR-2876) 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) Fix Version/s: 6.4.0.Final (was: drools_6.4.0.Final) > Column Filter like in xls file > ------------------------------ > > Key: DROOLS-1844 > URL: https://issues.jboss.org/browse/DROOLS-1844 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 6.4.0.Final > Reporter: Pankaj Trivedi > Fix For: 6.4.0.Final > > > As we propose Guided decision tables kind of alternate to xls file to business users as they are comfortable with xls. Can we have feature to filter columns of guided decision tables. It would be very handy for for business user to manage rules if decision table is getting bigger. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1845) Entry-point declarations: New asset type, new editor, change to existing editors

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1845?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1624 to DROOLS-1845: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1845 (was: GUVNOR-1624) 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.2.0.Final) > Entry-point declarations: New asset type, new editor, change to existing editors > -------------------------------------------------------------------------------- > > Key: DROOLS-1845 > URL: https://issues.jboss.org/browse/DROOLS-1845 > Project: Drools > Issue Type: Feature Request > Components: Data Model Oracle, Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > > Following on from JBRULES-3158 Guvnor needs to support the declaration of entry-points. It will need a new asset-type, and a new editor (although the declarative model editor is probably a good starting place). Also all existing rule authoring Widgets (guided rule editor, decision tables, decision table Wizard) that allow the user to specify a (text) entry-point name will need to be changed to provide a list of declared entry-points. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1846) Allow real time verification of Fact's constraints in Guided Editor

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1846?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-538 to DROOLS-1846: ----------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-1846 (was: GUVNOR-538) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Fix Version/s: 7.5.0.Final (was: Out of scope) > Allow real time verification of Fact's constraints in Guided Editor > ------------------------------------------------------------------- > > Key: DROOLS-1846 > URL: https://issues.jboss.org/browse/DROOLS-1846 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Reporter: Esteban Aliverti > Priority: Minor > Labels: guvnor, real_time, real_time_verification > Fix For: 7.5.0.Final > > > It would be good to have real time validation of Fact's Constraints in Guvnor's Guided Editor. > We can use the same verifier rules created by the constraints that are used right now in the "on demand" verification. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1834) Web Guided Rule Editor: Formula in Action Column

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1834?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2006 to DROOLS-1834: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1834 (was: GUVNOR-2006) 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.5.0.Final) > Web Guided Rule Editor: Formula in Action Column > ------------------------------------------------- > > Key: DROOLS-1834 > URL: https://issues.jboss.org/browse/DROOLS-1834 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Abhinay Agarwal > Assignee: Guilherme Carreiro > > In web guided editor, the feature of binding elements of condition column can be added. > And for the action column elements "formula" feature can be added based on the bindings. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1835) Validation false positive w/GDT: "Conflicting rows"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1835?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2803 to DROOLS-1835: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1835 (was: GUVNOR-2803) 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) > Validation false positive w/GDT: "Conflicting rows" > --------------------------------------------------- > > Key: DROOLS-1835 > URL: https://issues.jboss.org/browse/DROOLS-1835 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 6.4.0.Final > Reporter: Jeff Jensen > > The following false positive validation errors occurred for us with the Guided Decision Table editor (created the rule in the GDT editor). They are close but each has one discriminator column making the rows/rules unique. > Note that the same error occurred twice, once for rule rows 1:7 and once for rule rows 4:7. > {quote} > Conflicting rows > Affected rows:4, 7 > (same message for "Affected rows:1, 7") > Conflict between two rows exists when the conditions for both rules are met with a same set of facts, but the actions set existing fact fields to different values. The conditions can be redundant or subsumptant. > Since the actions do different things with the same conditions, it is impossible to know which actions end up activating last. This causes the rule set to be inconsistent. To fix this, please either remove one row or make the conditions more strict. > {quote} > This is the conditions source for the GDT (with names changed): > {code:java} > //from row number: 1 > rule "Row 1 RuleName" > dialect "mvel" > when > $f : F( r == "ABC" ) > $gmi : GMI( ) > $vmear : Vmear( value >= 0.8 , value < 2.0 ) > $sepr : Sepr( sepr <= 1 ) > //from row number: 4 > rule "Row 4 RuleName" > dialect "mvel" > when > $f : F( r == "ABC" ) > $gmi : GMI( ) > $vmear : Vmear( value >= 0.8 , value < 2.0 ) > $sepr : Sepr( sepr > 1 ) > //from row number: 7 > rule "Row 7 RuleName" > dialect "mvel" > when > $f : F( r == "ABC" ) > $gmi : GMI( ) > $vmear : Vmear( value >= 0.8 , value < 2.0 ) > not (Sepr( )) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1836) Guided Decision Tables should use XLS as the save file format

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1836?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2221 to DROOLS-1836: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1836 (was: GUVNOR-2221) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided Decision Tables should use XLS as the save file format > ------------------------------------------------------------- > > Key: DROOLS-1836 > URL: https://issues.jboss.org/browse/DROOLS-1836 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > We can already export the Guided Decision Tables to XLS, this Jira will first determinate what is needed for importing XLS to the current Guided dtable model. > h2. Visual differences > * XLS colored cells, the colors usually have a meaning > * XLS Font sizes, types, text color and bold/italic/overlined > * XLS Cell allows the user to set text aligment > * XLS lets the user to change cell size > h2. Differences in functional specification > * The Drools XLS format allows the user to add Guided rules to more than one Excel tab, each tab can have a different kind of table > * GDST requires each pattern to have a variable name, XLS does not > * GDST requires each column to have a title, XLS does not > * GDST stores the value type > * GDST does not support the XLS forall template > * GDST has "inner enums" that can be set for columns > * GDST file contains authoring history > * XLS does not support generic DRL fracments > * XLS does not support otherwise > * XLS does not support Workitems > * XLS does not support any Guvnor Enums or DSL > * XLS allows more than one $variable to be used for a single column. For example $param1, $param2 for method($param1,$param2) > * XLS allows the DRL functions to be declared inside the XLS file > * XLS can contain XLS formulas > h2. Some random thoughts > * If we go full XLS, then we lose the information about the value type that is set into each cell, but then again, maybe this is not that big of a loss since the information can be regained from the DMO. > * To get the XLS formulas and styles to work we need to write our own GWT Excel > * GDST file contains authoring history, in XLS form this would be openly editable. Then again, you can text edit the file anyway you want to if you git checkout the GDST XML file > * A XLS file can also be a rule template or anything else than a dtable. File ending like dtable.xls or gdst.xls would of course fix this. > * ^ The Guided rule templates might have to move to XLS too. Just to keep things simple, but the XLS templates are made out of two files DRL+XLS > * There is a need for some kind of migration tool or we keep allow the user to open .gdst and save .xml. This means we need to keep the codes for the old model in our workbench codebase forever and ever. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1837) Guided decision table: Add horizontal layout

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1837?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1459 to DROOLS-1837: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1837 (was: GUVNOR-1459) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Guided decision table: Add horizontal layout > -------------------------------------------- > > Key: DROOLS-1837 > URL: https://issues.jboss.org/browse/DROOLS-1837 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > > Guvnor currently provides for a vertical layout of it's guided decision table. This request is to add a horizontal layout (i.e. rules in columns, patterns in rows). -- 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