June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2512) Add support for multi-file validation on the DMN Validator

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2512?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2512: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 17-18, 2018 Week 19-22) > Add support for multi-file validation on the DMN Validator > ---------------------------------------------------------- > > Key: DROOLS-2512 > URL: https://issues.jboss.org/browse/DROOLS-2512 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Fix For: 7.8.0.Final > > > Currently the DMN validator supports only single file validation, but with the implementation of support for "import" we now have to add support for multi-file validation as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2513) Add support for embedded test execution

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2513?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2513: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 17-18, 2018 Week 19-22) > Add support for embedded test execution > --------------------------------------- > > Key: DROOLS-2513 > URL: https://issues.jboss.org/browse/DROOLS-2513 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Fix For: 7.8.0.Final > > > TCK test cases can be embedded in the DMN model under the extension elements (e.g., see Trisotech generated models). > Add a public API to allow execution of embedded test cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2521) Implement FEEL functions in preparation for DMN 1.2

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2521?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2521: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 17-18, 2018 Week 19-22) > Implement FEEL functions in preparation for DMN 1.2 > --------------------------------------------------- > > Key: DROOLS-2521 > URL: https://issues.jboss.org/browse/DROOLS-2521 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Fix For: 7.8.0.Final > > Attachments: DMN12-190_proposal_v4.docx > > > There are a few new FEEL functions defined for DMN 1.2. > See attached document for the list of functions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > 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: Matteo Mortari > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg, dmn import defaults.odt > > > 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)

6 years

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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2402) [DMN Designer] Support table header cell selection

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2402?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2402: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > [DMN Designer] Support table header cell selection > -------------------------------------------------- > > Key: DROOLS-2402 > URL: https://issues.jboss.org/browse/DROOLS-2402 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png > > > The decision table header cell does not support highlight / selection feature, see: > !Screenshot from 2018-03-20 08-59-39.png|thumbnail! > In contrast context entry name cell support this: > !Screenshot from 2018-03-20 09-20-04.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2156: ----------------------------------- Sprint: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2180) [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2180?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2180: ----------------------------------- Sprint: 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > [Guided Rule Editor] NPE closing a Guided Rule with an incomplete ActionCallMethod > ---------------------------------------------------------------------------------- > > Key: DROOLS-2180 > URL: https://issues.jboss.org/browse/DROOLS-2180 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Minor > > The implementation of {{ActionCallMethod.hashCode()}} fails if the "method name" is {{null}}. This scenario can arise if you create a new Guided Rule, add a "Call method on..." action and leave it incomplete. Trying to close the editor results in a NPE error (as the "is dirty" mechanism uses {{hashCode()}} implementations). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (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, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > 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)

6 years

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, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (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, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > [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, UXTeam > 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)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018