---
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 an action function
# Configure an action function {#ariaid-title1}
* Release version: Australia
*
* Updated June 21, 2026
*
*  8 minutes to read
Action functions enable the user to change something in the database. For example, making an update or adding a comment to a record requires an action function.
## 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 screen.
The Mobile App Builder categories home screen displays.
3. Select Functions in the menu, and then select New.
4. On the form, fill in the fields.
{#sg-studio-config-action-function__table_lvf_xd1_n2b__entry__2}
| Field | Description |
|-|-|
| Properties ||
| Name | The name of the function. Choose a name that is easy to identify. |
| Description | Additional information about the function. |
| Type | The type of function. Select Action item. |
| Context | The level to apply the action to. * Record: Applies an action at the record level. For example, use this option to create a button that changes the state of a record. You can set the context to Record for actions on a particular field, a particular record, or swipe actions. If the action function includes a UI parameter with the Input source field set to Auto fill, you must specify the table in the Table field. * Global: Applies an action at the global, or list level. For example, use this option to add a button that creates a record. Do not use the Global setting for actions that are in the context of a record, or actions that include a UI parameter with the Input source field set to Auto fill. {#sg-studio-config-action-function__ul_kvv_vth_2fb} For more information on button locations, 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."). |
| Available offline | Whether this function is available when the device is offline. Note: This option is only supported on the ServiceNow Mobile Agent app. |
| Action item | Action item to associate with the action. For more information, see [Configure an action item](https://servicenow-prod.fluidtopics.net/yoKrBS4snk1zej1cWalP~A "For an action function to work, you must create an action item to associate with the action function. Action items define what the action function is and how it works."). |
| Settings ||
| Allow images upload | Allows images to be uploaded. Images are stored in the attachment \[sys_attachment\] table. |
| Show signature field | Requires a user signature before submitting the action. Users can either sign with their fingers or type their names in the signature field. If Allow images upload is selected, an image of the signature is sent to the Signature Images \[signature_image\] table when the action executes. If selected, the signature form displays on a separate page. To overlay the signature form, use the Signature option in the Preconditions field. |
| Use Overlay | Overlays a text input parameter on the current details screen. Exactly one text input parameter must be defined for the action. If this option is not defined, the input parameter displays on a separate screen. |
| Preconditions | Select an option to require user confirmation before submitting the action. * None: Do not require user confirmation. This option is the default. * HR Task Signature: Require a user signature before submitting the action. Users can either sign with their fingers or type their names in the signature field. If Allow images upload is selected, an image of the signature is sent to the Signature Images \[signature_image\] table when the action executes. When this option is selected, the signature form overlays the current screen. * HR Task Credentials: Require users to input their credentials before submitting the action. This option is supported only with local authentication. * Re-authentication: Requires users to re-authenticate their credentials before executing an action. For more information, see [Configure mobile re-authentication system properties](https://servicenow-prod.fluidtopics.net/EfqhXXdYtLKHNiy61hBQSg "Set mobile re-authentication system properties so users must re-authenticate their login credentials when performing specific actions."). {#sg-studio-config-action-function__ul_vcx_vjr_23b} |
| Data ||
| Table | The table that the action applies to. Selecting a table is required if the Context is set to Record. If the Context is set to Global, selecting a table is optional. |
| Conditions ||
| Condition | Conditions that must be met to use the action. For example, you could prevent users from resolving an incident that is in a state of closed, resolved, or canceled. |
| Messages ||
| Show confirmation message | Displays a confirmation message to verify whether a user wants to continue with the action. |
| Confirmation message | The confirmation message to display. Note: Displays only if Show confirmation message is selected. |
| Confirm label | Label of the button to confirm the action. Note: Displays only if Show confirmation message is selected. |
| Cancel label | Label of the button to cancel the action. Note: Displays only if Show confirmation message is selected. |
| Success message | Text for a success confirmation message. Use curly braces to create a dynamic success message. For example, `{{number}} has successfully updated.` |
| Failure message | Text for a failure confirmation message. Use curly braces to create a dynamic failure message. For example, `{{number}} could not be updated.` |
| Acknowledgment messages ||
| Show acknowledgment text | Require user acknowledgment before submitting the action. If this field is enabled, the Context field must be Record. |
| Acknowledgment field | Field that includes the acknowledgment text you want to display to the user. Select the table for the field in the Data area. Only String fields are supported. Note: Displays only if Show acknowledgment text is selected. |
| Confirm label | Label for the confirmation button that appears below the acknowledgment text. The default value is I Agree. Note: Displays only if Show acknowledgment text is selected. |
| Action completion ||
| Refresh full screen after action | Option for the current screen to automatically refresh when an action completes. This option is available only when Context is set to Global. Note: The refresh option is supported for screens (applets) but not launcher screens. |
| Jump to previous screen | Redirects the user to the previous screen after completing an action. |
| Show refresh on previous screen | Shows a New Update message after the user completes the action and redirects back to previous screen. |
| Jump to screen after successful action completion | Displays additional screen navigation configuration options after the user completes an action. Use this field to determine whether user interaction is required before navigating to a specified screen. This option is available only when a table is selected in the Condition area of the form. |
| Jump to screen without user interaction | Sends the user to the destination screen. * If selected, redirection to the destination screen occurs automatically without user interaction. * If not selected, redirection occurs only with user interaction on a success message. To define a success message, you must complete the mandatory fields in the Messages section of the form. {#sg-studio-config-action-function__ul_r3b_bz5_pnb} Note: This option is available only when Jump to screen after successful action completion is selected. |
| Auto-populate screen parameters | Automatically populates parameters in the destination screen. Note: This option is available only when Jump to screen after successful action completion is selected. |
| Jump to destination screen | Specifies the screen that the user is redirected to after successful action completion. This screen displays newly created records, if available. Note: This option is available only when Jump to screen after successful action completion is selected. |
| UI parameters | Automatically populates parameters in the destination screen. Note: This option is available only when Jumpt to screen after successful action completion is selected. |
| Grouped inputs | This field is not used to configure an action function. Grouped input enables the users to scan several barcodes sequentially. You can configure grouped inputs with UI Parameters to accept multiple barcode scans. For information about grouped inputs, see [Configure a grouped input for multiple scans](https://servicenow-prod.fluidtopics.net/gbk~3FuiVaDIOwJj_f5E6A "Enable your users to scan several barcodes sequentially. Users can scan barcodes without leaving the scanning interface when you configure a grouped input. You can configure grouped inputs on buttons to accept multiple barcode scans.") |
| Button attributes | Specifies an additional attribute for a button. Select New to configure this option. You can select from the following button attributes: * alerts_require_dismissal: The button attribute when set to true enables the banner messages to persist until the user dismisses it. By default, banner messages are automatically dismissed. * used_for_deeplink: The button attribute when set to true determines 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: The button attribute when set to true triggers offline cache generation. After the cache is successfully generated, a download of it is triggered. * check_acl_on_url_parameter_field: When this button attribute is selected and 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. * refresh_parameter_screen_after_action : When enabled for write-back action buttons in input form screens, the input form automatically reloads after the action completes. This attribute keeps field values current and prevents you from working with stale data. The default value is false. Note: To keep the fields up to date with the latest database values, you must configure either a data source or an auto-fill variable for the relevant fields. This ensures the fields display the value that was just inserted or updated in the database. For more information, see [Loading mechanisms for input form screens](https://servicenow-prod.fluidtopics.net/CLuLn3FoPDfq7HDUqlN~Dg "The input form screen contains various UI elements, such as inputs, input actions, and descriptive elements. These elements can be populated either manually by the user or automatically using data sources and autofill variables."). * retain_parent_parameter_screen : When enabled for write-back actions in input form screens, the button keeps the user on the current input form instead of opening a new one. This attribute is required when configuring input form actions. For more information, see [Input form actions in an input form screen](https://servicenow-prod.fluidtopics.net/lM88WLm3rybA7aEiF3_LDA "Learn about adding a button next to input form fields. This button allows users to add comments, attach files, and navigate to other screens."). * consolidate_consecutive_outbox_items : When enabled for write-back buttons in offline mode, the attribute combines multiple consecutive saves of the same action on the same record (same action, record, table, and form) into a single outbox item instead of queuing each save separately. This setting controls offline outbox consolidation behavior. The default value is false. {#sg-studio-config-action-function__ul_aq3_frs_3wb} |
| Role access | Limit user access to an action by role. |
[Table 1. Function fields]
{#sg-studio-config-action-function__table_lvf_xd1_n2b}
Note:
While all the options in the Action completion area of the form can be set, their actions might overlap with each other. Make sure that you test the settings so the results produce the outcomes that you expect.
5. Select Save.
## What to do next
After you create an action function, you must associate it with a specific location in the mobile app. You can add an action function to a top menu, a swipe action, or to a specific field. For more information on associating the
action 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