[
https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi...
]
Liz Clayton commented on DROOLS-3077:
-------------------------------------
[~karreiro] [~manstis]
The latest direction for the Input Clause pop-over is:
https://redhat.invisionapp.com/share/8BQRVFUVU3Z#/349667215_Input1
(this is a rough version, still need to do some clean-up, but it shows the basic flow).
The basic changes are as follows:
* Explicit Save/Cancel buttons.
* If user enters a Data Type that has constraints already applied to them, they are
displayed as read-only. The user will need Add more constraints by going through the Data
Type (a story for another sprint.) In this case on the Manage link is available for that
action.
* If the user select a type without constraints, then they can add constraints via this
pop-over. The otherwise hidden Action to Add is enabled (presented). Clicking that will
open a dialog for just adding to the Input clause. The user enter the values and
round-trip back to the pop-over for confirmation before saving. Once saved the table is
updated. Wdyt?
Enhance data type restrictions UX - Decision Table/properties
-------------------------------------------------------------
Key: DROOLS-3077
URL:
https://issues.jboss.org/browse/DROOLS-3077
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)