[
https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi...
]
Michael Anstis commented on DROOLS-3077:
----------------------------------------
[~karreiro] [~uxdlc] On the whole I think it looks good.
However; I think with {{Applicant.Age}} set as the input expression and the Data Type
{{Age}} the _existing_ constraint of {{[18..24]}} could be overridden *without* needing to
select a different or define a new Data Type. Furthermore I wonder whether the User should
_set_ the constraint rather than _add_ one (as they can only have one constraint).
Also, at the moment, if I change the Name or Data Type the change can be undone. However
(currently) changes to the Constraint definition cannot be undone. So we have a mis-match
of functionality. However we could change this so that clicking OK performs the actions
necessary to change the Name, Data-type and Constraint in such a way as they can be
undone. Changes made on the Data Types cannot be undone.
Finally, I wonder if adding the "OK", "Cancel" buttons to the
{{InputClause}} popover should be replicated to all popovers; otherwise some popovers will
continue to apply changes when (a) the "Name" {{TextBox}} looses focus, (b) when
a selection is made in the "Data Type" drop-down, (c) when the "OK"
button is clicked... just wondering.
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)