November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1962) [DMN Editor] Decision service

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1962: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Decision service > ----------------------------- > > Key: DROOLS-1962 > URL: https://issues.jboss.org/browse/DROOLS-1962 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Trivial > Labels: reported-by-qe > > "In DRD it is rounded rectangle that surrounds all of the encapsulated decisions in the service. The inputs to the service are defined by all of the information requirements leading into the rounded rectangle. The outputs of the service are the decisions shown above the straight line bisecting the rounded rectangle. If there is no such line, all encapsulated decisions are exposed in the service output." cited form DMN Method and Style, Chapter 3, Decision Requirements -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1954) [DMN Editor] Keyboard shortcuts

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1954?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1954: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Keyboard shortcuts > ------------------------------- > > Key: DROOLS-1954 > URL: https://issues.jboss.org/browse/DROOLS-1954 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The DMN editor could support keyboard shortcuts (similar for current GDT tables) for basic operations like editing of DRD elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1975) [DMN Editor] Test marshalling of Decision

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1975?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1975: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Test marshalling of Decision > ----------------------------------------- > > Key: DROOLS-1975 > URL: https://issues.jboss.org/browse/DROOLS-1975 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > > Test that marshalling of Decision preserves all properties specific for the Decision. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1970) [DMN Editor] Hit policies

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1970?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1970: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Hit policies > ------------------------- > > Key: DROOLS-1970 > URL: https://issues.jboss.org/browse/DROOLS-1970 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > Implement hit policies of the DMN Specification: > - Unique (Single hit policy) > -- No overlap is possible and all rules are disjoint. Only a single rule can be matched. This is the default. > - First (Single hit policy) > -- Multiple (overlapping) rules can match, with different output entries. The first hit by rule order is returned (and > evaluation can halt). This is still a common usage, because it resolves inconsistencies by forcing the first hit. > However, first hit tables are not considered good practice because they do not offer a clear overview of the decision > logic. It is important to distinguish this type of table from others because the meaning depends on the order of the > rules. The last rule is often the catch-remainder. Because of this order, the table is hard to validate manually and > therefore has to be used with care. > - Priority (Single hit policy) > -- Multiple rules can match, with different output entries. This policy returns the matching rule with the > highest output priority. Output priorities are specified in the ordered list of output values, in decreasing order of > priority. Note that priorities are independent from rule sequence. > - Any (Single hit policy) > -- There may be overlap, but all of the matching rules show equal output entries for each output, so any match can > be used. If the output entries are non-equal, the hit policy is incorrect and the result is undefined. > - Output Order (Multiple hit policy) > -- returns all hits in decreasing output priority order. Output priorities are specified in the ordered list of > output values in decreasing order of priority. > - Rule Order (Multiple hit policy) > -- Returns all hits in rule order. Note: the meaning may depend on the sequence of the rules. > - Collect ( Multple hit policy with the aggregation operators +, >, < and #) > -- Returns all hits in arbitrary order. An operator (‘+’, ‘<’, ‘>’, ‘#’) can be added to apply a simple function to the outputs. If no operator is present, the result is the list of all the output entries. Collect operators are: > a) + (sum): the result of the decision table is the sum of all the distinct outputs. > b) < (min): the result of the decision table is the smallest value of all the outputs. > c) > (max): the result of the decision table is the largest value of all the outputs. > d) # (count): the result of the decision table is the number of distinct outputs. > Other policies, such as more complex manipulations on the outputs, can be performed by post-processing the > output list (outside the decision table). > Please ensure that the HIT policy can be changed whenever during modeling the decision table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1942: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1965) [DMN Editor] Test marshalling of BKM

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1965?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1965: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Test marshalling of BKM > ------------------------------------ > > Key: DROOLS-1965 > URL: https://issues.jboss.org/browse/DROOLS-1965 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > > Test that marshalling of BKM preserves all properties specific for the BKM. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1953) [DMN Editor] Show Subset of DRD nodes

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1953?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1953: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Show Subset of DRD nodes > ------------------------------------- > > Key: DROOLS-1953 > URL: https://issues.jboss.org/browse/DROOLS-1953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The editor will contain feature that shows just subset of DRD nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1944) [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1944?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1944: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1944 > URL: https://issues.jboss.org/browse/DROOLS-1944 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The "Toolbox" currently has a number of different "connector" icons; one for each type of connector that can emanate from the selected "source" node. [~tirelli] requested we have only one generic "connector" icon and the type of the created connector depends on the target node. This probably has an impact on the command being executed during drag move and drag complete. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1966) [DMN Editor] Ensure UI model has hashCode/equals implementations

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1966?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1966: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Ensure UI model has hashCode/equals implementations > ---------------------------------------------------------------- > > Key: DROOLS-1966 > URL: https://issues.jboss.org/browse/DROOLS-1966 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > See https://github.com/kiegroup/kie-wb-common/pull/920 (for Stunner's implementation). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1957) [DMN Editor] Syntax validation

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1957?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1957: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Syntax validation > ------------------------------ > > Key: DROOLS-1957 > URL: https://issues.jboss.org/browse/DROOLS-1957 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > The DMN editor should support syntax validation, it means if the generated XML can be compiled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2017