Free cookie consent management tool by TermsFeed

Safe Link

On This Page

Function

a!safeLink( label, uri, showWhen, openLinkIn )

Defines a link to an external web page. Links can be used in charts, grids, hierarchy browsers, images, link fields, milestones, pickers, and rich text.

See also:

Parameters

Name Keyword Types Description

Label

label

Text

Text displayed as the link name the user clicks on.

URI

uri

SafeURI

URI target of the hyperlink. Supported URI schemes: http:, https:, ftp:, tel:, sms:, mailto:. See SafeURI for more information.

Show When

showWhen

Boolean

Determines whether the component is displayed on the interface. When set to false, the component is hidden and is not evaluated. Default: true.

Open Link In

openLinkIn

Text

(Browser-Only) Determines where the linked content should open. Valid values: "SAME_TAB", "NEW_TAB" (default).

Usage considerations

Specifying URI schemes

It's recommended that the URI use a specific scheme. When no scheme is specified, the component generates a hyperlink using the system's scheme and domain.

  • A link created by a!safeLink() opens in a new tab by default. Opening a link in the same tab can be configured using the openLinkIn parameter.
  • Note that a user's browser may still be configured so that new tabs are instead opened as new windows.

If you use the telephone URI scheme (tel:) or the text message URI scheme (sms:), the link attempts to open in the device's default phone dialer or text messaging application. These links may work in a browser and in the Appian for Windows app, but behavior depends on the operating system and whether an appropriate application is installed.

Because this behavior is inconsistent across platforms, telephone and text message links work best on mobile devices. Consider adding logic to only display telephone and text message links when the user is in the Appian Mobile app using a!isNativeMobile().

Examples

To experiment with examples, copy and paste the expression into an interface object.

To an external website

1
2
3
4
a!safeLink(
  label: "Company web site",
  uri: "http://www.appian.com"
)

Returns a hyperlink to http://www.appian.com

To a telephone number

Returns a telephone link that opens the device's default calling application. For this example, we used a!isNativeMobile() to only show the link when the user is in the Appian Mobile app, where calling apps are reliably available.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
a!richTextDisplayField(
  value: if( 
    a!isNativeMobile(),
  a!richTextItem(
    text: (
      "(555)-555-5555"
    ),
    link: a!safeLink(
      label: "(555)-555-5555",
      uri: "tel: (555)-555-5555"
    ),

  ),
  "(555)-555-5555"
 )
)

Feature compatibility

The table below lists this component's compatibility with various features in Appian.
Feature Compatibility Note
Portals Compatible
Offline Interfaces Incompatible
Sync-Time Custom Record Fields Incompatible
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.

Process Reports Incompatible

Cannot be used to configure a process report.

Process Events Incompatible

Cannot be used to configure a process event node, such as a start event or timer event.

Process Autoscaling Incompatible

Cannot be used in autoscaled processes.

Event Consumer Filter Conditions Compatible

Can be used in filter conditions.

Event Consumer Event Handlers Compatible

Can be used in event handler expressions.

The following recipes include usage of the Safe Link.

  • Action Banner Pattern (Formatting, Buttons, Rich Text, Cards):

    Use the action banner pattern to display prominent messages that include interactive elements like links or buttons.

Feedback