Links on buttons

Link field for?

Else you can do one thing, create a cardlayout with rich text which looks like button, and use linkfield to it.

This will give a button feeling only

Regards,
Achuth

Hi Alexis Díaz Fajardo ,

It's an appian thing, instead you can use a!dynamicLink(), to save any data by saveInto field.

There are multple functions still supports in saveInto field of button.

But if you want a linkfield you can use following components:

1. Card Layout,
2. RichTextIcon,RichTextItem.
3. StampField
4. Tags(Record Link)

etc., according to your requirement.

Document downloading, for example

You can achieve the behavior you mention in various ways in Appian, and if you need to have the same look and feel, you can ,for example, use tagfields with recordLink, use a link Function...

In tend to disagree. A clear and consistent UX requires to make a clear distinction between navigating UI elements and actionable UI elements.

In my experience on environment where multiple groups develop apps with lacking governance, I already see enough messy and inconsistent UX, even with links in buttons.

In the case of documentDownloadLink, it isnt an action from the user and not a navigation? It would be nice too another way to do it.

Here is an example of using a CardLayout to simulate a button with a link.

a!sectionLayout(
  label: "Form",
  contents: {
    a!localVariables(
      local!selected,
      a!columnsLayout(
        columns: {
          a!columnLayout(
            contents: {
              a!buttonArrayLayout(
                buttons: {
                  a!buttonWidget(label: "Standard Button", style: "SOLID")
                }
              )
            }
          ),
          a!columnLayout(
            width: "NARROW",
            contents: {
              a!cardLayout(
                showBorder: false,
                showShadow: false,
                style: "ACCENT",
                padding: "EVEN_LESS",
                marginAbove: "NONE",
                marginBelow: "NONE",
                contents: a!richTextDisplayField(
                  align: "CENTER",
                  marginAbove: "NONE",
                  marginBelow: "LESS",
                  value: {
                    a!richTextItem(text: upper("Card Button"), color: "ACCENT")
                  }
                ),
                link: a!dynamicLink(
                  value: "BUTTON_VALUE",
                  saveInto: local!selected
                )
              )
            }
          )
        }
      )
    )
  }
)

Improved version from the one I posted in this thread: community.appian.com/.../card-layout

This has been a product request of mine for years.  StartProcessLink is another fine example of something I'd love to be able to put on a button.  There just shouldn't be limitations on what you CAN do with a button when you could easily configure it, then to Stephan's point you could include polite suggestions what you maybe SHOULDN'T do with a button in design documentation.  Some of course would be redundant, like putting submitLink() on a button when you could just set the button's submit: to true.  However, what you would gain far outweighs what silliness you would allow.