[JBoss JIRA] (DROOLS-3053) Warning dialog of column type change in Scenario grid
by Sarah Rambacher (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Sarah Rambacher commented on DROOLS-3053:
-----------------------------------------
Updated aria tags, so new rawgit: https://rawgit.com/srambach/BxMS-frontend/2e185285d846a25e2f6351bba863067...
> Warning dialog of column type change in Scenario grid
> -----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Final-WarningA.png, Final-WarningB.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3024:
--------------------------------------------
[~jomarko] I'm pretty sure that the issue above is related to refresh mechanism (after an update operation), which will be addressed by this JIRA https://issues.jboss.org/browse/DROOLS-3056. I'm going to link the DMN file there.
Thank you.
> [DMN Designer] Data Types - Add nested data types
> -------------------------------------------------
>
> Key: DROOLS-3024
> URL: https://issues.jboss.org/browse/DROOLS-3024
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, options.png
>
>
> - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
> !options.png|thumbnail!
> h2. Manual Acceptance Test
> h3. Insert above
> - on top level (/)
> - on the nested level (/)
> - on the deepest level (/)
> - no warning in browser console (/)
> h3. Insert below
> - on top level (/)
> - on the nested level (/)
> - on the deepest level (/)
> h3. Insert nested
> - on top level (/)
> - on the nested level (/)
> - on the deepest level (/)
> h3. Build and deploy
> - Build and deploy model that uses new created data type (x)
> -- DROOLS-3110
> -- DROOLS-3111
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning dialog of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
Thank you [~srambach], looks good to me - wdyt [~stetson.robinson]?
> Warning dialog of column type change in Scenario grid
> -----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Final-WarningA.png, Final-WarningB.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3095:
----------------------------------
Sprint: 2018 Week 42-44
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3112) FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper
by Edoardo Vacchi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3112?page=com.atlassian.jira.plugi... ]
Edoardo Vacchi commented on DROOLS-3112:
----------------------------------------
poker: 3
> FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper
> --------------------------------------------------------------------------
>
> Key: DROOLS-3112
> URL: https://issues.jboss.org/browse/DROOLS-3112
> Project: Drools
> Issue Type: Enhancement
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> Code in FEELImpl could be reused in the DMNFEELHelper, but it cannot be shared, because FEELImpl exposes an interface to evaluate expressions, while DMNFEELHelper needs access to the compiler backend.
> Solution: separate the compilation pipeline and the interpreter pipeline from the public FEEL interface to promote code reuse. In particular, CompilerBytecodeLoader can be probably split between some kind of CompiledUnit+CompiledUnaryTest impls that provide methods to retrieve Java source code and/or JVM bytecode.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months