March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5056: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned > ------------------------------------------------------------------------------- > > Key: DROOLS-5056 > URL: https://issues.redhat.com/browse/DROOLS-5056 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: issue.mp4, taxRate.dmn > > > Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again. > I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes. > I recorded a video with 2 minutes when the issue happens in the last seconds. > As it can be notice it takes lots of trials to reproduce the issue. > Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5077) Test Kogito Operator as a end user

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5077?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5077: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > Test Kogito Operator as a end user > ---------------------------------- > > Key: DROOLS-5077 > URL: https://issues.redhat.com/browse/DROOLS-5077 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4865: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > Add i18n reporting for DMN V&V > ------------------------------ > > Key: DROOLS-4865 > URL: https://issues.redhat.com/browse/DROOLS-4865 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5031) Use general V&V modularity for DMN Validation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5031?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5031: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 10-12 (from Mar 2)) > Use general V&V modularity for DMN Validation > --------------------------------------------- > > Key: DROOLS-5031 > URL: https://issues.redhat.com/browse/DROOLS-5031 > Project: Drools > Issue Type: Enhancement > Components: verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Modularity here means. Any part of the validation can be activated or deactivated. This is an existing feature in general verifier used by GDST. This allows for example two range check implementations to work next to each other making each check type a module. > Other benefits of this approach is for example any future needs that might require running the rules. Allowing static and dynamic validation to exist side by side. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > [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 > Components: DMN Editor > 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)

6 years, 1 month

1
0
0 / 0

[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), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > [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: Daniel José dos Santos > 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. > Accordingly to the spec has no evaluation semantic. User can put in any value. is only text like "code comments". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

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), 2020 Week 13-15 (from Mar 23) (was: 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)) > Move kie-remote and hacep module into droolsjbpm-integration > ------------------------------------------------------------ > > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5164) Automate with ansible HACep deploy

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5164?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5164: ----------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 10-12 (from Mar 2)) > Automate with ansible HACep deploy > ---------------------------------- > > Key: DROOLS-5164 > URL: https://issues.redhat.com/browse/DROOLS-5164 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > > Automate with Ansible the setup from scratch and for every new End user test on CRC -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2)) > 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, 1 month

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), 2020 Week 13-15 (from Mar 23) (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), 2020 Week 10-12 (from Mar 2)) > 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, 1 month

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