[JBoss JIRA] (DROOLS-4307) Drools unable to compile rules when using a declared enum in the DRL file
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4307?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4307:
-----------------------------------
Sprint: 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 29-31, 2019 Week 32-34)
> Drools unable to compile rules when using a declared enum in the DRL file
> -------------------------------------------------------------------------
>
> Key: DROOLS-4307
> URL: https://issues.jboss.org/browse/DROOLS-4307
> Project: Drools
> Issue Type: Bug
> Reporter: Robert Buchmann
> Assignee: Luca Molteni
> Priority: Major
> Attachments: drl.zip
>
>
> I am finding inconsistent behaviour between drools reading rules from a local file (as a fileSystemResource) as opposed to pre compiling the rules into a kjar.
> This happens if I use an enum declared within the drl file in the "when" or "then" section of a rule within the same drl file.
> The rule runs perfectly as expected if I load the rule from the filesystem, but fails to run if I have pre-compiled the rule. For this reason I think this is a bug as I would expect the same behaviour for both ways of running rules.
> I outlined the problem in more detail stackoverflow:
> https://stackoverflow.com/questions/56989080/drools-maven-plugin-not-unde...
> This is running JAVA8 and drools 7.23.0.Final
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3944:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> DMN Editor: Data type usability study
> -------------------------------------
>
> Key: DROOLS-3944
> URL: https://issues.jboss.org/browse/DROOLS-3944
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Environment: Version 7.4
> Reporter: Elizabeth Clayton
> Assignee: Sarahjane Clark
> Priority: Major
> Labels: UX, UXTeam, Usability, drools-tools
>
> Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
> GOALS: Access the Data Type editor in terms of productivity and usability.
> * Ease of use when creating a complex type (concern: minimizing the mouse usage.)
> * Ease of use when saving a basic data type (e.g. age: number)
> * Discoverability of actions in the kebab menu, especially, insert nested, delete.
> * Ease of use/accuracy: Type-ahead of the data type selector.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3954) DM UX solutions for communicating errors in graphs & grids.
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3954?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3954:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> DM UX solutions for communicating errors in graphs & grids.
> ------------------------------------------------------------
>
> Key: DROOLS-3954
> URL: https://issues.jboss.org/browse/DROOLS-3954
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Margot Menestrot
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
>
> 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.
> Current DM context specific "design pattern" document: https://docs.google.com/document/d/1fX9K_fDjEO4_wDLK9EDDb0OtEFir7S6nFH9cn...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3957?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3957:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> Make verifier panel use docks
> -----------------------------
>
> Key: DROOLS-3957
> URL: https://issues.jboss.org/browse/DROOLS-3957
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: v&v.webm
>
>
> Pretty sure we had a ticket for this, but could not find it. Here it is.
> h3. Acceptance test
> On both Firefox and Chrome (x)
> - Opening multiple decision tables, switching between them
> - Repeated reopening of guided decision table
> - Opening other asset that uses docks - scenario, data object
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3879:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> Create Kogito version of Test Scenarios designer
> ------------------------------------------------
>
> Key: DROOLS-3879
> URL: https://issues.jboss.org/browse/DROOLS-3879
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Create the *Kogito* versions of scesim editor.
> No Home Page, no Library, No preferences, no other editors.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4102) Persist/reload Test Scenario table width/height
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4102?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4102:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 23-25, 2019 Week 29-31, 2019 Week 32-34)
> Persist/reload Test Scenario table width/height
> -----------------------------------------------
>
> Key: DROOLS-4102
> URL: https://issues.jboss.org/browse/DROOLS-4102
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: screencast-01-08-19-1.webm, screencast-02-08-19-1.webm, screencast-07-08-19-1.webm, screencast-07-08-19-2.webm, screencast-07-08-19-3.webm
>
>
> Implement a mechanism to store/restore column width ({{FactMapping}}) and row height ({{Scenario}}) for the table in Test Scenario.
> Please consider:
> - Create/save a simulation (default column width/row height in scesim)
> - Rename a simulation (it perform a save/reload)
> - Change column type (recreate the column)
> - Duplicate column (preserve same size)
> - -Duplicate row (preserve same size)-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months