March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5045) [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5045?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5045: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation > ------------------------------------------------------------------------------- > > Key: DROOLS-5045 > URL: https://issues.redhat.com/browse/DROOLS-5045 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DMN1.2 has RuleAnnotation in the DecisionTable expression. > Our marshallers (-backend and -client) do not support it and use the Expression's Description element for the DecisionRule description column. We also need to enhance the UI to support adding/deleting additional RuleAnnotations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5032: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4956?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4956: ----------------------------------- Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > Normarize rule constraints for property reactivity and indexing > --------------------------------------------------------------- > > Key: DROOLS-4956 > URL: https://issues.redhat.com/browse/DROOLS-4956 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.31.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Having a constraint like > {code:java} > Person(name == $customer) > {code} > is not really the same thing as > {code:java} > Person($customer == name) > {code} > In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4910) [DMN Designer] Data Types - Redesign placeholder screen

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4910?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4910: ----------------------------------- Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > [DMN Designer] Data Types - Redesign placeholder screen > ------------------------------------------------------- > > Key: DROOLS-4910 > URL: https://issues.redhat.com/browse/DROOLS-4910 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Redesign placeholder screen: > !prototype.png|width=800! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4761) Move kie-remote and hacep module into drools repo

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4761?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4761: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 07-09 (from Feb 10)) > Move kie-remote and hacep module into drools repo > ------------------------------------------------- > > Key: DROOLS-4761 > URL: https://issues.redhat.com/browse/DROOLS-4761 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4575: ----------------------------------- Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5059) Verifier: GDST columns empty enumeration should be ignored

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5059?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5059: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Verifier: GDST columns empty enumeration should be ignored > ---------------------------------------------------------- > > Key: DROOLS-5059 > URL: https://issues.redhat.com/browse/DROOLS-5059 > Project: Drools > Issue Type: Bug > Components: verifier > Affects Versions: 7.33.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Not sure how the problem GDST is created, but it looks like there is a scenario where the value list for column is empty instead of null and the empty String as value list triggered the Verifier to think the column is an enumeration column. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3002) Redo PMML scorecards rules to use executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3002?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3002: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > Redo PMML scorecards rules to use executable model > -------------------------------------------------- > > Key: DROOLS-3002 > URL: https://issues.redhat.com/browse/DROOLS-3002 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.12.0.Final > Reporter: Lance Leverich > Assignee: Gabriele Cardosi > Priority: Major > Labels: PMMLRefactor, drools-core > > Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model. > # Make further usage of POJOs to replace any types declared within the rule file > # Change the rules generated so that the rules are Java, based on the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3648) [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3648?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3648: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3648 > URL: https://issues.redhat.com/browse/DROOLS-3648 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3648.png > > > Currently, when users click on "Input Clauses", the popover show "Name", however, the expected label is "Expression". > !DROOLS-3648.png|thumbnail! > ⚠️ Before starting this task, check with if only changing the label is enough. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-2845: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)) > Extend the existing verifier to support DMN tables > -------------------------------------------------- > > Key: DROOLS-2845 > URL: https://issues.redhat.com/browse/DROOLS-2845 > Project: Drools > Issue Type: Epic > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: UX, drools-tools, verifier > > h1. Goal > Reuse the V&V created for Guided Decision Tables on the DMN tables. > h1. Workload divided to steps > I propose the work goes in the following steps. After each step I should be able to merge into master. > Steps: > # Move Verifier core to kie-wb-common > # Move V&V reporting UI to kie-wb-common > # Make the web worker connector reusable for different V&V types > # -Make a servlet module for DMN that allows the download of the Web Worker.- > # Create an adapter for DMN tables > # Add support for ranges ( these are given in DMN so no need to use JSR303 ) > # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense > The workload has changed. Now the goal is to reuse the DRL V&V codes in the existing DMN Codes. This means most of the work done for this ticket has no effect and the goal is to adjust to existing DMN V&V reporting, not the other way around. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

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 March 2020