December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4724?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4724: ---------------------------------------- [~tari_manga] Could you please advise on my comment above, summarised here? IMO `dmn-core`(?) may need some changes to make reporting of invalid BKM state consistent (message from `dmn-validation` and `KieBuilder`). {quote} ERROR - DMN: Missing expression for Business Knowledge Model node WARNING - \[KBase: defaultKieBase\]: DMN: Missing expression for Business Knowledge Model node {quote} The first line is from presumably `dmn-validation` the second from `KieBuilder`. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.redhat.com/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4724?page=com.atlassian.jira.plug... ] Michael Anstis edited comment on DROOLS-4724 at 12/10/19 5:12 AM: ------------------------------------------------------------------ [~tari_manga] Could you please advise on my comment above, summarised here? IMO {{dmn-core}}\(?) may need some changes to make reporting of invalid BKM state consistent (message from {{dmn-validation}} and {{KieBuilder}}). {quote} ERROR - DMN: Missing expression for Business Knowledge Model node WARNING - \[KBase: defaultKieBase\]: DMN: Missing expression for Business Knowledge Model node {quote} The first line is from presumably `dmn-validation` the second from `KieBuilder`. was (Author: manstis): [~tari_manga] Could you please advise on my comment above, summarised here? IMO `dmn-core`(?) may need some changes to make reporting of invalid BKM state consistent (message from `dmn-validation` and `KieBuilder`). {quote} ERROR - DMN: Missing expression for Business Knowledge Model node WARNING - \[KBase: defaultKieBase\]: DMN: Missing expression for Business Knowledge Model node {quote} The first line is from presumably `dmn-validation` the second from `KieBuilder`. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.redhat.com/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4698?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4698: ------------------------------- Component/s: (was: DMN Editor) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.redhat.com/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: UX, UXTeam, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4863) Popup message about Doughnut at Coverage Report pannel of Test Scenario Editor places behind the ridge of the screen in default page scale

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4863: ------------------------------------ Summary: Popup message about Doughnut at Coverage Report pannel of Test Scenario Editor places behind the ridge of the screen in default page scale Key: DROOLS-4863 URL: https://issues.redhat.com/browse/DROOLS-4863 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.31.0.Final Reporter: Anna Dupliak Assignee: Yeser Amer Attachments: image-2019-12-10-10-19-03-285.png !image-2019-12-10-10-19-03-285.png|thumbnail! User cant see the popup message text if he navigates to the Doughnut chart on Coverage Report Panel -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4698?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4698: ------------------------------- Component/s: (was: Test Scenarios Editor) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.redhat.com/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: UX, UXTeam, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4698?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4698: ------------------------------- Component/s: DMN Editor > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.redhat.com/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: UX, UXTeam, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4507) Ability to externally execute project defined tests.

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4507?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4507: -------------------------------- Tester: Anna Dupliak > Ability to externally execute project defined tests. > ---------------------------------------------------- > > Key: DROOLS-4507 > URL: https://issues.redhat.com/browse/DROOLS-4507 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Paul Brown > Assignee: Daniele Zonca > Priority: Major > > Provide the ability to externally invoke project define tests scenario i.e via a rest api. > This is required in order for project defined tests to be reused and executed as part of a delivery pipeline and not from within business central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4296) Rewrite parsing of modified properties

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4296?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-4296: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Luca Molteni) > Rewrite parsing of modified properties > -------------------------------------- > > Key: DROOLS-4296 > URL: https://issues.redhat.com/browse/DROOLS-4296 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Minor > Labels: good-first-issue > > See Consequence::findModifiedProperties > Currently modified properties are parsed throughout the consequence, but that information is already present after the preprocessing of the ModifyStatement so it can be simplified a lot. > This can be forward ported to Kogito also > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4723: -------------------------------- Sprint: (was: 2019 Week 50-52 (from Dec 9)) > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: ScenarioSimulation > Fix For: 7.32.0.Final > > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4723. ------------------------------- Fix Version/s: 7.32.0.Final Resolution: Cannot Reproduce [~yamer] I agree, thank you > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: ScenarioSimulation > Fix For: 7.32.0.Final > > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019