October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1969) [DMN Editor] Check that variables are accessible just by parent nodes

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1969?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3282 to DROOLS-1969: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1969 (was: GUVNOR-3282) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Check that variables are accessible just by parent nodes > --------------------------------------------------------------------- > > Key: DROOLS-1969 > URL: https://issues.jboss.org/browse/DROOLS-1969 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > Each node of DRD represents a variable. Each such variable should be accessible just by parent nodes in the tree hierarchy. > Acceptance criteria: > - Define scenarios which will assert this behavior > - Try/implement these scenarios > - Possibly file found issues -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

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

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1970?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3255 to DROOLS-1970: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1970 (was: GUVNOR-3255) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Affects Version/s: 7.1.0.Beta2 (was: 7.1.0.Beta2) Fix Version/s: 7.5.0.Final (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 > Fix For: 7.5.0.Final > > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1971) [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1971?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3272 to DROOLS-1971: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1971 (was: GUVNOR-3272) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape > --------------------------------------------------------------------------- > > Key: DROOLS-1971 > URL: https://issues.jboss.org/browse/DROOLS-1971 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.5.0.Final > > > See:- > 1) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 2) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 3) <conan> manstis you want to extend {{AbstractOffsetMultiPointShape}} not {{AbstractDirectionalMultiPointShape}} as {{AbstractDirectionalMultiPointShape}} has 3 attributes, only applicable to orthogonal lines. you have neither a direction nor a direction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1972) [DMN Editor] Canvas Zooming

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1972?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3265 to DROOLS-1972: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1972 (was: GUVNOR-3265) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Canvas Zooming > --------------------------- > > Key: DROOLS-1972 > URL: https://issues.jboss.org/browse/DROOLS-1972 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > The DMN Editor should support zooming in/out the DRD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1959) [DMN Editor] Extend marshaller support for Expressions

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1959?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3353 to DROOLS-1959: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1959 (was: GUVNOR-3353) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) > [DMN Editor] Extend marshaller support for Expressions > ------------------------------------------------------ > > Key: DROOLS-1959 > URL: https://issues.jboss.org/browse/DROOLS-1959 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > When UI support for DMN Expression is available, the marshaller shall be extended to support marshalling between DMN xml and the stunner representation of the expression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1960) [DMN Editor] Check decision table output label

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1960?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3304 to DROOLS-1960: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1960 (was: GUVNOR-3304) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Check decision table output label > ---------------------------------------------- > > Key: DROOLS-1960 > URL: https://issues.jboss.org/browse/DROOLS-1960 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > The Decision table output label should equal either to variable name (decision table name) or to BKM name if some connected to the decision table (decision node). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1961) [DMN Editor] Export documentation

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1961?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3256 to DROOLS-1961: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1961 (was: GUVNOR-3256) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Affects Version/s: 7.1.0.Beta2 (was: 7.1.0.Beta2) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Export documentation > --------------------------------- > > Key: DROOLS-1961 > URL: https://issues.jboss.org/browse/DROOLS-1961 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > There should be option to export documentation (PDF probably?) that could contain more information than picture of diagram. Details of particular Elements? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

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

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3283 to DROOLS-1962: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1962 (was: GUVNOR-3283) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (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 > Fix For: 7.5.0.Final > > > "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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1963) [DMN Editor] Move from Errai DOM wrappers to Elemental2

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1963?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3436 to DROOLS-1963: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1963 (was: GUVNOR-3436) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) > [DMN Editor] Move from Errai DOM wrappers to Elemental2 > ------------------------------------------------------- > > Key: DROOLS-1963 > URL: https://issues.jboss.org/browse/DROOLS-1963 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > See "Support for Elemental 2 in Errai" email to BSIG.. > The DMN Editor targets 8.x and is therefore a candidate to launch with Elemental 2 support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1964) [DMN Editor] Input Data typeRef

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1964?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3302 to DROOLS-1964: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1964 (was: GUVNOR-3302) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Input Data typeRef > ------------------------------- > > Key: DROOLS-1964 > URL: https://issues.jboss.org/browse/DROOLS-1964 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > The Input Data nodes specifies the datatype via _typeRef_ attribute. Allowed are simple datatypes, enumerations of allowed values and complex data types like Person. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 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 October 2017