July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4161: --------------------------------------- [~zhutaojiajia] Yes I think setting panel is the best fit for this parameter. I think it could be nice to have the possibility to change decision service to be tested after file creation mainly because also decision service can change over the time and user needs a way to update this value. > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4162: --------------------------------------- [~zhutaojiajia] If you look at screenshot !Screenshot from 2019-07-08 14-12-18.png|thumbnail! You can see that all 4 scenarios has exactly the same 3 people as input ({{Person 1}}, {{Person 2}}, {{Person 3}}) and only {{Alert}} is specific of the scenario. User would like to specify Person 1-2-3 a single time and use in all the scenarios. To do that he needs to specify at least column mapping as usual + values. It is not clear to me what are you thinking because it is not clear to me how the user can specify that an instance is part of the background section and how to display it in the right panel. Keep in mind that in general background is exactly the same for each scenario so if background contains 10 instances, each scenario will have it automatically. We can probably propose something different like background per scenario but in this case I don't know how to differentiate a "shared" input to a normal scenario specific input > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-07-08 14-12-18.png, design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4300) Karaf KIE features contains special maven keywords RELEASE

by Daniel Brownell (Jira)

Daniel Brownell created DROOLS-4300: --------------------------------------- Summary: Karaf KIE features contains special maven keywords RELEASE Key: DROOLS-4300 URL: https://issues.jboss.org/browse/DROOLS-4300 Project: Drools Issue Type: Bug Components: integration Affects Versions: 7.11.0.Final Environment: JBoss Fuse 7.3 on Centos 7 (inside Docker 18.09.7), openjdk version "1.8.0_212" Reporter: Daniel Brownell Assignee: Mario Fusco In order to install KIE in Fuse, one needs to run: features:install kie This requires adding a URL first: features:addurl mvn:org.kie/kie-karaf-features/7.11.0.Final/xml/features This however adds: mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features and mvn:org.apache.cxf.karaf/apache-cxf/3.2.7.fuse-sb2-740011/xml/features to my feature:repo-list These are Red Hat Fuse 7.4 features, because the maven special word, RELEASE, grabs the latest versions available. I'm using Fuse 7.3 though, and it crashes a bunch of our applications, and spews errors. For example, it automatically tries to update all of the installed features to use the latest, and then gets into a loop of "Error resolving artifact org.apache.cxf.xjc-utils:cxf-xjc-runtime:jar:3.2.4.fuse-740013" for whatever reason. How does one work around this? What is a safe way to use KIE in Fuse? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4162: ---------------------------------- Attachment: Screenshot from 2019-07-08 14-12-18.png > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-07-08 14-12-18.png, design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4243) Test Scenario: rule scenarios with maps of simple types are failing

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4243?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4243: --------------------------------------- [~kkufova][~emmurphy] Moved to RHDM instead of RHPAM > Test Scenario: rule scenarios with maps of simple types are failing > ------------------------------------------------------------------- > > Key: DROOLS-4243 > URL: https://issues.jboss.org/browse/DROOLS-4243 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > > Create a map of simple type as value (i.e. Map<String, String>) and try to use it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4208) [DMN Designer] Documentation - Widget for links persisting links

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4208?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4208: -------------------------------- Description: Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. The widget must be just like this one: https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 (A list which is populated by the popover). Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). !DROOLS-4208.png|thumbnail! * This is just a suggestion, the entity name can be improved. h3. Acceptance test On both Firefox and Chrome - Multiple links - scroll to view all (/) - Add multiple, delete some (/) - Open the link (/) - Switch between nodes (/) - Link name - long (/) - Link name - multibyte characters (/) was: Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. The widget must be just like this one: https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 (A list which is populated by the popover). Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). !DROOLS-4208.png|thumbnail! * This is just a suggestion, the entity name can be improved. h3. Acceptance test On both Firefox and Chrome - Multiple links - scroll to view all - Add multiple, delete some - Open the link - Switch between nodes - Link name - long - Link name - multibyte characters > [DMN Designer] Documentation - Widget for links persisting links > ---------------------------------------------------------------- > > Key: DROOLS-4208 > URL: https://issues.jboss.org/browse/DROOLS-4208 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-4208.png > > > Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. > The widget must be just like this one: > https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 > (A list which is populated by the popover). > Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). > !DROOLS-4208.png|thumbnail! > * This is just a suggestion, the entity name can be improved. > h3. Acceptance test > On both Firefox and Chrome > - Multiple links - scroll to view all (/) > - Add multiple, delete some (/) > - Open the link (/) > - Switch between nodes (/) > - Link name - long (/) > - Link name - multibyte characters (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4259) Scenario can not access parent data object fields

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4259?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4259: --------------------------------------- [~emmurphy] Created ticket in RHDM as requested https://issues.jboss.org/browse/RHDM-1014 And commented in the PR > Scenario can not access parent data object fields > ------------------------------------------------- > > Key: DROOLS-4259 > URL: https://issues.jboss.org/browse/DROOLS-4259 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > Attachments: Screenshot from 2019-06-26 08-56-23.png, inheritance.zip > > > Scenario Designer can not access parent data object fields, even if the field has public getter and setter. If you check the attached project there are two fields - *price* and *size* while *size* is declared in parent class. If you try to run the scenario, error about not possible initialization of the data object appears. > If you move the *size* field from *Picture* into *Advertisement* class and rerun the scenario, everything works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4299) Scenario can not access parent data object fields

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4299: ------------------------------------- Summary: Scenario can not access parent data object fields Key: DROOLS-4299 URL: https://issues.jboss.org/browse/DROOLS-4299 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.24.0.Final Reporter: Daniele Zonca Assignee: Daniele Zonca Scenario Designer can not access parent data object fields, even if the field has public getter and setter. If you check the attached project there are two fields - *price* and *size* while *size* is declared in parent class. If you try to run the scenario, error about not possible initialization of the data object appears. If you move the *size* field from *Picture* into *Advertisement* class and rerun the scenario, everything works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-807) Tablue Project Access

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-807?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-807: ------------------------------------- Some Update on the ticket received from CEE: Access to CEE dashboards has been requested for all CEE Analytics dashboard stakeholders automatically. We will confirm once this is active. User Enablement - We are currently developing a Mojo page with user enablement and documentation specific for CEE Analytics stakeholders. This will be ready within the next couple of weeks and will be shared once ready. > Tablue Project Access > --------------------- > > Key: SWSQE-807 > URL: https://issues.jboss.org/browse/SWSQE-807 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Prachi Yadav > Priority: Major > Labels: PQI > > [~skondkar] now has access to Tablue, but no visible projects. > [~pyadav] will you work with Sunil to get access to the following projects? > Swiftsunshine > Jaeger > Maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4208) [DMN Designer] Documentation - Widget for links persisting links

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4208?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4208: -------------------------------- Description: Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. The widget must be just like this one: https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 (A list which is populated by the popover). Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). !DROOLS-4208.png|thumbnail! * This is just a suggestion, the entity name can be improved. h3. Acceptance test On both Firefox and Chrome - Multiple links - scroll to view all - Add multiple, delete some - Open the link - Switch between nodes - Link name - long - Link name - multibyte characters was: Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. The widget must be just like this one: https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 (A list which is populated by the popover). Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). !DROOLS-4208.png|thumbnail! * This is just a suggestion, the entity name can be improved. h3. Acceptance test On both Firefox and Chrome - Multiple links - scroll to view all - Add multiple, delete some - Open the link - Switch between nodes > [DMN Designer] Documentation - Widget for links persisting links > ---------------------------------------------------------------- > > Key: DROOLS-4208 > URL: https://issues.jboss.org/browse/DROOLS-4208 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DROOLS-4208.png > > > Every {{DRGElement}} ({{BusinessKnowledgeModel}}, {{Decision}}, {{DecisionService}}, {{InputData}}, {{KnowledgeSource}}) must have into its properties panel a widget for adding links. > The widget must be just like this one: > https://redhat.invisionapp.com/share/JSQRRG2ZU8K#/screens/349635889 > (A list which is populated by the popover). > Each item in this list is a {{DMNExternalLink}}*, this entity as only two string fields ({{name}} and {{URL}}). > !DROOLS-4208.png|thumbnail! > * This is just a suggestion, the entity name can be improved. > h3. Acceptance test > On both Firefox and Chrome > - Multiple links - scroll to view all > - Add multiple, delete some > - Open the link > - Switch between nodes > - Link name - long > - Link name - multibyte characters -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019