Feature Request: add Confirmation Message capabilities to a!dynamicLink()

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Wed, 28 Jun 2023 15:46:50 GMT

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.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Fri, 18 Nov 2022 17:46:44 GMT

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.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

davel001150 — Thu, 29 Aug 2019 17:25:15 GMT

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.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Thu, 29 Aug 2019 16:04:40 GMT

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).

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Jacob Edelman — Wed, 14 Aug 2019 19:45:49 GMT

Adding to this feature request: https://community.appian.com/discussions/f/general/17461/safe-link-with-confirmation---leaving-application/68832#68832

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

sayalip — Thu, 13 Jun 2019 09:10:00 GMT

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!

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Thu, 06 Jun 2019 14:01:08 GMT

This issue isn't really related to this thread as far as I can tell - I would suggest you start a new Community thread to discuss this, and/or create a case with Appian Support.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

davel001150 — Thu, 06 Jun 2019 13:37:44 GMT

From a pure usability standpoint it's just good to make error difficult and/or recovery easy wherever possible. Even in a case where a change is reversible, but it's a lengthy process to do so or requires an undue interruption (like needing to start a separate action or a related action on a completely different type of record), it would be good to have a confirmation message to mitigate the action from occurring in error.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Ravi Roshan — Thu, 06 Jun 2019 08:56:13 GMT

We are facing few issues on Confirmation Message. Scenario is like:

Based on the selection of Grid, i need to do some calculation on data, which i am doing on grid's saveinto. The issue is if I select few rows and click on button i get correct confirmation message, however if click on cancel and quickly select some other selection (For which confirmation message will be different), and I click again to the button (Progress bar is still in progress), i did not get the change confirmation message. This is definitely lagging issue.

Is there any solution for this, we have tried maximum possible code optimization.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Wed, 05 Jun 2019 18:51:39 GMT

That's a primary use case, especially if we boil it down to the "do something they can't reverse" part (or perhaps, 'commit to a particular action' or similar), though there are probably other use cases where it would provide an extra benefit to require the user to confirm before the saveInto of a link executes.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Rachel Rater — Wed, 05 Jun 2019 18:45:37 GMT

I understand where you're coming from. I'm looking for the reasons why you felt it was important to have the safety net of the confirmation message. Only when the user is about to delete data or otherwise do something they can't reverse?

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Wed, 05 Jun 2019 18:40:50 GMT

Dynamic links can do a lot - from setting or clearing local / rule input variable values, to directly writing, altering or deleting data in the database via inline smart service functions like a!writeToDataStoreEntity. I know I've personally run into more small or nich use cases than this in my development experience which I have long since forgotten the details of - and at many times I've had to choose between either being able to use rich text / link components, and being forced to use a (non-submitting) Button Widget just so I can have the safety net of a confirmation popup message. To me it's artificially restrictive to force us to make these compromises.

I realize that the evolutionary paths of the different components have been separate and/or disconnected (i.e. no links had this functionality at all until the SubmitLink was introduced), but now as the SAIL feature set has become more rich and components have been enhanced with greater flexibility, this particular item has started standing out more and more to me as a functionality gap.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Rachel Rater — Wed, 05 Jun 2019 18:31:55 GMT

Thanks for bringing it up. I see one use case here - inline grid row deletions. What are some of your other use cases where it's important to provide the user a confirmation option?

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

davel001150 — Tue, 28 May 2019 13:24:55 GMT

No reason in my mind not to provide more options with the ability to choose not to use them.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Mike Schmitt — Fri, 24 May 2019 17:49:33 GMT

That's exactly one of the use cases I was thinking of, too.

RE: Feature Request: add Confirmation Message capabilities to a!dynamicLink()

Tim — Fri, 24 May 2019 17:36:04 GMT

Good call Mike. +1 from me on this! Would be useful on inline grid row deletions too.