June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2655: ------------------------------------- [~tari_manga] thanks for quick response, and agree, we can keep it simple for now. > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2655: ---------------------------------------- bq. if user has opened expression editor, the top level is a decision table, and an Input column was deleted, should be the input node deleted (in case it is not connected to other nodes of DRG)? I would NOT automatically delete, because the user originally explicited the link in the DRG the inputRequirement, hence in some DRD this is also visually explicit. We could however think of asking with a dialog box, as you suggest if it is not linked to other DRG element, then such InputData (assuming a simple type) becomes irrelevant now for the only decision which had it as a requirement. But it is a very advanced feature I would leave it for much later. > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2628) [DMN Designer] DataInput toolbox actions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2628?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2628: -------------------------------- Description: The Data Input node offers not appropriate actions. In the attached screenshot if you check actions on positions *1* and *2* both offer the *Create DMN Decision* action. Furthermore if you select the action at the position *2* the attached error appears. h3. Manual PR Acceptance Test Check all toolbox actions of each node type (/) was: The Data Input node offers not appropriate actions. In the attached screenshot if you check actions on positions *1* and *2* both offer the *Create DMN Decision* action. Furthermore if you select the action at the position *2* the attached error appears. h3. Manual PR Acceptance Test Check all toolbox actions of each node type > [DMN Designer] DataInput toolbox actions > ---------------------------------------- > > Key: DROOLS-2628 > URL: https://issues.jboss.org/browse/DROOLS-2628 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-06-11 15-49-28.png, Screenshot from 2018-06-11 15-53-34.png > > > The Data Input node offers not appropriate actions. In the attached screenshot if you check actions on positions *1* and *2* both offer the *Create DMN Decision* action. Furthermore if you select the action at the position *2* the attached error appears. > h3. Manual PR Acceptance Test > Check all toolbox actions of each node type (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2628) [DMN Designer] DataInput toolbox actions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2628?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2628: -------------------------------- Git Pull Request: https://github.com/kiegroup/kie-wb-common/pull/1919 > [DMN Designer] DataInput toolbox actions > ---------------------------------------- > > Key: DROOLS-2628 > URL: https://issues.jboss.org/browse/DROOLS-2628 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-06-11 15-49-28.png, Screenshot from 2018-06-11 15-53-34.png > > > The Data Input node offers not appropriate actions. In the attached screenshot if you check actions on positions *1* and *2* both offer the *Create DMN Decision* action. Furthermore if you select the action at the position *2* the attached error appears. > h3. Manual PR Acceptance Test > Check all toolbox actions of each node type (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-28) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-28?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-28: ------------------------------------- [~martyn-taylor] I could not get any reasonable information even with enabled traces. It looks like one of the EAP servers is killed. However it's weird that it happens just Artemis 2.x and not with Artemis 1.5.x. > [Artemis 2.x upgrade] Unexptected crash of server in SOAK test > -------------------------------------------------------------- > > Key: WFWIP-28 > URL: https://issues.jboss.org/browse/WFWIP-28 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: feature-branch-blocker > > After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. > Test Scenario: > * Start 2 servers > * Client sends messages to input queue. Messages then go through: > * One server to another through MDB reading and sending them from remote container through resource adapter > * Messages are forwarded from one server to another over JMS bridge and back over Core bridge > * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client > * Messages are read from the destination with stateless EJB and sent back to clients > * Client reads the messages after the pass through all the soak modules. > Pass Criteria: In the last step receiver consumes all messages sent by producer. > Actual Result: > After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2655: ------------------------------------- [~manstis] Please correct me if I am wrong, I think currently we do not have support for complex data types (Person etc...), I think we should split this jira to handle separately simple data types and complex data types. > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2655: ------------------------------------- [~tari_manga] In the meeting we discussed creating InputData nodes if input column added in the expression editor. You explained it is not expected/required. Now came to my mind similar question, if user has opened expression editor, the top level is a decision table, and an Input column was deleted, should be the input node deleted (in case it is not connected to other nodes of DRG)? > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the column causes last column width increase

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2644: -------------------------------- Description: There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. h3. Manual Accpetance Test # Steps to reproduce fixed (/) # Steps to reproduce fixed when decision table / relation is not top level context entry (/) # Repeat steps to reproduce, save and reopen, edit the expression (/) was: There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. h3. Manual Accpetance Test # Steps to reproduce fixed (/) # Steps to reproduce fixed when decision table / relation is not top level context entry (x) # Repeat steps to reproduce, save and reopen, edit the expression (/) > [DMN Designer] Deletion of the column causes last column width increase > ----------------------------------------------------------------------- > > Key: DROOLS-2644 > URL: https://issues.jboss.org/browse/DROOLS-2644 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > > There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. > h3. Manual Accpetance Test > # Steps to reproduce fixed (/) > # Steps to reproduce fixed when decision table / relation is not top level context entry (/) > # Repeat steps to reproduce, save and reopen, edit the expression (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2655: -------------------------------- Description: [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. was:[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2652) [DMN Designer] Different icons for different connector types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2652?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2652: ------------------------------------- [~manstis] [~tari_manga] Hi, this came to my mind after the meeting, could we somehow sort the icons in the context menu? I mean to have grouped nodes and connectors? Does it makes sense for you? Would it be useful from your point of view? > [DMN Designer] Different icons for different connector types > ------------------------------------------------------------ > > Key: DROOLS-2652 > URL: https://issues.jboss.org/browse/DROOLS-2652 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2652 (toolbox icons).png > > > The toolbox shows icons for the different connection types available from a given node. > At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type. > h3. Manual Acceptance test > Each node type has appropriate connector icons in the context menu -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 June 2018