[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2922:
-----------------------------------
Story Points: 3 (was: 2)
> CSS: Pop-over menu for DMN decision tables.
> -------------------------------------------
>
> Key: DROOLS-2922
> URL: https://issues.jboss.org/browse/DROOLS-2922
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, pop-overcSpecs.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases from the DMN canvas view, as a user I want to:
> * Search a list of available data types from a decision table, as part of an input/selection process.
> * Select a data type inline from a decision table.
> * Have a means to rename the Decision (node.)
> * Have a means to access the Manage Data Types dialog.
> Notes:
> Design requires a Pop-over, which includes:
> * Form field labels for usability (context) and accessibility.
> * Variant 1 of the PF pop-over patterns, which supports a the pop-up title.
> * Drop down component with Live Search
> * "Manage" link opens a dialog.
> * Pop-up is initiated by a single-left mouse click within the respective decision table cell.
> * Design needs to be reasonably consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2804) [DMN Designer] Properties Panel to drill-down to DMN component level
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2804:
-----------------------------------
Story Points: 5 (was: 13)
> [DMN Designer] Properties Panel to drill-down to DMN component level
> --------------------------------------------------------------------
>
> Key: DROOLS-2804
> URL: https://issues.jboss.org/browse/DROOLS-2804
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> h3. Literal expression
> ||Selected item||Properties panel items||
> |Cell|(?)|
> h3. Context
> ||Selected item||Properties panel items||
> |Row|(?)|
> |Column|(?)|
> |Cell|(?)|
> h3. Decision Table
> ||Selected item||Properties panel items||
> |Row|(?)|
> |Column|(?)|
> |Cell|(?)|
> h3. Relation
> ||Selected item||Properties panel items||
> |Row|(?)|
> |Column|(?)|
> |Cell|(?)|
> h3. Function
> ||Selected item||Properties panel items||
> |Row|(?)|
> |Column|(?)|
> |Cell|(?)|
> h3. Invocation
> ||Selected item||Properties panel items||
> |Row|(?)|
> |Column|(?)|
> |Cell|(?)|
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2922:
-----------------------------------
Sprint: 2018 Week 39-41
> CSS: Pop-over menu for DMN decision tables.
> -------------------------------------------
>
> Key: DROOLS-2922
> URL: https://issues.jboss.org/browse/DROOLS-2922
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, pop-overcSpecs.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases from the DMN canvas view, as a user I want to:
> * Search a list of available data types from a decision table, as part of an input/selection process.
> * Select a data type inline from a decision table.
> * Have a means to rename the Decision (node.)
> * Have a means to access the Manage Data Types dialog.
> Notes:
> Design requires a Pop-over, which includes:
> * Form field labels for usability (context) and accessibility.
> * Variant 1 of the PF pop-over patterns, which supports a the pop-up title.
> * Drop down component with Live Search
> * "Manage" link opens a dialog.
> * Pop-up is initiated by a single-left mouse click within the respective decision table cell.
> * Design needs to be reasonably consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JGRP-2295) Add local Operation System DNS resolver implementation
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created JGRP-2295:
-----------------------------------------
Summary: Add local Operation System DNS resolver implementation
Key: JGRP-2295
URL: https://issues.jboss.org/browse/JGRP-2295
Project: JGroups
Issue Type: Feature Request
Reporter: Sebastian Łaskawiec
Assignee: Bela Ban
The {{DefaultDNSResolver}} queries the DNS server and extracts values it returned. There's however another approach - query the local OS DNS resolver. This approach has some advantages because it takes both {{/etc/hosts}} as well as {{/etc/resolv.conf}} files under consideration. We should provide an {{OSDNSResolver}} implementation that would do it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JGRP-2295) Add local Operation System DNS resolver implementation
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/JGRP-2295?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec reassigned JGRP-2295:
-----------------------------------------
Assignee: Sebastian Łaskawiec (was: Bela Ban)
> Add local Operation System DNS resolver implementation
> ------------------------------------------------------
>
> Key: JGRP-2295
> URL: https://issues.jboss.org/browse/JGRP-2295
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> The {{DefaultDNSResolver}} queries the DNS server and extracts values it returned. There's however another approach - query the local OS DNS resolver. This approach has some advantages because it takes both {{/etc/hosts}} as well as {{/etc/resolv.conf}} files under consideration. We should provide an {{OSDNSResolver}} implementation that would do it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3004) FEEL Parser: refactor `not` unary negation and `not` function call; fix support to wildcard `?`
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-3004:
-----------------------------------
Summary: FEEL Parser: refactor `not` unary negation and `not` function call; fix support to wildcard `?`
Key: DROOLS-3004
URL: https://issues.jboss.org/browse/DROOLS-3004
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
*list contains([1,2,3,4,5,6], 3)* returns true
*not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false
Most likely related to an issue with the parse tree branches
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months