July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2609) Implement decision table analysis as DMN validator extension

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2609?page=com.atlassian.jira.plugi... ] Fedor Gavrilov reassigned DROOLS-2609: -------------------------------------- Assignee: Matteo Mortari (was: Fedor Gavrilov) > Implement decision table analysis as DMN validator extension > ------------------------------------------------------------ > > Key: DROOLS-2609 > URL: https://issues.jboss.org/browse/DROOLS-2609 > Project: Drools > Issue Type: Enhancement > Reporter: Fedor Gavrilov > Assignee: Matteo Mortari > Attachments: Algorithms for Decision Table Analysis.docx > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2721) [DMN Designer] InputData node can not be connected to BKM node

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2721?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2721: ---------------------------------------- Rejecting and closing as BKM's cannot be connected with {{InformationRequirement}}. The OMG DMNv1.1 Specification states: {quote} 6.2.2.1 Information Requirement notation Information Requirements may be drawn from Input Data elements to Decisions, and from Decisions to other Decisions. They represent the dependency of a Decision on information from input data or the results of other Decisions... {quote} > [DMN Designer] InputData node can not be connected to BKM node > -------------------------------------------------------------- > > Key: DROOLS-2721 > URL: https://issues.jboss.org/browse/DROOLS-2721 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.9.0.Final > > > User is unable to connect InputData node with BKM node. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2721) [DMN Designer] InputData node can not be connected to BKM node

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2721?page=com.atlassian.jira.plugi... ] Michael Anstis reopened DROOLS-2721: ------------------------------------ > [DMN Designer] InputData node can not be connected to BKM node > -------------------------------------------------------------- > > Key: DROOLS-2721 > URL: https://issues.jboss.org/browse/DROOLS-2721 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.9.0.Final > > > User is unable to connect InputData node with BKM node. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2721) [DMN Designer] InputData node can not be connected to BKM node

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2721?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2721. ------------------------------------ Resolution: Rejected > [DMN Designer] InputData node can not be connected to BKM node > -------------------------------------------------------------- > > Key: DROOLS-2721 > URL: https://issues.jboss.org/browse/DROOLS-2721 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.9.0.Final > > > User is unable to connect InputData node with BKM node. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2655: ----------------------------------- Description: [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}} containing the {{DecisionTable}} expression. For example, if a {{Decision}} has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a {{Decision}} has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. - For simple data types the input column names should correspond exactly to InputData elements. - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... h3. PR Manual Acceptance Test - Check Decision Table Decision node, with inputs (/) - Check Decision Table Decision node, without inputs (/) - Check Non Decision Table Decision node (/) was: [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}} containing the {{DecisionTable}} expression. For example, if a {{Decision}} has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a {{Decision}} has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. - For simple data types the input column names should correspond exactly to InputData elements. - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... h3. PR Manual Acceptance Test - Check Decision Table Decision node, with inputs (/) - Check Decision Table Decision node, without inputs (/) - Check Decision Table BKM node, with inputs (x) DROOLS-2721 - Check Decision Table BKM node, without inputs (x) DROOLS-2721 - Check Non Decision Table Decision/BKM node (/) > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}} containing the {{DecisionTable}} expression. For example, if a {{Decision}} has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a {{Decision}} has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. > - For simple data types the input column names should correspond exactly to InputData elements. > - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... > h3. PR Manual Acceptance Test > - Check Decision Table Decision node, with inputs (/) > - Check Decision Table Decision node, without inputs (/) > - Check Non Decision Table Decision node (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2655: ----------------------------------- Description: [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}} containing the {{DecisionTable}} expression. For example, if a {{Decision}} has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a {{Decision}} has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. - For simple data types the input column names should correspond exactly to InputData elements. - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... h3. PR Manual Acceptance Test - Check Decision Table Decision node, with inputs (/) - Check Decision Table Decision node, without inputs (/) - Check Decision Table BKM node, with inputs (x) DROOLS-2721 - Check Decision Table BKM node, without inputs (x) DROOLS-2721 - Check Non Decision Table Decision/BKM node (/) was: [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. - For simple data types the input column names should correspond exactly to InputData elements. - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... h3. PR Manual Acceptance Test - Check Decision Table Decision node, with inputs (/) - Check Decision Table Decision node, without inputs (/) - Check Decision Table BKM node, with inputs (x) DROOLS-2721 - Check Decision Table BKM node, without inputs (x) DROOLS-2721 - Check Non Decision Table Decision/BKM node (/) > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}} containing the {{DecisionTable}} expression. For example, if a {{Decision}} has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a {{Decision}} has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. > - For simple data types the input column names should correspond exactly to InputData elements. > - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... > h3. PR Manual Acceptance Test > - Check Decision Table Decision node, with inputs (/) > - Check Decision Table Decision node, without inputs (/) > - Check Decision Table BKM node, with inputs (x) DROOLS-2721 > - Check Decision Table BKM node, without inputs (x) DROOLS-2721 > - Check Non Decision Table Decision/BKM node (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1299) DROOLS-778 is back with 6.4.0

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1299?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1299. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/59bb794b7 > DROOLS-778 is back with 6.4.0 > ----------------------------- > > Key: DROOLS-1299 > URL: https://issues.jboss.org/browse/DROOLS-1299 > Project: Drools > Issue Type: Sub-task > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Christoph Schachinger > Assignee: Mario Fusco > Fix For: 6.0.0.Final > > > Issue DROOLS-778 is back again with version 6.4.0.FINAL -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1280: --------------------------------------- Not sure if this is still actual, so assigning to Gaurav. > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Reporter: Matteo Mortari > Assignee: Gaurav Dey > Priority: Minor > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Flow charts and state diagrams > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-1280: ---------------------------------- Component/s: docs > further document state machine, thread-safety and include diagrams > ------------------------------------------------------------------ > > Key: DROOLS-1280 > URL: https://issues.jboss.org/browse/DROOLS-1280 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Gaurav Dey > Priority: Minor > > Spin-off remaining linked documentation work from [DROOLS-1272] for: > Include docs on state machine and thread safety > Flow charts and state diagrams > Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1273) document Rule Evaluation Modes

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1273?page=com.atlassian.jira.plugi... ] Tibor Zimányi edited comment on DROOLS-1273 at 7/12/18 4:04 AM: ---------------------------------------------------------------- Not sure if this is still relevant, so assigning to Gaurav. was (Author: tzimanyi): Not sure if this is still relevant, however assigning to Gaurav. > document Rule Evaluation Modes > ------------------------------ > > Key: DROOLS-1273 > URL: https://issues.jboss.org/browse/DROOLS-1273 > Project: Drools > Issue Type: Enhancement > Components: docs > Reporter: Matteo Mortari > Assignee: Gaurav Dey > Priority: Minor > > documents Immediate, Eager and Lazy annotations. As well as the ForceImmedateFilter api. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018