[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-4270:
-------------------------------------------
[~bdellasc] There are some OPEN issues concerning the visual design solution, as a result of some design changes. The open issues are documented on slides 14 & 15 at: https://docs.google.com/presentation/d/1itceVe225mMtR55pqB-llpLNdU6kq4TBi.... Please let me know if you have any questions. :) Thanks
> Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
> -------------------------------------------------------------------
>
> Key: DROOLS-4270
> URL: https://issues.jboss.org/browse/DROOLS-4270
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area.
> Find is a local search that could be performed in these areas of the application:
> * Guided Decision Table editor (tables) - text strings within "Data cells"
> * DMN graph- text strings within canvas nodes.
> * DMN boxed expressions (logic) - text strings within "Data cells"
> Requirements
> * Colors, etc for partial and whole text strings will need to be highlighted is required.
> * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes.
> * Visual styles for the above if recommended.
> Considerations
> * Will not be able to leverage browser controls for Find.
> * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4270:
--------------------------------------
Sprint: 2019 Week 29-31
> Visual design: Highlighting treatment for GDST/DMN 7.5 Find results
> -------------------------------------------------------------------
>
> Key: DROOLS-4270
> URL: https://issues.jboss.org/browse/DROOLS-4270
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area.
> Find is a local search that could be performed in these areas of the application:
> * Guided Decision Table editor (tables) - text strings within "Data cells"
> * DMN graph- text strings within canvas nodes.
> * DMN boxed expressions (logic) - text strings within "Data cells"
> Requirements
> * Colors, etc for partial and whole text strings will need to be highlighted is required.
> * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes.
> * Visual styles for the above if recommended.
> Considerations
> * Will not be able to leverage browser controls for Find.
> * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster
by Richard Achmatowicz (Jira)
[ https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin... ]
Richard Achmatowicz updated WFLY-11833:
---------------------------------------
Attachment: test-debug-log.txt
> Stateful Session Bean affinity URI instead of cluster
> -----------------------------------------------------
>
> Key: WFLY-11833
> URL: https://issues.jboss.org/browse/WFLY-11833
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 16.0.0.Final
> Environment: WildFly cluster having SFSB deployed.
> Reporter: Joerg Baesner
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: downstream_dependency
> Attachments: stateful-timeout.zip, test-debug-log.txt
>
>
> Deployed is an application with the following setup:
> * Containing a SFSB (_with passivationCapable="true"_)
> * A SLSB exposing a _remote_ method to a standalone client returning an instance of the SFSB
> Scenario:
> A standalone client is invoking the _remote_ method on the Stateless Session Bean and a new instance of the Stateful Session Bean is returned.
> The issue is that the affinity of the returned Stateful Session Bean is URI instead of Cluster.
> See the attached Gradle reproducer application
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster
by Richard Achmatowicz (Jira)
[ https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin... ]
Richard Achmatowicz updated WFLY-11833:
---------------------------------------
Attachment: (was: test-debug-log.txt)
> Stateful Session Bean affinity URI instead of cluster
> -----------------------------------------------------
>
> Key: WFLY-11833
> URL: https://issues.jboss.org/browse/WFLY-11833
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 16.0.0.Final
> Environment: WildFly cluster having SFSB deployed.
> Reporter: Joerg Baesner
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: downstream_dependency
> Attachments: stateful-timeout.zip
>
>
> Deployed is an application with the following setup:
> * Containing a SFSB (_with passivationCapable="true"_)
> * A SLSB exposing a _remote_ method to a standalone client returning an instance of the SFSB
> Scenario:
> A standalone client is invoking the _remote_ method on the Stateless Session Bean and a new instance of the Stateful Session Bean is returned.
> The issue is that the affinity of the returned Stateful Session Bean is URI instead of Cluster.
> See the attached Gradle reproducer application
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service
by Amy Glass (Jira)
[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ]
Amy Glass commented on DROOLS-4161:
-----------------------------------
Hi [~zhutaojiajia] - I think it's close. but I was suggesting that you place the checkbox before the dropdown field, in a row *above* the field. Then when the user selects that checkbox, the drop-down field is enabled and the user can select the Decision service to use for testing. I added this comment to the Marvel as well. Thank you.
> 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)
7 years
[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service
by Tao Zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ]
Tao Zhu commented on DROOLS-4161:
---------------------------------
[~aglass] HI Amy, thanks for your feedback, I have updated the demo. Please have a review~
> 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)
7 years
[JBoss JIRA] (DROOLS-4342) Using BigDecimal with From Accumulate causes an "Error: argument type mismatch"
by Luca Molteni (Jira)
[ https://issues.jboss.org/browse/DROOLS-4342?page=com.atlassian.jira.plugi... ]
Luca Molteni reassigned DROOLS-4342:
------------------------------------
Assignee: Luca Molteni (was: Maciej Swiderski)
> Using BigDecimal with From Accumulate causes an "Error: argument type mismatch"
> -------------------------------------------------------------------------------
>
> Key: DROOLS-4342
> URL: https://issues.jboss.org/browse/DROOLS-4342
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Environment: Red Hat Process Automation Manager (RHPAM) 7.2.0
> Reporter: Rodrigo Ribeiro
> Assignee: Luca Molteni
> Priority: Major
> Labels: BigDecimal, DRL, bigdecimal, drl, kie-server, rhpam, rule
> Attachments: reproducer-02425606.zip, request.json, testSum.scenario
>
>
> When written a rule that does a sum using ‘from accumulate’. The rule validates successfully. However, when trying to test it, is returned a very generic error message: Error: argument type mismatch.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years