[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4484:
-----------------------------------
Sprint: 2019 Week 38-40 (from Sep 16), 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28) (was: 2019 Week 38-40 (from Sep 16), 2019 Week 41-43 (from Okt 7))
> [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism
> -----------------------------------------------------------------------------------------
>
> Key: DROOLS-4484
> URL: https://issues.jboss.org/browse/DROOLS-4484
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: issue1-drag-edit.webm, issue3-click-hide.webm, issue5-reorder-structure.webm, issue6-drag-used-type.webm, s1.gif, s2.gif, s3.gif, s4.gif, s5.gif
>
>
> This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list.
> *Acceptance criteria:*
> - The drag and drop feature must behaves as the following scenarios describe:
> -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany:
> !s1.gif|width=400!
> -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany:
> !s2.gif|width=400!
> -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type:
> !s3.gif|width=400!
> -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it:
> !s4.gif|width=400!
> -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model:
> !s5.gif|width=400!
> - The keyboard control can not be affected
> -- User need to be able start edit mode
> -- User need to be able finish/cancel edit mode
> - Search can not be affected
> - Imported data types are not editable
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-3002) Redo PMML scorecards rules to use executable model
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3002?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3002:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28) (was: 2019 Week 41-43 (from Okt 7))
> Redo PMML scorecards rules to use executable model
> --------------------------------------------------
>
> Key: DROOLS-3002
> URL: https://issues.jboss.org/browse/DROOLS-3002
> Project: Drools
> Issue Type: Enhancement
> Components: PMML
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
> Labels: PMMLRefactor, drools-core
>
> Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model.
> # Make further usage of POJOs to replace any types declared within the rule file
> # Change the rules generated so that the rules are Java, based on the executable model
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4449:
-----------------------------------
Sprint: 2019 Week 35-37, 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28) (was: 2019 Week 35-37, 2019 Week 41-43 (from Okt 7))
> Visual design enhancements: Scenario/DMN error overlays
> -------------------------------------------------------
>
> Key: DROOLS-4449
> URL: https://issues.jboss.org/browse/DROOLS-4449
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
> Attachments: ban-solid.svg, check-circle-regular.svg, check-circle-solid.svg, exclamation-circle-regular.svg, exclamation-circle-solid.svg
>
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Verification conditions:
> - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN)
> - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4522) Adding "expression" type handling
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4522:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28) (was: 2019 Week 41-43 (from Okt 7))
> Adding "expression" type handling
> ---------------------------------
>
> Key: DROOLS-4522
> URL: https://issues.jboss.org/browse/DROOLS-4522
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Attachments: can-be-suspended-expression.webm
>
>
> Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12717) Upgrade beantuils from 1.93 to 1.94
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-12717:
----------------------------------------
Summary: Upgrade beantuils from 1.93 to 1.94
Key: WFLY-12717
URL: https://issues.jboss.org/browse/WFLY-12717
Project: WildFly
Issue Type: Component Upgrade
Components: JMS
Affects Versions: 18.0.0.Final
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Upgrade Apache BeanUtils from 1.93. to 1.94
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12716) Upgrade Narayana to 5.10.0.Final
by Michael Musgrove (Jira)
Michael Musgrove created WFLY-12716:
---------------------------------------
Summary: Upgrade Narayana to 5.10.0.Final
Key: WFLY-12716
URL: https://issues.jboss.org/browse/WFLY-12716
Project: WildFly
Issue Type: Component Upgrade
Components: Transactions
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 19.0.0.Beta1
I will add a link to the release notes for 5.10.0.Final when I have created the release.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4522) Adding "expression" type handling
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-4522:
-------------------------------
Summary: Adding "expression" type handling (was: Add an "expression" property for every complex type in Scenario Testing)
> Adding "expression" type handling
> ---------------------------------
>
> Key: DROOLS-4522
> URL: https://issues.jboss.org/browse/DROOLS-4522
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Attachments: can-be-suspended-expression.webm
>
>
> Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months