February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2272) [DMN Editor] Move Editor controls inline

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2272?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2272: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 05-06) > [DMN Editor] Move Editor controls inline > ---------------------------------------- > > Key: DROOLS-2272 > URL: https://issues.jboss.org/browse/DROOLS-2272 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > Expression Editors have a row of controls to add row, column, change Hit Policy etc. > These all need moving "inline" into the editor itself. The content of the new context menu will be driven by the cell in the Expression grid that was (single) clicked. Double click continues to edit the cell. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1663: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 05-06) > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Fedor Gavrilov > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2307) DMN enhanced for loop

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2307?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2307: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 05-06) > DMN enhanced for loop > --------------------- > > Key: DROOLS-2307 > URL: https://issues.jboss.org/browse/DROOLS-2307 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > Implement enhanced for loop -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2311) Drools Engine not able to load rules in spring-Boot project

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2311?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2311: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 05-06) > Drools Engine not able to load rules in spring-Boot project > ----------------------------------------------------------- > > Key: DROOLS-2311 > URL: https://issues.jboss.org/browse/DROOLS-2311 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Attachments: Drools-Issue.rar > > > am using the Drools 7.5.0-final in the spring Boot project. > I am working on a multi-module Gradle project. Rules and kmodule.xml is present in the sub-module project. This module is packaged as a Jar inside a fat spring boot Jar file. > I am building the container from the classpath. > KieContainer kContainer = kieService.newKieClasspathContainer(); > on server start-up (java -jar) it loads the Kmodule.xml and prints all the kbase and sessionName. > But when I fire rules it returns zero rules fired. > It works fine when I run as spring boot app from Eclipse. Please help. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2316) wrong ordering of ItemDefinition for compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2316?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2316: ----------------------------------- Sprint: 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 05-06) > wrong ordering of ItemDefinition for compilation > ------------------------------------------------ > > Key: DROOLS-2316 > URL: https://issues.jboss.org/browse/DROOLS-2316 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > The following exhibit the issue in the dmn compiler: > {code:java} > @Test > public void test3() { > ItemDefinition tNumberList = build("tNumberList"); > ItemDefinition tTax = build("tTax"); > ItemDefinition tStateModel = build("tStateModel"); > ItemDefinition tTaxList = build("tTaxList", tTax); > ItemDefinition tCategory = build("tCategory"); > ItemDefinition tItem = build("tItem", tCategory); > ItemDefinition tItemList = build("tItemList", tItem); > ItemDefinition tOrder = build("tOrder", tItemList); > > List<ItemDefinition> originalList = Arrays.asList(new ItemDefinition[]{ > tOrder, > tItem, > tCategory, > tNumberList, > tItemList, > tTax, > tStateModel, > tTaxList > }); > > List<ItemDefinition> orderedList = orderingStrategy(originalList); > > assertTrue("Index of tCategory < tItem", orderedList.indexOf(tCategory) < orderedList.indexOf(tItem)); > assertTrue("Index of tItem < tItemList", orderedList.indexOf(tItem) < orderedList.indexOf(tItemList)); > assertTrue("Index of tItemList < tOrder", orderedList.indexOf(tItemList) < orderedList.indexOf(tOrder)); > > assertTrue("Index of tTax < tTaxList", orderedList.indexOf(tTax) < orderedList.indexOf(tTaxList)); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the decision node is not copied

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2214: ----------------------------------- Sprint: 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08 (was: 2018 Week 03-04, 2018 Week 05-06) > [DMN Editor] Content of the decision node is not copied > ------------------------------------------------------- > > Key: DROOLS-2214 > URL: https://issues.jboss.org/browse/DROOLS-2214 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: Stunner > > User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2109: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08 (was: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06) > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Attachments: Screenshot from 2017-11-03 10-20-21.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06) > [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, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08 (was: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06) > FEEL code generation and compilation > ------------------------------------ > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06) > [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 > Labels: UX > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > 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, 2 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 February 2018