January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4936) Unsaved changes dialog appears even if it just have been saved

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4936?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4936: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Unsaved changes dialog appears even if it just have been saved > -------------------------------------------------------------- > > Key: DROOLS-4936 > URL: https://issues.redhat.com/browse/DROOLS-4936 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Open a GRE file. Add a fact pattern. Save. > Close and the editor still thinks it has not been saved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4895) Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4895?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4895: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String ); > ---------------------------------------------------------------------------------- > > Key: DROOLS-4895 > URL: https://issues.redhat.com/browse/DROOLS-4895 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito > also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4742) [DMN Designer] Code Completion - Add suggestions about "requirements" and/or "dependencies" of a decision node

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4742?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4742: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Code Completion - Add suggestions about "requirements" and/or "dependencies" of a decision node > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4742 > URL: https://issues.redhat.com/browse/DROOLS-4742 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Add suggestions about "requirements" and/or "dependencies" of a decision node. > For instance, when a *Decision* {{routing}} has *Input Data* {{Customer}} in the information requirement, the code completion must show the suggestion {{Customer}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3936) [DMN Designer] Data Types - Constraints enumeration - skip zero values

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3936?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3936: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > [DMN Designer] Data Types - Constraints enumeration - skip zero values > ---------------------------------------------------------------------- > > Key: DROOLS-3936 > URL: https://issues.redhat.com/browse/DROOLS-3936 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3936.png > > > In the Data Types tab > Data Types list > Constraints > Enumeration (for *days and time duration*): > !DROOLS-3936.png|thumbnail! > We must skip zeros, and show: > *1 day* > ...instead of showing: > *1 day, 0 hours, 0 minutes, 0 seconds* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-3879: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 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) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Create Kogito version of Test Scenarios designer > ------------------------------------------------ > > Key: DROOLS-3879 > URL: https://issues.redhat.com/browse/DROOLS-3879 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor. > From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`. > Access to it has been "hided" behind a wrapper interface with three actual implementations: > * `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment > * `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment > * `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode). > As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place. > Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach. > Kogito-testing module is a standalone showcase that provides some minimum interaction to: > * load DMN files > * create DMN-related scesim assets, selecting one of the imported DMN. > Currently - RULE/data object model scesim is disabled. > Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset. > Some minimal tests may be done in the following way: > # full compilation (i.e. included GWT compilation) of the runtime module > # open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome > # inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid. > # edit the asset > # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().getContent() and store the returned xml > # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent method with the stored xml > Some tricks: to avoid CORS and other policy-related issues: > # set chrome://flags/#allow-insecure-localhost for invalid certificates error > # start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file. > /----/ > The "run scenario" functionality won't be implemented by this PR. > All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4507?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4507: ----------------------------------- 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) (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)) > 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 > Labels: drools-tools > > 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, 3 months

1
0
0 / 0

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

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4636?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4636: ----------------------------------- Sprint: 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) (was: 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)) > Update Scenario Cheatsheet to mention MVEL and Background > --------------------------------------------------------- > > Key: DROOLS-4636 > URL: https://issues.redhat.com/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, drools-tools > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4878) Test Scenario: fix support for default stateless kieSession

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4878?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4878: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30)) > Test Scenario: fix support for default stateless kieSession > ----------------------------------------------------------- > > Key: DROOLS-4878 > URL: https://issues.redhat.com/browse/DROOLS-4878 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > How to reproduce: > - edit kmodule.xml and create only a default stateless session > {code:java} > <kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <kbase name="myKieBase"> > <ksession name="mySession" type="stateless" default="true"/> > </kbase> > </kmodule> > {code} > - create a Rule test scenario and specify in Setting panel {{stateless}} > - run -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4883?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4883: ----------------------------------- Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20) (was: 2020 Week 01-03 (from Dec 30)) > Test Scenario: create kie-docs content for Test Scenario Kie-server support > --------------------------------------------------------------------------- > > Key: DROOLS-4883 > URL: https://issues.redhat.com/browse/DROOLS-4883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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.redhat.com/browse/DROOLS-4688?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4688: ----------------------------------- Sprint: 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) (was: 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)) > [DMN Designer] Basic Code Completion for DMN Literal Expressions (7.6) > ---------------------------------------------------------------------- > > Key: DROOLS-4688 > URL: https://issues.redhat.com/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, 3 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 January 2020