February 2020 - jboss-jira - Jboss List Archives

[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) (was: 2020 Week 04-06 (from Jan 20)) > 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)

6 years, 4 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) (was: 2020 Week 04-06 (from Jan 20)) > [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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4912) [DMN Designer] Data Types - Inline add action button

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4912?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4912: ----------------------------------- Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2020 Week 04-06 (from Jan 20)) > [DMN Designer] Data Types - Inline add action button > ---------------------------------------------------- > > Key: DROOLS-4912 > URL: https://issues.redhat.com/browse/DROOLS-4912 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Minor > Labels: UX, drools-tools > Attachments: Screen Shot 2020-01-08 at 7.06.20 PM.png > > > Change the behavior and tooltip for the inline add icon-button (+). Currently it converts the type to Structure before adding a row below. Instead, we want it to add another row without converting the type. > Acceptance criteria: > * Tooltip: "Add row below (Ctrl + B)" > Behavior - Clicking the (+) inline add button: > * from a type defined as Structure, will add a field row below. > * from a Field row (within a Structure), will add another field row below. > * from a Simple type, such as "Person(string)", will add another row of the same type below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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) (was: 2020 Week 04-06 (from Jan 20)) > 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)

6 years, 4 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) (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)) > 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: Lance Leverich > 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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4792) [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4792?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4792: ----------------------------------- Sprint: 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) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20)) > [DMN Designer] Eliminate producing of RenedringInformation - BaseKeyboardOperation > ---------------------------------------------------------------------------------- > > Key: DROOLS-4792 > URL: https://issues.redhat.com/browse/DROOLS-4792 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseKeyboardOperation#scrollSelectedCellIntoView|https://github.com/kiegr...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4793) [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4793?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4793: ----------------------------------- Sprint: 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) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20)) > [DMN Designer] Eliminate producing of RenedringInformation - BaseCellSelectionManager > ------------------------------------------------------------------------------------- > > Key: DROOLS-4793 > URL: https://issues.redhat.com/browse/DROOLS-4793 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > During the DROOLS-4735 development, it was found out repetitive producing of {{RenderingInformation}} decreases the designer performance, see the [comment|https://github.com/kiegroup/appformer/pull/843#discussion_r347948845]. > According the changes related to the comment above, we should update also the [BaseCellSelectionManager#startEditingCell|https://github.com/kiegroup/app...]. This method can be rewritten to produce {{RenderingInformation}} just once. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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) (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)) > 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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4870: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20)) > Materialize consequences using Drools > ------------------------------------- > > Key: DROOLS-4870 > URL: https://issues.redhat.com/browse/DROOLS-4870 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance. > We should find a way to pass the bitmask instance to the consequence so that we can materialize them. > This means we should probably not change only the compiler, but also the interpreter of the DSL -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4561) DMN introspect PMML for output types

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4561?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4561: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 04-06 (from Jan 20)) > DMN introspect PMML for output types > ------------------------------------ > > Key: DROOLS-4561 > URL: https://issues.redhat.com/browse/DROOLS-4561 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Critical > Labels: good-first-issue > > Currently PMML is introspected for input parameters names and types. > Also for output parameters names. > Currently the feature is missing PMML introspection for output parameters types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 2020