[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ]
Kabir Khan edited comment on WFCORE-4045 at 8/20/18 3:52 PM:
-------------------------------------------------------------
See WFLY-10861 for the background information resulting in this.
The output with https://github.com/wildfly/wildfly-core/pull/3465 is now:
{code}
$curl -v http://127.0.0.1:9990/health
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 9990 (#0)
> GET /health HTTP/1.1
> Host: 127.0.0.1:9990
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: keep-alive
< Content-Type: application/json; charset=utf-8
< Content-Length: 408
< Date: Mon, 20 Aug 2018 19:39:30 GMT
<
* Connection #0 to host 127.0.0.1 left intact
"WFLYDMHTTP0016: Your Application Server is running. However you have not yet added any users to be able to access the HTTP management interface. To add a new user execute the add-user.sh script within the bin folder of your WildFly installation and enter the requested information. By default the realm name used by WildFly is 'ManagementRealm' and this is already selected by default by the add-user tool."
{code}
{code}
[~]
$curl -v -L http://127.0.0.1:9990/health
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 9990 (#0)
> GET /health HTTP/1.1
> Host: 127.0.0.1:9990
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: keep-alive
< Content-Type: application/json; charset=utf-8
< Content-Length: 408
< Date: Mon, 20 Aug 2018 19:51:30 GMT
<
* Connection #0 to host 127.0.0.1 left intact
"WFLYDMHTTP0016: Your Application Server is running. However you have not yet added any users to be able to access the HTTP management interface. To add a new user execute the add-user.sh script within the bin folder of your WildFly installation and enter the requested information. By default the realm name used by WildFly is 'ManagementRea
{code}
As discussed with [~rsvoboda] the API exposed to register http handlers from the subsystems is new and we want to keep it as simple as possible at the moment. The new ManagementHttpServer.addManagementHandler() was reusing the logic from the console to redirect to the standard error mechanism used for the console. This mechanism ends up loading the page https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (linux) or https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (windows).
For this use-case, which will also be used by other subsystems which want to register a custom HttpHandler, the mechanism is to simply send a 500 status code with the text shown above. If something more advanced is needed in the future we can expand the API, but it is too early to do so without knowing the use-cases.
was (Author: kabirkhan):
See WFLY-10861 for the background information resulting in this.
The output with this fix is:
{code}
$curl -v http://127.0.0.1:9990/health
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 9990 (#0)
> GET /health HTTP/1.1
> Host: 127.0.0.1:9990
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: keep-alive
< Content-Type: application/json; charset=utf-8
< Content-Length: 408
< Date: Mon, 20 Aug 2018 19:39:30 GMT
<
* Connection #0 to host 127.0.0.1 left intact
"WFLYDMHTTP0016: Your Application Server is running. However you have not yet added any users to be able to access the HTTP management interface. To add a new user execute the add-user.sh script within the bin folder of your WildFly installation and enter the requested information. By default the realm name used by WildFly is 'ManagementRealm' and this is already selected by default by the add-user tool."
{code}
As discussed with [~rsvoboda] the API exposed to register http handlers from the subsystems is new and we want to keep it as simple as possible at the moment. The new ManagementHttpServer.addManagementHandler() was reusing the logic from the console to redirect to the standard error mechanism used for the console. This mechanism ends up loading the page https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (linux) or https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (windows).
For this use-case, which will also be used by other subsystems which want to register a custom HttpHandler, the mechanism is to simply send a 500 status code with the text shown above. If something more advanced is needed in the future we can expand the API, but it is too early to do so without knowing the use-cases.
> Make ExtensibleHttpManagement.addManagementHandler() return error code 500
> --------------------------------------------------------------------------
>
> Key: WFCORE-4045
> URL: https://issues.jboss.org/browse/WFCORE-4045
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Kabir Khan
> Assignee: Kabir Khan
>
> The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change.
> This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. The standard error page will be updated in WFCORE-4046 to be more generic.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-4045) Make ExtensibleHttpManagement.addManagementHandler() return error code 500
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4045?page=com.atlassian.jira.plugi... ]
Kabir Khan commented on WFCORE-4045:
------------------------------------
See WFLY-10861 for the background information resulting in this.
The output with this fix is:
{code}
$curl -v http://127.0.0.1:9990/health
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 9990 (#0)
> GET /health HTTP/1.1
> Host: 127.0.0.1:9990
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: keep-alive
< Content-Type: application/json; charset=utf-8
< Content-Length: 408
< Date: Mon, 20 Aug 2018 19:39:30 GMT
<
* Connection #0 to host 127.0.0.1 left intact
"WFLYDMHTTP0016: Your Application Server is running. However you have not yet added any users to be able to access the HTTP management interface. To add a new user execute the add-user.sh script within the bin folder of your WildFly installation and enter the requested information. By default the realm name used by WildFly is 'ManagementRealm' and this is already selected by default by the add-user tool."
{code}
As discussed with [~rsvoboda] the API exposed to register http handlers from the subsystems is new and we want to keep it as simple as possible at the moment. The new ManagementHttpServer.addManagementHandler() was reusing the logic from the console to redirect to the standard error mechanism used for the console. This mechanism ends up loading the page https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (linux) or https://github.com/wildfly/wildfly-core/blob/master/domain-http/error-con... (windows).
For this use-case, which will also be used by other subsystems which want to register a custom HttpHandler, the mechanism is to simply send a 500 status code with the text shown above. If something more advanced is needed in the future we can expand the API, but it is too early to do so without knowing the use-cases.
> Make ExtensibleHttpManagement.addManagementHandler() return error code 500
> --------------------------------------------------------------------------
>
> Key: WFCORE-4045
> URL: https://issues.jboss.org/browse/WFCORE-4045
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Kabir Khan
> Assignee: Kabir Khan
>
> The security checks done by the handlers added via ExtensibleHttpManagement.addManagementHandler() currently redirect to the standard html page with an error code of 200. This behaviour is impossible to change.
> This is currently only used by MP Health, for which the ExtensibleHttpManagement API was added. Rather than expand this API we will change the behaviour of handlers added with this mechanism to return 500. The standard error page will be updated in WFCORE-4046 to be more generic.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10861) MP Health - security enabled, no user yed added, user get info about adding user to access management interface, HTTP code is 200, should be 500
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10861?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFLY-10861:
------------------------------
Summary: MP Health - security enabled, no user yed added, user get info about adding user to access management interface, HTTP code is 200, should be 500 (was: MP Health - security enabled, no user yed added, user get info about adding user to access web console, HTTP code is 200, should be 500)
> MP Health - security enabled, no user yed added, user get info about adding user to access management interface, HTTP code is 200, should be 500
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10861
> URL: https://issues.jboss.org/browse/WFLY-10861
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Health
> Reporter: Rostislav Svoboda
> Assignee: Kabir Khan
> Priority: Blocker
>
> I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server
> Note: I didn't add user via {{bin/add-user.sh}}
> ----
> Kabir edit: the full command is:
> /subsystem=microprofile-health-smallrye:write-attribute(name=security-enabled,value=true)
> ----
> When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console:
> {code}
> <h3>Your WildFly Application Server is running.</h3>
> <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able
> to access the admin console.</p>
> <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of
> your WildFly installation and enter the requested information.</p>
> {code}
> Can /health endpoint get customized response in case no mgmt user is defined on server side ?
> Current response can be little confusing if user is not yet so familiar with WildFly.
> I marked this as minor bug.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-95) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
by Clebert Suconic (JIRA)
[ https://issues.jboss.org/browse/WFWIP-95?page=com.atlassian.jira.plugin.s... ]
Clebert Suconic commented on WFWIP-95:
--------------------------------------
The only way to fix this is with System.properties.
I'm proposing using System properties, backed with a file named org.apache.activemq.Artemis.properties.
So, we will look for a System property org.apache.activemq.Artemis.enable1xPrefixes=true
it will be possible to also add a file org.apache.activemq.Artemis.properties and set the value to true. such file could exist on the classpath by default in Wildfly.
> [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
> -----------------------------------------------------------------------------
>
> Key: WFWIP-95
> URL: https://issues.jboss.org/browse/WFWIP-95
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq
>
> Having queue defined as follows
> {code:xml}
> <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/>
> {code}
> Client is instantiating it directly using its name.
> {code:title=Client}
> HashMap<String, Object> map = new HashMap<String, Object>();
> map.put("host", hostName);
> map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true);
> map.put("port", httpPort);
> TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map);
> try {
> ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration);
> Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue");
> connection = cf.createConnection();
> session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
> MessageProducer producer = session.createProducer(orderQueue);
> connection.start();
> ...
> {code}
> Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception
> {code}
> javax.jms.InvalidDestinationException: Destination InQueue does not exist
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326)
> {code}
> This is regression against EAP 7.1.0
> 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)
7 years, 11 months
[JBoss JIRA] (WFCORE-4041) ManagementRealm does now show plain-text attribute in default read-resource output
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4041?page=com.atlassian.jira.plugi... ]
Justin Cook reassigned WFCORE-4041:
-----------------------------------
Assignee: (was: Justin Cook)
> ManagementRealm does now show plain-text attribute in default read-resource output
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4041
> URL: https://issues.jboss.org/browse/WFCORE-4041
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Reporter: Justin Cook
>
> Currently running /subsystem=elytron/properties-realm=ManagementRealm:read-resource() results in the output:
> {code}
> {
> "outcome" => "success",
> "result" => {
> "groups-attribute" => "groups",
> "groups-properties" => {
> "path" => "mgmt-groups.properties",
> "relative-to" => "jboss.server.config.dir"
> },
> "users-properties" => {
> "path" => "mgmt-users.properties",
> "relative-to" => "jboss.server.config.dir",
> "digest-realm-name" => "ManagementRealm"
> }
> }
> }
> {code}
> which is missing the plain-text attribute
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-4046) Make the text in the console error context less console specific.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4046?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-4046.
------------------------------
Resolution: Won't Fix
Closing as Won't Fix as the mechanism for WFCORE-4045 (send error rather than redirect) doesn't actually load the page.
> Make the text in the console error context less console specific.
> -----------------------------------------------------------------
>
> Key: WFCORE-4046
> URL: https://issues.jboss.org/browse/WFCORE-4046
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Kabir Khan
> Assignee: Kabir Khan
>
> The text currently mentions
> {quote}
> However you have <strong>not</strong> yet <strong>added any users</strong> to be able to access the admin console.</p>
> {quote}
> which is too console specific as we now allow subsystems to register their own handlers via the ExtensibleHttpManagement.addManagementHandler() method. It will be changed to
> {quote}
> However you have <strong>not</strong> yet <strong>added any users</strong> to be able to access the HTTP management API.</p>
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-95) [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
by Bilge Ozpeynirci (JIRA)
[ https://issues.jboss.org/browse/WFWIP-95?page=com.atlassian.jira.plugin.s... ]
Bilge Ozpeynirci commented on WFWIP-95:
---------------------------------------
Unfortunately, it is not acceptable to expect a user to make a code change when upgrading to a minor EAP 7.* version.
I agree with [~bmaxwell] 's recommended action to deprecate it so that we can remove support in EAP Next.
> [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
> -----------------------------------------------------------------------------
>
> Key: WFWIP-95
> URL: https://issues.jboss.org/browse/WFWIP-95
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq
>
> Having queue defined as follows
> {code:xml}
> <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/>
> {code}
> Client is instantiating it directly using its name.
> {code:title=Client}
> HashMap<String, Object> map = new HashMap<String, Object>();
> map.put("host", hostName);
> map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true);
> map.put("port", httpPort);
> TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map);
> try {
> ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration);
> Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue");
> connection = cf.createConnection();
> session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
> MessageProducer producer = session.createProducer(orderQueue);
> connection.start();
> ...
> {code}
> Client is not able to send messages to, because {{session.createProducer(orderQueue)}} throws following exception
> {code}
> javax.jms.InvalidDestinationException: Destination InQueue does not exist
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326)
> {code}
> This is regression against EAP 7.1.0
> 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)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-2888 at 8/20/18 2:06 PM:
-------------------------------------------------------------------
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the structure of the data used in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the structure of the data used in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
was (Author: stetson.robinson):
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
For more information about DMN data types, see [Designing a decision service using DMN models|http://file.rdu.redhat.com/~sterobin/BXMSDOC-DMN_PAM/#dmn-data-typ...]. (Temporary link)
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-2888 at 8/20/18 1:52 PM:
-------------------------------------------------------------------
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
For more information about DMN data types, see [Designing a decision service using DMN models|http://file.rdu.redhat.com/~sterobin/BXMSDOC-DMN_PAM/#dmn-data-typ...].
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
was (Author: stetson.robinson):
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-2888 at 8/20/18 1:52 PM:
-------------------------------------------------------------------
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
For more information about DMN data types, see [Designing a decision service using DMN models|http://file.rdu.redhat.com/~sterobin/BXMSDOC-DMN_PAM/#dmn-data-typ...]. (Temporary link)
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
was (Author: stetson.robinson):
[~uxdlc], [~karreiro], Here's my proposed re-write of the data types help, based on my understanding:
Collapsed
"Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types." View more >>"
Expanded
Data types determine the input and output values in DMN decision tables. You can use basic data types (example, Boolean) or you can use this dialog to create custom data types."
Custom data types that you create in this dialog can be *Simple* or *Structured* data types:
• *Simple* data types have only a name and a type assignment. Example: "Age (Number)"
• *Structured* data types contain fields and are more complex. A single type "Person" may define a number of fields within it. Example: "name (String), age (Number), email (String)."
For more information about DMN data types, see [Designing a decision service using DMN models|http://file.rdu.redhat.com/~sterobin/BXMSDOC-DMN_PAM/#dmn-data-typ...].
View less >>
The main thing we want to watch for is passive, feature-centric language. We want instead user-centric language that speaks to the user and says exactly what the use can or must do.
Also, I'm not sure how we feel about linking to documentation from the UI, but our latest DMN document (to be retro-actively published to DM/PAM 7.0) describes each available data type and that will continue to be the case when this is released in 7.2. It won't be long before I have a fairly reliable 7.2 URL for that. I know with linking docs from UI there are gains (added info, doc promotion, better odds of user success) as well as losses (content out of sync, broken links) but it's a discussion that's being had around CCS. It sounds like there are ways to automate or otherwise facilitate the linking and syncing issue, but still a matter of optimal user success and opinion. This is also more prominent a discussion as community and product docs become single-sourced, and DMN will be the very first to do so :) I will be making this happen immediately after the new kie-docs repo structure is merged in the coming days/week-ish.
Just food for thought.
I should add also that we always want to specify "DMN decision tables", which are distinct (in supported features) from the guided or uploaded decision tables used elsewhere in the workbench. I know we know, but just a reminder for any communication to the user, to avoid confusion.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, previous.gif, viewMoreLess.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months