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

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.

  • a!submitLink has the ability to define confirmation message parameters in a way analogous to the ButtonWidget
  • However, other SAIL link styles do not have this capability
  • Therefore, I request that the same parameters be added to a!dynamicLink(), as well as perhaps certain other link types such as Start Process Link and Task Link
  • This would allow us to more fully utilize the various SAIL link components (especially paired with Rich Text and Card Layouts) in places where we might currently be forced to stick to ButtonWidgets.

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

Parents
  • 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".

    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.

Reply
  • 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".

    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.

Children