November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4753) NPE shows in scesim editor when user runs imported scesim

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4753?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4753: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > NPE shows in scesim editor when user runs imported scesim > --------------------------------------------------------- > > Key: DROOLS-4753 > URL: https://issues.jboss.org/browse/DROOLS-4753 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz, image-2019-11-13-16-59-18-340.png > > > Unexpected exception throws if user runs test scenario that was previously imported s a scesim file. > !image-2019-11-13-16-59-18-340.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4730) Scenario description column appears on breakdown tab when creating DMN based scenario

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4730?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4730: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > Scenario description column appears on breakdown tab when creating DMN based scenario > ------------------------------------------------------------------------------------- > > Key: DROOLS-4730 > URL: https://issues.jboss.org/browse/DROOLS-4730 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Anna Dupliak > Assignee: Gabriele Cardosi > Priority: Major > Labels: CustomerFocus > Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-56-17-983.png > > > When User goes to Background tab there should be only one column with given. But for Dmn based scenarios there is also description column. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4754) Background cell doesn't highlites if passed vallue to DRL returns scenario failure

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4754?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4754: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > Background cell doesn't highlites if passed vallue to DRL returns scenario failure > ---------------------------------------------------------------------------------- > > Key: DROOLS-4754 > URL: https://issues.jboss.org/browse/DROOLS-4754 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz > > > If the value in Background section made a scenario DRL to fall with exception then the scenario fails and alerts is viewing in alerts table, but the caused cell are not getting red. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4711) [DMN Designer] User is able to drag single data type entry horizontally

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4711?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4711: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > [DMN Designer] User is able to drag single data type entry horizontally > ----------------------------------------------------------------------- > > Key: DROOLS-4711 > URL: https://issues.jboss.org/browse/DROOLS-4711 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Optional > Labels: drools-tools > Attachments: horizontally.webm > > > This issue is caused by DROOLS-4484 > If there is single data type entry user is able to drag in horizontally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4518: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > Implement UX styles for Test Coverage Report > -------------------------------------------- > > Key: DROOLS-4518 > URL: https://issues.jboss.org/browse/DROOLS-4518 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png, Screenshot from 2019-09-10 17-52-00.png, Screenshot from 2019-09-20 12-30-01.png, Screenshot from 2019-09-20 16-05-04.png, Screenshot from 2019-09-20 16-10-22.png, screenshot-1.png > > > The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741. > The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4636: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > Update Scenario Cheatsheet to mention MVEL and Background > --------------------------------------------------------- > > Key: DROOLS-4636 > URL: https://issues.jboss.org/browse/DROOLS-4636 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.27.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Minor > Labels: CustomerFocus > > Update Scenario Cheatsheet for MVEL expression usage. > h3. Here are some topics that could be mentioned: > Expressions for Rule based scenarios for simple types > * Starts from "*#*" > * Runs for +properties+ > * Runs for +duplicated+ properties > * Returns the +same+ type as property type in *GIVEN* > * Returns boolean in *EXPECTED* > * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*" > * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean* > * Could run any of java function for the project > * Exports and imports as any other value > Limitations > 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+ > Use case: > User inputs 1/2 to Integer property > 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+ > Use case: > User inputs inexistent MVEL function in one of the properties > 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons > Use case: > User got one of the GIVEN fact expression excepted > 4.Mvel +cannot be mixed+ with simple expressions in one cell > Use case: > For cell inputs : > {code:java} > [#4+4,68] > #actualvalue>1 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4684) Parser and Canonical Model Compiler error on Conditional Named Consequence

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4684?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4684: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > Parser and Canonical Model Compiler error on Conditional Named Consequence > -------------------------------------------------------------------------- > > Key: DROOLS-4684 > URL: https://issues.jboss.org/browse/DROOLS-4684 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.28.0.Final > Environment: macOS 10.14.6, OpenJDK 1.8.0_222 > Reporter: Duncan Doyle > Assignee: Luca Molteni > Priority: Major > > See reproducer here: https://github.com/DuncanDoyle/drools-conditional-named-consequence-issue > When you use a Conditional Named Consequence {code}if{code} definition directly after an {code}accumulate{code}, Drools gives the following error when parsing the DRL: > {code} > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.28.0.Final:build (default-build) on project drools-conditional-named-consequence-issue: Execution default-build of goal org.kie:kie-maven-plugin:7.28.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: > [ERROR] Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=19, column=0 > [ERROR] text=Unable to resolve ObjectType 'if'] > [ERROR] --- > [ERROR] Warning Messages: > [ERROR] --- > [ERROR] Info Messages: > [ERROR] > {code} > When you add a constraint between the {code}accumulate{code} and the {code}if{code} statement of the Conditional Named Consequence, it works fine. > Also when you try to generate the canonical model from a DRL that contains a Conditional Named Consequence, you get the following error: > {code} > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.28.0.Final:generateModel (default-generateModel) on project drools-conditional-named-consequence-issue: A type incompatibility occurred while executing org.kie:kie-maven-plugin:7.28.0.Final:generateModel: org.drools.compiler.lang.descr.NamedConsequenceDescr cannot be cast to org.drools.compiler.lang.descr.PatternDescr > {code} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4688) [DMN Designer] Basic Code Completion for DMN Literal Expressions (7.6)

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4688?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4688: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > [DMN Designer] Basic Code Completion for DMN Literal Expressions (7.6) > ---------------------------------------------------------------------- > > Key: DROOLS-4688 > URL: https://issues.jboss.org/browse/DROOLS-4688 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Users must have a basic code completion for DMN Literal Expressions. > This task is a MVP, and don't have any backend logic. The code completion is powered by a simple autocompleted of FEEL functions and a simple code highlight. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4689) [DMN Designer] Code Completion - Setup Monaco (loader)

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4689?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4689: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > [DMN Designer] Code Completion - Setup Monaco (loader) > ------------------------------------------------------ > > Key: DROOLS-4689 > URL: https://issues.jboss.org/browse/DROOLS-4689 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: auto-vs-explicit.webm, completion-twice.webm, completions-tabulator.webm, context-completions.webm, last-entry-completion.webm > > > Setup Monaco library (and it's loader) into the DMN webapp. > ⚠️ Notice: test it in all environments (dev-webapp, VSCode webapp, Business Central webapp) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4690) [DMN Designer] Code Completion - Add Monaco support for 'TextAreaSingletonDOMElementFactory'

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4690?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4690: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18) (was: 2019 Week 44-46 (from Okt 28)) > [DMN Designer] Code Completion - Add Monaco support for 'TextAreaSingletonDOMElementFactory' > -------------------------------------------------------------------------------------------- > > Key: DROOLS-4690 > URL: https://issues.jboss.org/browse/DROOLS-4690 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Add Monaco support for {{TextAreaSingletonDOMElementFactory}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019