January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1814) Guided Decision Table V&V reporting - detect redundancy for rows differing only in bound vars

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1814?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1814: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Guided Decision Table V&V reporting - detect redundancy for rows differing only in bound vars > --------------------------------------------------------------------------------------------- > > Key: DROOLS-1814 > URL: https://issues.jboss.org/browse/DROOLS-1814 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe, verifier > > The following 2 rows/rules from one GDT are redundant but not detected as such. The reason is that one operates with a fact bound to variable 'p', the other binds the same fact to variable 'q'. It would be nice, if things like this were detected as well. > rule "Row 1 asd" > when > p : Person( age > 0 ) > then > p.setSth( 0 ); > end > rule "Row 2 asd" > when > q : Person( age > 0 ) > then > q.setSth( 0 ); > end -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1818) Guided Decision Table V&V reporting - Analysis panel visual improvements

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1818?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1818: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Guided Decision Table V&V reporting - Analysis panel visual improvements > ------------------------------------------------------------------------ > > Key: DROOLS-1818 > URL: https://issues.jboss.org/browse/DROOLS-1818 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe, verifier > > The part of the panel with the issue description has a 60px padding - this is a bit too much. It leaves less space for the actual text, which then often has to be scrolled. > There is also an unusual line-height of 30px for a font-size of 18px. This makes the text hog even more space, quite unnecessarily. > The 'Affected rows' line blends in with the description itself. It could do with a pixel or two (or 5) more of space underneath - together with the removal the 30px line-height, this could set it nicely apart without disrupting anything else. > There are only 5 rows of issues displayed in the top part of the Analysis panel, but even in small guided DTs, there can easily be many more issues. Giving this part more space should be easier after resolving the points above. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1824) Guided Decision Table V&V - Make the V&V pick up salience & activation-group

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1824?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1824: --------------------------------- Labels: verifier (was: ) > Guided Decision Table V&V - Make the V&V pick up salience & activation-group > ---------------------------------------------------------------------------- > > Key: DROOLS-1824 > URL: https://issues.jboss.org/browse/DROOLS-1824 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > Either the one set in the table or the ones added with code generation based on Hit Policy. > Made the ticket, but not sure if salience changes anything with what we resolve at the moment. It does affect loop detection, but we do not handle that at the moment > * If two rules are subsumptant. The order of the rows does not matter, they are still subsumptant > * If two rules are in conflict. The order does not matter. > Saliance with activation-group however does change things. > * If a rule's LHS with a higher priority subsumes a rule with a lower priority. The lower row never fires. > * We do not care about conflicting rows in activation-group > Due to PHREAK, we always have top to down salience or a salience set by the user. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1826) Guided Decision Table V&V: Overlaps

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1826?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1826: --------------------------------- Labels: verifier (was: ) > Guided Decision Table V&V: Overlaps > ----------------------------------- > > Key: DROOLS-1826 > URL: https://issues.jboss.org/browse/DROOLS-1826 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > This will be needed by Unique hit to resolve if table is in fact Unique Singe hit. > We already resolve subsumption. Meaning all the possible values that row A can take also satisfy B. > Subsumption does not cover overlapping rows. Where a set of given values that fire A also fire B, but both rules have a range of given values that only fire A or B. > h6. For example > || Person.age || Application.approve || > | 0 - 50 | yes | > | 40 - 100 | no | > If age is between 40 and 50 both rules fire and it is impossible to say if the rule is approved or not. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1825: --------------------------------- Labels: UX UXTeam drools-tools verifier (was: UX UXTeam drools-tools) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX, UXTeam, drools-tools, verifier > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1839) Guided Decision Table V&V - Unused attributes

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1839?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1839: --------------------------------- Labels: verifier (was: ) > Guided Decision Table V&V - Unused attributes > --------------------------------------------- > > Key: DROOLS-1839 > URL: https://issues.jboss.org/browse/DROOLS-1839 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > We check if a field "status" has the enum values WAITING or DECLINED in the LHS, but never if it is OK. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1857) Guided Decision Table V&V - Finding Missing Ranges and Rows

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1857?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1857: --------------------------------- Labels: verifier (was: ) > Guided Decision Table V&V - Finding Missing Ranges and Rows > ------------------------------------------------------------ > > Key: DROOLS-1857 > URL: https://issues.jboss.org/browse/DROOLS-1857 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1857) Guided Decision Table V&V - Finding Missing Ranges and Rows

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1857?page=com.atlassian.jira.plugi... ] Toni Rikkola resolved DROOLS-1857. ---------------------------------- Resolution: Done > Guided Decision Table V&V - Finding Missing Ranges and Rows > ------------------------------------------------------------ > > Key: DROOLS-1857 > URL: https://issues.jboss.org/browse/DROOLS-1857 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1978) Test Scenarios: Expecting empty facts does not work

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1978?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1978. -------------------------------- Resolution: Won't Do > Test Scenarios: Expecting empty facts does not work > --------------------------------------------------- > > Key: DROOLS-1978 > URL: https://issues.jboss.org/browse/DROOLS-1978 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > > Create a test that checks if a Fact exists. > Create a rule that inserts this Fact. > Run the scenario and it fails. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1979) Test Scenario: Activated rule flow does not work if the test scenario is restricted to a single rule

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1979?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1979. -------------------------------- Resolution: Won't Do > Test Scenario: Activated rule flow does not work if the test scenario is restricted to a single rule > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1979 > URL: https://issues.jboss.org/browse/DROOLS-1979 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 January 2019