December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2149) Row and column can be added to read only table

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2149?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2149: ----------------------------------- Sprint: 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 49-50) > Row and column can be added to read only table > ---------------------------------------------- > > Key: DROOLS-2149 > URL: https://issues.jboss.org/browse/DROOLS-2149 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.4.1.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.6.0.Final > > > The options for adding row or column into guided decision table are not disabled correctly in special case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2154?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2154: ----------------------------------- Sprint: 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 49-50) > Design navigation between the DRG and DRD's > ------------------------------------------- > > Key: DROOLS-2154 > URL: https://issues.jboss.org/browse/DROOLS-2154 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2017-12-15 at 10.16.33 AM.png > > > *Use case description: * > As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. > *Requirements:* > * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". > *Verification Conditions* > * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. > * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1959?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1959: ----------------------------------- Sprint: 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > [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

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > FEEL code generation and compilation > ------------------------------------ > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > [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 > 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.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2175) [Guided Decision Table Graph] Refresh after removal of table

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2175?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2175: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 36-37, 2017 Week 49-50) > [Guided Decision Table Graph] Refresh after removal of table > ------------------------------------------------------------ > > Key: DROOLS-2175 > URL: https://issues.jboss.org/browse/DROOLS-2175 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.3.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > There are two problem after removal one of linked tables. For more details see Steps to Reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.6.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3464) Fix build for JDK10

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-3464: ----------------------------------- Summary: Fix build for JDK10 Key: WFCORE-3464 URL: https://issues.jboss.org/browse/WFCORE-3464 Project: WildFly Core Issue Type: Enhancement Components: Domain Management, Scripts, Server Environment: JDK10 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently we have quite few issues when running on JDK10. it mostly looks related to version detection code that fails to properly detect 10. same goes for many dependent components. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017