[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3077: ------------------------------------- [~manstis] [~tirelli]K, I need some clarification on what was stated above ^^: 1) *Over-ride a Data Type*? _" 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. " _ * I believe [~tirelli] suggested that the management of +existing+ Data Type constraints should happen within the context of the Data Types list (Manage). 2)Multiple constraints? _"I wonder whether the User should set the constraint rather than add one (as they can only have one constraint)."_ * I thought the concept of "Input Constraints" was to ADD constraints and potentially further scope an existing Data Type constraint. 3) Undo? _"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."_ * Are you saying I need to add a remove or clear action to the design? 4) Pop-over consistency. "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." * This one I understand, and I agree. :) Although wrt (a) [~karreiro] and I were discussing this and IIRC agreed that the apply should happen on ENTER. But yes, now that the pop-overs are propagating we do need to align them, where applicable. Please assign any design jiras needed to me. :) -- This message was sent by Atlassian Jira (v7.12.1#712002)