dzonca@redhat.com karreiro_ gcardosi I got some feedback from etirelli@redhat.com that the on-click approach might not be good for some of our business use cases. So I created an alternative on-hover solution. But to address the keyboard accessibility concerns that were raised I pulled the actions (copy, view alerts) out of the popover. Here's an updated click-thru: https://marvelapp.com/66j6fei

update to "on-click" from on hover.

etirelli@redhat.com gcardosi I'm reopening this design jira, to update the behavior to launch the pop-over from on-hover to on-click. I met with srambach and bdellasc to discuss this concern, and are agreed that this is the recommended behavior from the UX perspective (it will best support usability and PF consistency.)

I need to update this click-thru as well as the Scenario ones that mmenestr created to reflect this change. And I'll document the basic keyboard requirements for this feature as well. The presentation in these overlays will require a refactoring of the Scenario solution though, to make it consistent. << dzonca@redhat.com will you need a jira for that work?

karreiro_ Marking as resolved per team review. cc. gcardosi

karreiro_ etirelli@redhat.com mmenestr I updated the click-thru with the changes we discussed:

• Added a Clear button (it's a toggle state of the Validate button.)
• Provided a summary tally for the error message with a link to Alert details.
  The Marvel mockup posted above reflects these changes. bdellasc FYI ^^
  I'll demo it next meeting, to see if I can mark this issue Resolved.

mmenestrkarreiro_ I've updated the click-thru with the changes we discussed:

• Using an alert inside the canvas node, and removing the badge from outside of it.
• Changed the canvas overlay from a tooltip to a popover.
• Changed the popover interaction from initiating on click to on hover.
  Other than that: Made some adjustments to the messaging inside the dialog.

karreiro_ mmenestr etirelli@redhat.com I've attached a click-thru ( in the "Marvel " section above) with a first pass at just the Validation scenario portion of the flow. I will post the Scenario test version next.

• One addition to this that karreiro_ and I were discussing was to add a (modeless) dialog after hitting the Validate button that would show the user a summary of the validation errors, and could also show the progress indicator while it's processing. Just an idea, if this sounds useful, I'll mock it up next. Please post comments, thanks!

dzonca@redhat.com Okay thanks. When you are ready to look at it, it would be good to fold in bdellasc to see if we can enhance the visual presentation to make sure the final solution is accessible to all users.

rhn-support-eclayton
For me is the same, I don't have a strong opinion about that and I don't know what is technically feasible on DMN editor side. I expect is doable but I think this will be evaluated in a further phase

tzhu@redhat.com Are you or dzonca@redhat.com planning to use a redundant visual cue to indicate error state - or is it just color alone?