Use Case: There are numerous valid use cases where a confirmation message pop-up is useful even when not submitting a form. Case in point, we are currently able to do this using the ButtonWidget component(s) even when not configured to submit.
I look forward to hearing from anyone else who might agree with this, and/or if anyone has any further comments or questions.
Thanks!
Discussion posts and replies are publicly visible
Even I have a use case in my current project which a "confirmation message upon click of a link" would sort out. I say this is much needed. Thanks Mike for requesting this feature!
Adding to this feature request: https://community.appian.com/discussions/f/general/17461/safe-link-with-confirmation---leaving-application/68832#68832
I agree - I even came up with a new use case a few weeks ago: a paging grid with many pages and user selections; i like to have a dynamic link which the user can click to clear all selections, but there is no way to have a confirmation pop-up to keep them from clicking it by accident (as i would be able to do with a non-submitting button).
Hey I can tack something on right there. Let's say you're doing a paging grid with multiple pages of selections, and you make dozens of selections then click something to perform an operation on each of them.
There's no way to conveniently display all the items that have been selected, but a confirmation box could show all your selections and confirm you want to perform said operation on all of them. You might have fat fingered one on the first page you didn't intend; you could cancel, deselect that one, then run it again.
While this feature request remains mired in the product enhancement backlog (and maybe not even there? we have no way of knowing...) it's still being requested by users (probably more than just the one linked thread, but this one just reminded me). If anyone at Appian is watching, this is one of those things that I'm thinking of every time I bring up "feature-completeness quality-of-life features that consistently go ignored".
Suvajit Gupta this is but one of the things I was referring to when I talked to you in person last month at the fall event at HQ. Things with a (presumably) low dev effort, no real impact on or removal of existing functionality, and fills a feature-completeness gap that's been a minor-but-frequent pain point for many of us, for... well, several years now at least.
April Schuppel - i think this is a good example of the sort of thing you were asking me about the other day, if it's useful to you at all at this point.