May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3956: ---------------------------------------- Hi [~uxdlc] AFAIK they're BPMN terms; however they _could_ possibly apply to the use of a DMN file too (e.g. it's when the BPMN Node is entered/exited). > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png > > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3956: -------------------------------------- Attachment: Screen Shot 2019-05-03 at 1.53.33 PM.png > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png > > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3956: ------------------------------------------- !Screen Shot 2019-05-03 at 1.53.33 PM.png|thumbnail! > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png > > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3956: ------------------------------------------- [~roger.martinez] [~manstis] Can you tell me about the On Entry/ On Exit portion of this? I didn't include it in the mock. Is that more Process related, for the node, rather than the Rules? > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png > > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Elizabeth Clayton edited comment on DROOLS-3956 at 5/3/19 2:34 PM: ------------------------------------------------------------------- [~roger.martinez][~ibek] [~tirelli] I attached a mock for the basic design for this scoped jira, in addition to some documentation (^^ link.) Please let me know if there are any additional details that need to be mocked or documented. !Screen Shot 2019-05-03 at 7.31.32 AM.png|thumbnail! was (Author: uxdlc): [~roger.martinez][~ibek] [~tirelli] I attached a mock for the basic design for this scoped jira, in addition to some documentation (^^ link.) Please let me know if there are any additional details that need to be mocked or documented. Barring objection, I'll mark this as Resolved. !Screen Shot 2019-05-03 at 7.31.32 AM.png|thumbnail! > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-03 at 7.31.32 AM.png > > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12019: ------------------------------------- [~spyrkob] I've linked and submitted a fix for https://issues.jboss.org/browse/WFLY-12047. It should only affect master. > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12047) Single sign-on removal does not remove all installed services.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12047: ----------------------------------- Summary: Single sign-on removal does not remove all installed services. Key: WFLY-12047 URL: https://issues.jboss.org/browse/WFLY-12047 Project: WildFly Issue Type: Bug Components: Clustering, Web (Undertow) Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro I'm running into a problem with SSO manager installer service. When I remove the sso setting from host config using allow-resource-service-restart=true and try to add it again without reload I'm get a failure: {noformat} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:remove{allow-resource-service-restart=true} {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=test-host/setting=single-sign-on:add { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service. DuplicateServiceException: Service jboss.undertow.server.default-server.test-host.single-si gn-on.manager.installer is already registered", "rolled-back" => true } {noformat} It looks like the installer service is created every time DistributableSingleSignOnManagerServiceConfigurator is build, but never removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12019: ----------------------------------- Assignee: Bartosz Spyrko (was: Paul Ferraro) > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12019: ------------------------------------- The jboss.undertow.server.default-server.test-host.single-sign-on.manager.installer service is installed into a child target, which the intention of being auto-removed when the parent service container is destroyed. However, it appears that this parent service container isn't granular enough. I'll have a look today. > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12019: ----------------------------------- Assignee: Paul Ferraro (was: Bartosz Spyrko) > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Paul Ferraro > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019