November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3225: -------------------------------- Attachment: (was: auto.dmn) > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3193: --------------------------------- Sprint: (was: 2018 Week 42-44) > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png > > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3193: -------------------------------------- [~uxdlc], don't worry about it, Liz, I will move this issue directly to the next sprint. Thanks for scheduling the meeting! > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png > > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3220. ------------------------------- Resolution: Cannot Reproduce Tried with latest bits, seems working fine. > [DMN Designer] [Edge] Unable to edit context cell > ------------------------------------------------- > > Key: DROOLS-3220 > URL: https://issues.jboss.org/browse/DROOLS-3220 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Environment: Windows, Edge browser > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > Attachments: drools-3220.gif > > > User is unable to invoke edit mode for context cells. Other expression types seems to work fine. > Spotted during DROOLS-3214 review, however don't think it is related. > h2. Acceptance test > Invoke edit mode of regular cell > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context > Invoke edit mode of header cell - where applicable > - Literal > - Dec. Table > - Function > - Relation > - Invocation > - Context -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4195) CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-4195?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-4195: ----------------------------------- User {{test}} can not see the new server group without a reload operation because [ServerGroupScopedRoleWriteAttributeHandler.applyUpdateToRuntime()|https:/...] (where it applies change to constraint) is not executed for write operation: {code:java} /core-service=management/access=authorization/server-group-scoped-role=maintainer-scope-role:write-attribute(name=server-groups, value=[main-server-group,new-server-group] {code} It's supposed to be called from a Runtime step handler in AbstractWriteAttributeHandler.execute(), but it's skipped at [if (requiresRuntime(context))|https://github.com/wildfly/wildfly-core/blob/7....] check. [AbstractOperationContext.isHostCapableAddress()|https://github.com/wildfl...] returns false as following activeStep.address does not match the address format _The process is a HC, and the address of the operation is a subsystem in the host model or a child thereof_ {code:java} activeStep.address.size() >= 2 && activeStep.address.getElement(0).getKey().equals(HOST) && activeStep.address.getElement(1).getKey().equals(SUBSYSTEM) {code} {code:xml} [ ("core-service" => "management"), ("access" => "authorization"), ("server-group-scoped-role" => "maintainer-scope-role") ] {code} I'd like to confirm the correct behavior with [~brian.stansberry] first. If not requiring a reload is preferable option as said in BZ, it seems that ServerGroupScopedRoleWriteAttributeHandler should override execute() and apply change to constraint without matching the activeStep.address format above ? > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-4195 > URL: https://issues.jboss.org/browse/WFCORE-4195 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Alpha4 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3225: ------------------------------------- [~manstis] ok, I think it is tightly related to this [~tari_manga]'s [comment|https://github.com/kiegroup/drools/pull/2123#pullrequestreview-17...] > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2910) [DMN Designer] All grid cell editing should respond to single click

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2910?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2910: ------------------------------------- [~uxdlc] From my point of see no problem in conversion to Story or task. Regarding your question "how to prioritize for 7.3". Well 7.3 is product version and thus planning has to happen via: - BAPL for new features - RHDM, RHPAM for bugs and small enhancements I believe this "single click" affect so many elements of DMN (BPMN, CM probably too) so we need some BAPL jira for this. > [DMN Designer] All grid cell editing should respond to single click > -------------------------------------------------------------------- > > Key: DROOLS-2910 > URL: https://issues.jboss.org/browse/DROOLS-2910 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > > Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click. > h2. Manual Acceptance Test > - Not possible edit multiple cells by hold CTRL and click on multiple cells > - Click column/row leading cell discard edit dialog > - Edit can be discarded by escape > - Edit can be discarded by click to canvas > - Invoke edit of cell, return do DRG > - Save and reopen > - Undo redo of editation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3225: ------------------------------------- [~manstis] In header cell. > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4195) CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-4195?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-15759 to WFCORE-4195: ------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4195 (was: JBEAP-15759) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) Affects Version/s: 7.0.0.Alpha4 (was: 7.1.4.GA) > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-4195 > URL: https://issues.jboss.org/browse/WFCORE-4195 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Alpha4 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-102) Validate timeout attributes in configuration

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-102?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-102. ------------------------------ Resolution: Done > Validate timeout attributes in configuration > --------------------------------------------- > > Key: AG-102 > URL: https://issues.jboss.org/browse/AG-102 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 1.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 2018