[JBoss JIRA] (DROOLS-2997) [DMN Designer] Add support for DMN v1.2
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2997?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2997:
-----------------------------------
Sprint: 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 42-44)
> [DMN Designer] Add support for DMN v1.2
> ---------------------------------------
>
> Key: DROOLS-2997
> URL: https://issues.jboss.org/browse/DROOLS-2997
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The DMN Editor needs to support DMN v1.2
> This requires enhancements to the marshalling and UI.
> More specifically we need both to support DMN v1.1 and v1.2 models and restrict the operations that can be performed by the User in the editor when handling a v1.1 model (the editor needs to support v1.2 operations).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2932) [DMN Designer] keyboard navigation in context grid editor
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2932?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2932:
-----------------------------------
Sprint: 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 42-44)
> [DMN Designer] keyboard navigation in context grid editor
> ---------------------------------------------------------
>
> Key: DROOLS-2932
> URL: https://issues.jboss.org/browse/DROOLS-2932
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User should be able to navigate between context grid editor cells by keyboard. We should implement standard navigation:
> - Move up: *arrow up*
> - Move left: *arrow left*
> - Move down: *arrow down*
> - Move right: *arrow right*
> Corner cases we need to address:
> - No cell selected
> -- -Select Top left cell if any arrow pressed?- left top cell selected by default
> - Multiple cells selected
> -- -Select Top left cell of current selected if any arrow pressed?- selection adjusted, no error thrown
> - Selected cell on the corner, no other cells in demanded way
> -- Keep selected the current cell
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2924:
-----------------------------------
Sprint: 2018 Week 33-35, 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 33-35, 2018 Week 42-44)
> Factor out Unit behavior to allow pluggable backends
> ----------------------------------------------------
>
> Key: DROOLS-2924
> URL: https://issues.jboss.org/browse/DROOLS-2924
> Project: Drools
> Issue Type: Task
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: Stunner, drools-core
>
> The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g.
> - rule units (Drools)
> - process units (jBPM)
> - etc.
> then the mechanism must allow for extensions.
> This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2563:
-----------------------------------
Sprint: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44)
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2569) [DMN Designer] Marshalling of magnet positions
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2569?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2569:
-----------------------------------
Sprint: 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 42-44)
> [DMN Designer] Marshalling of magnet positions
> ----------------------------------------------
>
> Key: DROOLS-2569
> URL: https://issues.jboss.org/browse/DROOLS-2569
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Labels: drools-tools
> Attachments: after_save.png, before_save.png
>
>
> When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML.
> [~tari_manga] could you please liaise with [~roger600] to understand where the issue is?
> h2. PR Acceptance test
> In DMN Designer, change magnet position in:
> - Source node
> -- BKM(/), BKS (/), Decision(/), Input (/)
> - Target node
> -- BKM(/), BKS(/), Decision (/), Annotation (x)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2989) Avoid refire of rules with synthetic Fact Handles
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2989?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2989:
-----------------------------------
Sprint: 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44)
> Avoid refire of rules with synthetic Fact Handles
> -------------------------------------------------
>
> Key: DROOLS-2989
> URL: https://issues.jboss.org/browse/DROOLS-2989
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Currently the FromNode and the AccumulateNode create "synthetic" fact handles, that means they're not serialized and they're recreated in memory each time we need the access.
> There's already a way to avoid the refiring of the rules but involves serializing and deserializing these synthetic Fact Handles without the objects.
> We now want a better way to do it by serializing the objects without their FactHandles and at the same time keep the same behaviour as before (same number of rules should fire)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3003) Enhance performance of PMML using decision trees
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3003?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3003:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 39-41, 2018 Week 42-44)
> Enhance performance of PMML using decision trees
> ------------------------------------------------
>
> Key: DROOLS-3003
> URL: https://issues.jboss.org/browse/DROOLS-3003
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
>
> Refactor the generation of rules and classes by the PMMLCompiler, for PMML resources containing Tree models.
> # Replace any remaining instances of types declared in rules files with POJOs
> # Reduce and/or remove the usage of rules in the process of generating rules and classes
> # Expose/make available the POJO that is generated from the MiningSchema, so that it can be used as input, instead of PMMLRequestData type
> # Update rules to make direct use of the input POJO
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3002) Enhance performance of PMML using scorecards
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3002?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3002:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47 (was: 2018 Week 39-41, 2018 Week 42-44)
> Enhance performance of PMML using scorecards
> --------------------------------------------
>
> Key: DROOLS-3002
> URL: https://issues.jboss.org/browse/DROOLS-3002
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
> Labels: 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
> # Make the generation of rules and classes be more direct (i.e. reduce/remove the rules engine use in generating rules and classes)
> # Reduce the rules generated so that the number of steps required to apply a model is minimized
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months