April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2974) [DMN Designer] Code Enhancements

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-2974?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-2974: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Code Enhancements > -------------------------------- > > Key: DROOLS-2974 > URL: https://issues.redhat.com/browse/DROOLS-2974 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Purpose of this requirement is to collect issues for code enhancements. These enhancements can't be usually seen by end user however could improve app performance... > Due to the above, not setting target release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4037) [DMN Designer] Remove white-space from Names

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4037?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4037: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Remove white-space from Names > --------------------------------------------- > > Key: DROOLS-4037 > URL: https://issues.redhat.com/browse/DROOLS-4037 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Further to the discussion on https://issues.jboss.org/browse/JBPM-7117 the DMN marshaller should remove white-space from {{Name}} values when loading and saving a model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2942) DMN Editor UX/visual enhancements

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-2942?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-2942: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > DMN Editor UX/visual enhancements > --------------------------------- > > Key: DROOLS-2942 > URL: https://issues.redhat.com/browse/DROOLS-2942 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UX-CSS, UXTeam, drools-tools > > Variety of jiras which support improving the overall look and feel of the DMN editor, specifically wrt to palette, table, and "navigator enhancements. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3200) [DMN Designer] Properties Panel Hints

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3200?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3200: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Properties Panel Hints > ------------------------------------- > > Key: DROOLS-3200 > URL: https://issues.redhat.com/browse/DROOLS-3200 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Following DROOLS-3145 we need to identify most important fields set via properties panel and provide hints directly in the properties panel to support self-documentary product effort. > The hints should shortly explain the fields and provide sample valid values if applicable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3657) [DMN Designer] Highlight invalid DRGElements

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3657?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3657: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Highlight invalid DRGElements > -------------------------------------------- > > Key: DROOLS-3657 > URL: https://issues.redhat.com/browse/DROOLS-3657 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Whenever a DMN file is validated (be it when the Project is compiled or via the Validate button on the toolbar) the DMN editor should highlight issues reported by the validation. This should include DRG nodes (on the graph view) or DRGElements (in the Boxed Expression, aka grid, view). The nature of the highlighting is to be defined; but probably consists of an orange background for warnings and red background for errors; possibly both with a warning triangle positioned somewhere. UX will need engaging for design proposals. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5054) DMN Editor does not cascade allowedValues for Decision Table input

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5054?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5054: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > DMN Editor does not cascade allowedValues for Decision Table input > ------------------------------------------------------------------ > > Key: DROOLS-5054 > URL: https://issues.redhat.com/browse/DROOLS-5054 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Traffic Violation (1).dmn > > > Following the Traffic Violation tutorial, e.g.: https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.... > Despite {{Violation.Type}} is defined as a constraint enumeration: > {code:xml} > <dmn:itemComponent id="_D16710C9-F626-4351-ABCE-C7F0A1A82F70" name="Type" isCollection="false"> > <dmn:typeRef>string</dmn:typeRef> > <dmn:allowedValues kie:constraintType="enumeration" id="_C4AFEF49-331A-4A9F-B9AF-478DB7525008"> > <dmn:text>"speed", "parking", "driving under the influence"</dmn:text> > </dmn:allowedValues> > </dmn:itemComponent> > {code} > the constraints are not cascaded down to the Decision Table input: > {code:xml} > <dmn:input id="_CD3B3323-7C98-44CB-802E-F3A52A4364CC"> > <dmn:inputExpression id="_621CEBEF-0710-4474-AFC3-D305517A348F" typeRef="string"> > <dmn:text>Violation.Type</dmn:text> > </dmn:inputExpression> > </dmn:input> > {code} > and this does not allow for the Decision Table static analysis to be perfomed (the static analysis reckognize these values seems to be enumerated, but the decision table column does not list them) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3288?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3288: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-3288 > URL: https://issues.redhat.com/browse/DROOLS-3288 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: diagram.png, dtable.png, steps.gif > > > When the user persists the following diagram: > !diagram.png|thumbnail! > ..with the following Decision Table: > !dtable.png|thumbnail! > ..and change the Input Node type, the type in the Decision Table does not change. > *Steps to reproduce* > !steps.gif|thumbnail! > *Expected behaviour* > Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] Add visual indicators for imported Nodes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3907?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3907: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Add visual indicators for imported Nodes > ------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.redhat.com/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1943) [DMN Editor] Association: Add support for AssociationDirection

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-1943?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-1943: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Editor] Association: Add support for AssociationDirection > -------------------------------------------------------------- > > Key: DROOLS-1943 > URL: https://issues.redhat.com/browse/DROOLS-1943 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Edson Tirelli > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > The DMN Editor only supports creating {{Association}} *from* a DRG Element *to* a {{TextAnnotation}}. The DMN Specification however provides for the {{Association}} to have a direction (either from-DRG-to-TA, or from-TA-to-DRG or both). > When implementing the UI model {{AssociationDirection}} was omitted as I thought it's direction could be inferred from the source and target nodes. However this may not be entirely accurate (for the "both" direction). Furthermore the UI currently does not support creating an {{Association}} from a {{TextAnnotation}}. > [~tirelli] [~tari_manga] FYI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3169?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3169: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Last Context Entry differentiation > ------------------------------------------------- > > Key: DROOLS-3169 > URL: https://issues.redhat.com/browse/DROOLS-3169 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot 2018-10-23 18.37.56.png, Screenshot from 2018-10-22 17-35-07.png > > > The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change. > We should improve this in one of the following ways: > - Keep name *Default*, change font to italics and use grey background color > - Merge the *Default* and *Value* cells of last entry and remove the name *Default* -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020