January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3454: -------------------------------- Attachment: (was: range-redo.png) > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, kebab.png, range.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 tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3565) DMN: Navigator panel UX updates

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3565: ---------------------------------------- [~uxdlc] I think, at best, all we can commit to now is that it could be plausible to re-use the Form Modeller palette code. We would not want to have a dependency in DMN on Form Modeller so unless their existing code is eminently re-usable we may not be able to re-use it without some effort in refactoring. Also, we could only plausibly re-use the palette part and not the drag and drop from palette to the editor as Stunner and Form Modeller use different technologies: Form Modeller is all HTML whereas Stunner is part HTML, part Canvas, part Frankenstein! When we get to implement "import" we'd be able to make a better judgement call as to what we could re-use (we can obviously make DMN's component palette look like anything we choose... so we could _borrow_ some HTML from Form Modeller for the palette's appearance.. but this is not re-use as you ask; but duplication). > DMN: Navigator panel UX updates > ------------------------------- > > Key: DROOLS-3565 > URL: https://issues.jboss.org/browse/DROOLS-3565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png > > > As a user I want to be able to be able to view and use imported nodes and decision logic in the diagram that I am authoring. > Based on card view design (see linked jira), detail new Navigator elements required to support this workflow including: > - Import components panel: Filter components by BKMs, decisions..., badge count > - Graph panel with checkbox option to view map. > - Single scrolling navigator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3454: -------------------------------- Attachment: range-redo.png > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, kebab.png, range-redo.png, range.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 tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3454: --------------------------------------- Reopening because for "days and time duration" values, the user can input and combination of days, hours, minutes and seconds. 2 days -> valid 2 days and 2 minutes -> valid 2 hours and 50 minutes and 20 seconds -> valid 2 hours and 40 seconds -> valid etc > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, kebab.png, range.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 tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3454) Data type constraints: Day/Time Duration

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3454?page=com.atlassian.jira.plugi... ] Edson Tirelli reopened DROOLS-3454: ----------------------------------- > Data type constraints: Day/Time Duration > ---------------------------------------- > > Key: DROOLS-3454 > URL: https://issues.jboss.org/browse/DROOLS-3454 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, kebab.png, range.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 tab - as a user I want the ability to define constraints for the following types: Day/Time Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2008) Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-2008?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2008: --------------------------------------- [~danielezonca] for core rules, this is a requirement Daniele as per Toni's comment. For DMN, I don't think we need it. > Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed > --------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2008 > URL: https://issues.jboss.org/browse/DROOLS-2008 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Andrea Lee > Assignee: Toni Rikkola > Priority: Minor > > Example scenario: > Existing Rules: Rule A, Rule B, Rule C. > Test Scenario expectation: Expect Rule A to fire once. > I would like to have the ability to specify that this Test Scenario should fail if any other rule in addition to Rule A is fired WITHOUT having to specify the following additional expectations: Expect Rule B to not fire, Expect Rule C to not fire. > I have posted this in the user mailing list as well: http://n3.nabble.com/Guvnor-Test-Scenario-Expectations-td722429.html#a722429 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3525) Data type constraints: Expression help text.

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3525?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3525: --------------------------------------- Looks fine to me. > Data type constraints: Expression help text. > -------------------------------------------- > > Key: DROOLS-3525 > URL: https://issues.jboss.org/browse/DROOLS-3525 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Stetson Robinson > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Help-Text.png, expression.png > > > Background > Persona: Business analyst or Rules practitioner > *Use Cases:* > As a user I want inline help text for defining Expression constraints, so that I am guided in formatting the the expression using the correct syntax. . > *Note, applies to: > - Number > - Day/Time Duration > - Year/Mos Duration > - Date/Time > - Date > - Time > *Verification conditions:* > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Edson Tirelli reopened DROOLS-3455: ----------------------------------- > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range.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 tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3455: --------------------------------------- Sorry I missed this before, but an "Years and Months duration" allows the user to input a number of years and a number of months on the same duration value, with the caveat that both are optional. 4 years -> valid 3 years and 5 months -> valid 6 months -> valid It is also valid to enter a number of months higher than 11, but the engine is supposed to normalize that internally. 18 months -> valid, but the spec requires the engine to normalize that to "1 year and 6 months" Reopening the ticket. > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range.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 tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3565) DMN: Navigator panel UX updates

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3565: ------------------------------------- [~karreiro][~manstis] I had envisioned that the Components palette would use drag-n-drop similar to the form modeler. Just wondering if you'll be reusing any of that code or presentation? !Screen Shot 2019-01-28 at 2.35.00 PM.png|thumbnail! > DMN: Navigator panel UX updates > ------------------------------- > > Key: DROOLS-3565 > URL: https://issues.jboss.org/browse/DROOLS-3565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png > > > As a user I want to be able to be able to view and use imported nodes and decision logic in the diagram that I am authoring. > Based on card view design (see linked jira), detail new Navigator elements required to support this workflow including: > - Import components panel: Filter components by BKMs, decisions..., badge count > - Graph panel with checkbox option to view map. > - Single scrolling navigator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019