[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2109:
-------------------------------------
As shown in the screenshots form 2018-02-21, there is needed additional refactoring for these assets.
> [XLS Decision Table] New Asset Dialogue misses descriptions
> -----------------------------------------------------------
>
> Key: DROOLS-2109
> URL: https://issues.jboss.org/browse/DROOLS-2109
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Affects Versions: 7.5.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Optional
> Attachments: Screenshot from 2017-11-03 10-20-21.png, Screenshot from 2018-02-21 17-30-29.png, Screenshot from 2018-02-21 17-30-38.png, Screenshot from 2018-02-21 17-30-51.png, Screenshot from 2018-02-21 17-31-12.png, Screenshot from 2018-02-21 17-31-56.png, Screenshot from 2018-02-21 17-32-25.png, Screenshot from 2018-02-21 17-33-00.png, Screenshot from 2018-02-21 17-33-57.png, Screenshot from 2018-02-21 17-34-22.png
>
>
> The attached dialogue shows missing descriptions for table format and file selector.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2109:
--------------------------------
Attachment: Screenshot from 2018-02-21 17-34-22.png
Screenshot from 2018-02-21 17-33-57.png
Screenshot from 2018-02-21 17-33-00.png
Screenshot from 2018-02-21 17-32-25.png
Screenshot from 2018-02-21 17-31-56.png
Screenshot from 2018-02-21 17-31-12.png
Screenshot from 2018-02-21 17-30-51.png
Screenshot from 2018-02-21 17-30-38.png
Screenshot from 2018-02-21 17-30-29.png
> [XLS Decision Table] New Asset Dialogue misses descriptions
> -----------------------------------------------------------
>
> Key: DROOLS-2109
> URL: https://issues.jboss.org/browse/DROOLS-2109
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Affects Versions: 7.5.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Optional
> Attachments: Screenshot from 2017-11-03 10-20-21.png, Screenshot from 2018-02-21 17-30-29.png, Screenshot from 2018-02-21 17-30-38.png, Screenshot from 2018-02-21 17-30-51.png, Screenshot from 2018-02-21 17-31-12.png, Screenshot from 2018-02-21 17-31-56.png, Screenshot from 2018-02-21 17-32-25.png, Screenshot from 2018-02-21 17-33-00.png, Screenshot from 2018-02-21 17-33-57.png, Screenshot from 2018-02-21 17-34-22.png
>
>
> The attached dialogue shows missing descriptions for table format and file selector.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (DROOLS-2184) UX design DRD logic table actions
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2184?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2184:
-------------------------------------
Interactive wireframes at: https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/43bdff12/design/DMN/index....
> UX design DRD logic table actions
> ---------------------------------
>
> Key: DROOLS-2184
> URL: https://issues.jboss.org/browse/DROOLS-2184
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
> Attachments: Logic_2184_Feb18.pdf, Screen Shot 2018-01-19 at 3.22.25 PM.png, Screen Shot 2018-01-19 at 3.23.31 PM.png, kebab-where.png
>
>
> Use case description:
As a business user (Citizen Developer…), I want to easily create, edit, and refine business decision logic (tables, expressions, boxed expression, etc.) Note: Using inline controls and employ autocomplete capabilities where possible.
> Verification Conditions
> * The user of this feature is able to easily/quickly perform key actions (Add, Remove, Edit) in logic tables, boxed expressions, and the like.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (WFLY-9744) Improve Infinispan subsystem model descriptions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9744?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9744:
--------------------------------------
I have implemented WFLY-9743 to show deprecation more clearly in wildscribe.
> Improve Infinispan subsystem model descriptions
> ------------------------------------------------
>
> Key: WFLY-9744
> URL: https://issues.jboss.org/browse/WFLY-9744
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
>
> In order to not duplicate documentation in docs/ and wildscribe, we will link from documentation to wildscribe. This requires descriptions to be improved. The descriptions:
> * should describe behavior
> * should avoid using domain model terminology (e.g. attributes, child)
> * take out the redundant verb such as 'configures' (unless appropriate, e.g. in operation desc.)
> Upon completion, we can remove the sections from documentation and link.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JGRP-2112) Sticky site masters
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/JGRP-2112?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on JGRP-2112:
-------------------------------------------
This probably can't happen if the sites use Load Balancers as frontends. This way you will never send a message from C (LON) to C1 and C2 (NYC).
> Sticky site masters
> -------------------
>
> Key: JGRP-2112
> URL: https://issues.jboss.org/browse/JGRP-2112
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.12, 4.0
>
>
> If members in one site send messages to site masters of other sites, if we have multiple site masters, then reordering can occur.
> Example:
> * Member C in site LON sends messages C1 and C2 to site NYC
> * C1 picks SM1 and C2 picks SM2
> * Although site masters process messages in delivery order, because C1 and C2 travel through different site masters, C2 could pass C1, leading to ordering issues
> h4. Design
> * When sending a message to the one of the site masters of the current site, or from a site master to a remote site master, we invoke a callback to pick the site master based on the original caller
> * Note that this only applies when we have more than one site master.
> * The callback passes the address of the original caller and the list of available site masters, and needs to return a site master
> h5. Transactions
> * Transactions by different originators with overlapping key sets cannot be reliably ordered
> * Transactional support therefore requires single site masters
> * This should not be an issue as transactions bundle multiple updates, so the number of messages sent is less than non-transactional updates
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months