[JBoss JIRA] (DROOLS-1770) More FEEL runtime cycle detection tests
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1770?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1770:
-----------------------------------
Sprint: 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 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50)
> More FEEL runtime cycle detection tests
> ---------------------------------------
>
> Key: DROOLS-1770
> URL: https://issues.jboss.org/browse/DROOLS-1770
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.4.1.Final
> Reporter: Fedor Gavrilov
> Assignee: Fedor Gavrilov
> Priority: Minor
>
> Runtime cycle detecton lacks tests for false positive, such as deadly diamond topology:
> A depends on B and C
> B and C depend on D
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[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, 4 months
[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, 4 months
[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, 4 months
[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, 4 months
[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, 4 months