[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3022:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
> h2. Manaul Acceptance Test
> - Try to put same name by Typing (/)
> - Try to put same name by Copy and paste (/)
> - Do not allow empty name (/)
> - Allow spaces in name (/)
> - Allow multibyte chars in name (/)
> - Allow special characters in name (/)
> - Allow lower upper case in name (/)
> - Save when error shown (/)
> - Cancel edit when error shown (/)
> - Invoke other edit when error shown (/)
> -- https://github.com/kiegroup/kie-wb-common/pull/2161#issuecomment-427978978
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3023:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: prototype.png
>
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
> h2. Manual acceptance test
> Check warning list all occurrences:
> - Remove item definition used as part of other item definitions (/)
> -- Top level, all occurences removed
> -- Nested level, top level definition remains
> - Remove item definitions used as output data-type for decision node (x)
> - Remove item definition used as data-type for expression element (column, parameter, ...) (x)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3124) Nested GridCell/GridCellValue
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3124?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3124:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> Nested GridCell/GridCellValue
> -----------------------------
>
> Key: DROOLS-3124
> URL: https://issues.jboss.org/browse/DROOLS-3124
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-12 10-10-01.png
>
>
> For some click/double click combination (not easy to reproduce) inside a gridcell, it seems that a nested GridCell or gridcellvallue will be created:
> in the screenshot it is shown by the empty box inside the cell below do2.mydo1.myint1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2910) [DMN Designer] All grid cell editing should respond to single click
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-2910?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2910:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> [DMN Designer] All grid cell editing should respond to single click
> --------------------------------------------------------------------
>
> Key: DROOLS-2910
> URL: https://issues.jboss.org/browse/DROOLS-2910
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
>
> Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click.
> h2. Manual Acceptance Test
> - Not possible edit multiple cells by hold CTRL and click on multiple cells
> - Click column/row leading cell discard edit dialog
> - Edit can be discarded by escape
> - Edit can be discarded by click to canvas
> - Invoke edit of cell, return do DRG
> - Save and reopen
> - Undo redo of editation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 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 (was: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41)
> [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, 7 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 (was: 2018 Week 36-38, 2018 Week 39-41)
> 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, 7 months