[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3406:
----------------------------------------
All going good [~roger600]; but I have a question.
Do I have to _map_ Lienzo/Wires events (in response to drag/move/resize etc) in {{WiresShapeViewExt.addHandler(..)}} to Stunner {{ViewHandler}}?
I have some new Lienzo/Wires events being raised for moving the "splitter" that I _can_ handle in my new {{AbstractCanvasHandlerRegistrationControl}} implementation (to get access to a {{CommandManager}} etc) however looking at existing code it looks like I should have {{WiresShapeViewExt.addHandler(..)}} handle the Lienzo/Wires event and re-raise as a Stunner {{ViewHandler}} event... problem is that moving the "splitter" cannot re-use one of the existing {{ViewEventType}} and adding a new type seems more effort than it's worth (since it's an {{enum}}).
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3446:
-------------------------------------
[~tirelli] [~karreiro] [~manstis] I created this scoped jira for the goal of defining the "generic" workflow for defining constraints (regardless of type.) According to the original Epic there are two contexts from which the user will need to define the data type:
A) Data type list/tab.
B) from the DMN canvas view (Decision table.)
I have some questions about B, will follow-up on IM. But have an initial proposal for the interaction from the Data type tab, illustrated in this click thru: https://redhat.invisionapp.com/share/D5PPHAI8PAG#/screens.
I think using a dialog will allow the user to better focus on the task of defining constraints, which can be fairly involved. Let me know what you think, thanks!
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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 data type definitions in use in my file.
> 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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3446:
--------------------------------
Description:
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 data type definitions in use in my file.
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.
was:
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 supported data types, documented at: https://docs.google.com/document/d/1513XNFw4uRtSQJ_iAMcose9B7Mje0NUG0Mng7...
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.
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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 data type definitions in use in my file.
> 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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Description:
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: Date (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.
was:
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: Date
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.
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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: Date (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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Story Points: 3 (was: 5)
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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: Date
> 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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3445:
--------------------------------
Summary: Data type constraints: Date (was: Date-related data type constraints)
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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: Date
> 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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3446:
--------------------------------
Description:
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 supported data types, documented at: https://docs.google.com/document/d/1513XNFw4uRtSQJ_iAMcose9B7Mje0NUG0Mng7...
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.
was:
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: Date
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.
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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 supported data types, documented at: https://docs.google.com/document/d/1513XNFw4uRtSQJ_iAMcose9B7Mje0NUG0Mng7...
> 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)
5 years, 6 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3446:
-----------------------------------
Summary: Data type constraints: Basic interaction/workflow
Key: DROOLS-3446
URL: https://issues.jboss.org/browse/DROOLS-3446
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
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: Date
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)
5 years, 6 months