[JBoss JIRA] (DROOLS-3000) Design data type constraints UX
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3000:
-----------------------------------
Sprint: 2018 Week 33-35, 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 33-35, 2018 Week 48-50)
> Design data type constraints UX
> --------------------------------
>
> Key: DROOLS-3000
> URL: https://issues.jboss.org/browse/DROOLS-3000
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3286) [DMN Designer] FunctionGrid: Move F, J, P selector to header
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3286?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3286:
-----------------------------------
Sprint: 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 48-50)
> [DMN Designer] FunctionGrid: Move F, J, P selector to header
> -------------------------------------------------------------
>
> Key: DROOLS-3286
> URL: https://issues.jboss.org/browse/DROOLS-3286
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}!
> Also, the default in classes should be String, not Undefined.
> The cell that shows function parameters also needs to show the text "Select parameters" when there is none parameter added and the parameters when there is parameters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3283:
-----------------------------------
Sprint: 2018 Week 45-47, 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 45-47, 2018 Week 48-50)
> Incorrect V&V results when operator is filled in the row (as opposed to column definition)
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3283
> URL: https://issues.jboss.org/browse/DROOLS-3283
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.14.0.Final
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, support
>
> Imagine data model Person with attribute age.
> If you create decision table and add two columns:
> - both are defined against "age" attribute
> - none of them have operator defined
> then you add one row, and you fill in the operator and the value directly inside the row.
> For example:
> >= 20
> <= 30
> The generated DRL looks like this:
> {code:java}
> package org;
> //from row number: 1
> rule "Row 1 AnotherTest"
> dialect "mvel"
> when
> p : Person( age >= 20 , age <= 30 )
> then
> p.setAgeGroup( "whatever" );
> end
> {code}
> The V&V will report this as conflicting row:
> !6iOx.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3175) [DMN Designer] keyboard context menu invocation
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3175?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3175:
-----------------------------------
Sprint: 2018 Week 42-44, 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 42-44, 2018 Week 48-50)
> [DMN Designer] keyboard context menu invocation
> -----------------------------------------------
>
> Key: DROOLS-3175
> URL: https://issues.jboss.org/browse/DROOLS-3175
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3131) [DMN Designer] Data Types - Add Item inconsistency
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3131?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3131:
-----------------------------------
Sprint: 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 48-50)
> [DMN Designer] Data Types - Add Item inconsistency
> --------------------------------------------------
>
> Key: DROOLS-3131
> URL: https://issues.jboss.org/browse/DROOLS-3131
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
>
> *Prerequisite:*
> - Existing DMN model
> *Step to reproduce:*
> - Open manage custom data type dialog
> - Click blue *Add* button
> - Added entry will be immediately in edit mode to allow user change name and type
> - Now click Insert Below, Insert Above or Insert Nested next to any entry
> - Added entry won't be in edit mode
> *Expected scenario:*
> - Adding entries either via blue *Add* button or entries context menu options should be consistent
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3307) Refactor jBPM out of Drools core
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3307?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3307:
-----------------------------------
Sprint: 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 48-50)
> Refactor jBPM out of Drools core
> --------------------------------
>
> Key: DROOLS-3307
> URL: https://issues.jboss.org/browse/DROOLS-3307
> Project: Drools
> Issue Type: Enhancement
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> Use the Assembler/Weaver mechanism to move jBPM out of drools core
> other notes:
> current impl exposes both drools-specific and jbpm-specific methods
> core should not account for the underlying type: we'd rather give a wrapper or a common super-type instead of a different map for rules and processes.
> aim for API like:
> {code} kpg.get(Rules.class).getRules() {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months