---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia Mobile Configuration and Navigation
ft:clusterId :
- mobile
bundleId :
- mobile
workflow :
- Development, Data and Analytics
---
# Configure a smart button
# Configure a smart button {#ariaid-title1}
* Release version: Australia
*
* Updated March 12, 2026
*
*  4 minutes to read
Smart buttons are actions that allow you to perform another action, such as sending
an email, making a phone call, pulling up a location, or navigating directly to a
URL.
## Before you begin
Role required: admin
## Procedure
1. Navigate to AllSystem MobileMobile App Builder.
The Mobile App Builder opens in a new browser tab and displays the application scope selection screen.
2. Search for the application scope you are working in and then select the name of the application scope.
The Mobile App Builder categories home screen displays.
3. Select Functions from the menu and then select New.
4. Complete the following fields as needed.
{#sg-studio-config-smart-button__table_yrx_2qc_clb__entry__2}
| Field | Value |
|-|-|
| Properties ||
| Name | Name for your smart button |
| Description | Unique description for your smart button to make it easy to identify. |
| Type | Type of smart button. Select from: * URL * Phone * Address * Email * Upload attachment * Chat launcher {#sg-studio-config-smart-button__ul_ur4_1tp_qwb} Note: Choose a field appropriate to the type of smart button you are creating. For example, if you are creating a smart button with the type Phone, select a field that includes a phone number. |
| Context | Context for your smart button. Select from: * Record * Global {#sg-studio-config-smart-button__ul_wrl_c5c_clb} Use Record context navigation functions in situations where the navigation depends on information from a record. For example, you want to navigate from the Assigned to field in an incident record to the assignee's user record. Use Global context navigation functions in situations where the navigation does not depend on information from a record. Note: Smart buttons using the Address type must use the Record context. The Context field returns an error if you select Global context for an Address type smart button |
| Data ||
| Table | Select the table where you want to use your smart button. Note: This option is only shown when the Context is set to Record. |
| Settings ||
| Take source value from field | Use a specific field from a table as the source of the smart button type. |
| Depending on what smart button type you select, you can specify the following settings. ||
| URL smart button | * Link URL: The URL to which your smart button will navigate. * Link label: The visible label of your URL link. {#sg-studio-config-smart-button__ul_jvf_r5p_qwb} |
| Phone smart button | * Phone type: Type of phone the smart button communicates with. Select from: * Cellular * Landline {#sg-studio-config-smart-button__ul_t34_z5p_qwb} * Phone number * SMS: The SMS message sent by the smart button. This field is only visible when you select Cellular in the Phone type field. {#sg-studio-config-smart-button__ul_rbj_w5p_qwb} |
| Email smart button | * Mail subject: Subject for the email message. * Mail content: Content of the email message. * Mail address: Email address to which the email is sent. {#sg-studio-config-smart-button__ul_zql_hvp_qwb} |
| Conditions (optional) ||
| Condition Type | Type of condition to use. Create conditions to limit when the smart button appears. For example, if you are creating a Phone type of smart button, you could create a condition to require a value in the phone number field. The following condition types appear if Context is set to Record and a Table is selected: * Declarative: Adds a condition builder to the form. For more information, see [Condition builder](https://www.servicenow.com/docs/access?context=c_ConditionBuilder&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). * Script: Adds a script condition field to the form. {#sg-studio-config-smart-button__ul_iw5_wvp_qwb} |
| Conditions | This option appears if Context is set to Global. This is a condition that must be met for the function to be visible in the app for the user to click on. |
| Button attributes | (Optional) Specifies an additional attribute for your smart button. Select New to create one of the following button attributes: * alerts_require_dismissal: When set to true, this button attribute enables the banner messages to persist until the user dismisses it. By default, banner messages are automatically dismissed. * used_for_deeplink: When set to true, this button attribute specifies that the button is used for deep linking. For more information, see [Deep linking for mobile](https://servicenow-prod.fluidtopics.net/A22zodEev1PeeKQm65e6vA "Mobile deep links are linking formats that direct users to specific content and locations within a mobile app. These links can be placed in email notifications, text messages, push notifications, launcher screens, and input form screens. You can also configure a mobile app login URL for multiple SSO identity providers."). * trigger_offline_cache_download: When set to true, this button attribute triggers offline cache generation. After the cache is successfully generated, a download of it is triggered. * check_acl_on_url_parameter_field: When set to true, any field in the URL string, is checked against the ACL (access control list). For example, a string like {{meeting_id}}. If a field does not pass this check, the field value is not included in the URL. By default, the URL parameter field is not checked against the ACL for backward compatibility. * hidden_attachment_sources: Enter values in the Value field from where you don't want images sourced from. Values can be camera, files or gallery, or any combination separated by commas. If this field is left blank, then images and files can be sourced from all locations. For more information, see [Define attachment sources available to users](https://servicenow-prod.fluidtopics.net/mlICSNEA9t0ov0RAYHqDow "Control the origin of where images and files are sourced from, including a phone's gallery, camera, or file system. This capability confirms that images can’t be reused and verifies that they aren't AI-generated."). {#sg-studio-config-smart-button__ul_dgd_pxp_qwb} |
| Role access | Limit user access to an action by role. |
[Table 1. Function form]
{#sg-studio-config-smart-button__table_yrx_2qc_clb}
5. Select Save.
## Result
## What to do next
After you create a smart button function, you must associate it with a specific location in the mobile app. You can add a smart button function to a top menu, a swipe action, or to a specific field. For more information on associating the smart button function to a location, see [Associate a function with a location in the app](https://servicenow-prod.fluidtopics.net/Augs8xkDK6V0LwjrneytfQ "For each function you create for an app, you must associate it with a specific location. You can associate most functions with a top menu, a swipe, or a specific field.").
*[\>]: and then