Skip to main content
July 9, 2021
Question

Feature Request: allow the use of a link behind a button. (eg to start a process using a!startProcessLink() inside a button)

  • July 9, 2021
  • 6 replies
  • 1 view

It would be nice it it would be possible to allow a link to be configured inside a button.
Currently a button only has a saveInto. If you want to launch a worklfow form a button you are limited to using a!startProcess(). This method only allows for headless processes to be launched.
If you want to launch a process with a process startform, you need to used the  a!startProcessLink(), but there is no way to configure this when using a button.

Example usecase:

Imagine you have a custom grid of objects.
You want the users to be able to select one or more objects. Based on the selection you will show the possible actions to use above the grid. A nice way to display these actions is by using buttons.

If one of these actions involves a process with a process start form, there is no way to configure this using a button. You can however just just a link, but it wil nog look as clean.

    6 replies

    selvakumark
    Participating Frequently
    July 9, 2021

    Hi [mention:8a41fde900214ab7bd1eea37d674ba20:e9ed411860ed4f2ba0265705b8793d05],

    Maybe you can make use of the record action field - by adding your process as a related action to a record and show the actions as per the style guide below:

    docs.appian.com/.../ux_record_actions.html

    I hope this workaround might help you!

    maartencAuthor
    July 9, 2021

    Hi Selvakumar,

    Thanks for your reply.

    We already use that workaround in other cases. The problem with this is that you can only launch this record action for a single selection.

    When you want to have the possibility to select multiple objects this workaround won't work.

    selvakumark
    Participating Frequently
    July 9, 2021

    Hi Maarten, 

    Have you tried using a card layout(with rich text inside) and applying the start process link over the card layout? With the recent padding customizations added to the card layout, we can try to make it look like a button.

    davel001150
    July 14, 2021

    I most heartily agree with this request.  There are many functions that simply can't be performed easily with a button, that can performed quite easily with any other object type.

    Use Case:  Client wants to start a process when you click on a button.  You have to tell them Appian can't do that.  You have to click on a card, boxLayout, grid cell, richText, Stamp, Tag, or almost anything else in the entire platform, but not a button.  They insist that you figure out how to make it a button.

    mikes0011
    Brainy
    July 14, 2021

    And, conversely, a button is the only thing that can generate a confirmation pop-up (well, or a submit link).  (I already have a feature request out for that one...)

    The Expression Guru