Mobile Platform -- Access your instance from anywhere using the ServiceNow Mobile Platform. The Mobile Platform enables you to create customized mobile experiences on the Now Mobile and Mobile Agent apps. Using these apps, your users access custom reports and can execute multiple tasks, enabling them to perform their work from anywhere, at any time.
Exploring the Mobile Platform -- Learn about the ServiceNow Mobile Platform and how you can give your users the ability to access resources by using Now Mobile and Mobile Agent mobile apps.
Now Mobile app -- Submit incidents and requests, manage tasks, and access company resources from anywhere using the Now Mobile app.
Mobile Agent app -- Use the ServiceNow Mobile Agent app to update records, coordinate with coworkers, track your location, and work without an internet connection — all from your mobile device. Download the Mobile Agent app for either Apple iOS from the Apple App Store or the Google Android version from the Google Play store.
Mobile Agent app demo -- Access the demo in your Mobile Agent app to learn how the app can help your agents work from anywhere using their mobile device.
Base system functionality -- Learn about the base system functionality included in with ServiceNow mobile apps.
Tested devices/supported versions -- Use the following information to verify that your mobile devices and operating systems are ready to use ServiceNow mobile apps.
Mobile admin role -- Administrators can assign roles that grant specific permissions, which govern what users and groups with that role can do within the ServiceNow Mobile Platform.
Encryption compliance -- Learn about how ServiceNow mobile apps comply with encryption security standards for the FedRAMP and DISA environments.
Mobile application management (MAM) -- Use Microsoft Intune or BlackBerry Dynamics to secure and protect sensitive information in mobile applications, even in cases where customers use their own mobile devices.
Bundle & Package IDs -- To enforce app policies your mobile application management software may require the bundle or package ID associated with the mobile app. See the following reference for these IDs.
Mobile instances -- Instances available on your ServiceNow mobile apps correspond to at least one instance on your ServiceNow platform web-based UI. According to your setup, the mobile instance contains some of the data and capabilities found on the web-based UI.
Branded landing page -- A branded landing page is a public web page displayed to users before they log in to their ServiceNow mobile app. This pre-login page contains a login button in the header or a deep link that navigates users to a specified area of a ServiceNow mobile app, bypassing the need to select an instance. The login button can be in the header of the mobile app, an integral part of the web page or both. The login button can either be in the header of the mobile app or an integral part of the web page.
Create -- Create a branded pre-login landing page with a ServiceNow mobile login button or mobile deep links. These elements redirect users either to a specific area within the ServiceNow mobile app or to the login screen.
Navigation links -- Learn about the different behavior of trusted or untrusted links on your branded landing page.
Cabrillo JS support -- Use Cabrillo JS to build custom mobile experiences inside of native mobile apps. Certain Cabrillo JS functions are available for the pre-login branded landing page.
Multiple users on a shared device -- Enable multiple users to log into a ServiceNow mobile account from a single mobile device. This is beneficial in environments where devices are shared, as it offers secure and personalized access through user-configured PINs, eliminating the need for repetitive full authentications.
General guidelines -- When configuring the setup for multiple users using a shared device, keep these general guidelines in mind for usability and a good user experience.
Optional settings -- Use optional settings on a shared device to define how long users are allowed to remain inactive before being required to reenter their PIN. The default is 300 seconds. You also have the option define the maximum number of users permitted on a shared device. The default is 15 users.
Next Experience -- Learn about the ServiceNow Next Experience user interface and how to enable it on your instance.
Configuration detail -- Learn about configuration details for the ServiceNow Mobile platform.
Before implementation -- Use these guidelines and considerations when implementing ServiceNow mobile on your instance.
Push notifications -- Mobile push notifications are configurable pushed messages that appear directly in a mobile app. These push notifications are non-actionable or actionable, and are configured by administrators to meet the needs of their users.
Components -- Configure mobile push notifications to target a specific screen in one of the ServiceNow Mobile Platform applications.
Configure message content -- Configure push notification message content and select which mobile application receives notifications. You can configure critical alert notifications, customize the message appearance, and determine the deep link used when users tap the notification.
Configure a message -- Configure the message displayed to users when they receive their push notification.
Configure an event -- Configure when a push notification event is triggered and sends a mobile push notification to users.
Configure sounds -- Add sounds and tones to push notifications to indicate to users if a message is urgent or just requires the users' attention.
Register push notifications -- Register your standard push notification in a push application to use it in your mobile apps.
Reuse push notifications -- Reuse push notifications across mobile apps with Mobile App Builder (MAB). Push notifications are configurable pushed messages that appear directly in mobile apps. Using MAB to manage push notifications streamlines your mobile application development into one tool.
Configure for iOS apps/certificates -- Install an iOS push certificate to use push notifications on your branded ServiceNow mobile apps for iOS.
Configure for iOS apps/tokens -- Use push notifications on your branded ServiceNow mobile apps for iOS using token-based authentication.
Configure for Android apps/HTTP v1 -- Enter your Google Firebase Cloud Messaging push token authentication in your push application record to use push notifications on your branded ServiceNow mobile apps for Google Android.
Configure actionable push notifications -- Include actions with your push notifications. Users can perform push notification actions without opening the app.
Create -- Create a push notification your users will see on their mobile devices.
Script example -- You can use this JSON script example to configure an actionable push notification for ServiceNow mobile apps.
Add an action category -- Select a push category to determine what actions your users can take in a notification. This category defines which actions your users can take when viewing a notification.
Create a push action -- Create push actions to suit your needs, when the base system actions do not meet your requirements.
Create functions for push actions -- Create mobile function for each function in the selected action category. These actions perform tasks on your instance based on what the user selects in the notification.
Map functions w/push actions -- Associate functions to the actions in your notification so the instance uses the correct function for each action.
Create message content -- Create a record to determine what information the notification displays to your users.
Create a notification -- Create a standard notification on your instance using the platform notifications.
Configure activity stream notifications -- Configure your instance to send an email notification or a push notification when a user mentions a contact’s name within a mobile activity stream record.
Configure push notifications -- Enable users to alert their contacts, through the use push notifications, that they are mentioned in a thread. The user enters the @ character followed by the contact's name in a record's activity stream, for their contact to be alerted.
Customize email notifications -- Enable users to alert their contacts by email that they are mentioned in a thread. The user enters the @ character followed by the contact's name in a record's activity stream, for their contact to be alerted. This feature is enabled by default.
Mobile critical alerts -- Send your users critical alerts, even if they set their mobile device to Do Not Disturb or Silent mode. Configure these visual and audio alerts to be sent when an issue needs immediate attention. Example scenarios can be to inform the user of an essential update, or to publicize a major incident that requires a speedy response.
Configure code -- You can make a push notification into a critical alert with the addition of some JSON code. Different JSON code is used for iOS and Android operating systems and for the ITSM business unit.
Location tracking in the Now Mobile Agent app -- Location tracking enables you to track the activity and positioning of agents while they perform tasks. You can also use the feature to make sure your agents are safe and can be easily located.
Enabling/selecting options -- Learn how to enable location tracking for the Mobile Agent and select the location tracking option best suited for your users.
Manual tracking -- Configure manual location tracking system properties to control how location tracking registers the activity of your users, while performing their tasks.
Action-based tracking -- Configure action-based tracking location properties. This tracking option starts and stops tracking based on the actions a user performs.
User location tracking -- Enable location tracking for specified users. The same tracking location settings apply to all the selected users on the instance.
Localization -- ServiceNow mobile apps are localized in many languages, including both left-to-right and right-to-left languages. Additionally, you can customize non-default languages on the client-side. These features ensure that your translations remain consistent across your mobile applications.
Native localization -- Native (on device) localization is controlled by the device's language preference, which means that many components are localized with the language preference for the user's device. These components can include local screen titles, such as Settings, and local button titles, such as the Clear All button on the filter screen.
Server-side localization -- Server-side localization works the same way as desktop web localization, using either the server system language or user preferences set on the server. Localized components on the server include things like field labels, web content, and other data stored on the server in a translated field.
Create translation records -- Create records on the Translated Name / Field table to translate elements of your mobile app that aren't natively translated.
Translation values -- Use this reference to find which values to use to translate your mobile elements.
Client-side localization -- Add customized client-side translations to extend language support on your mobile device. You can include languages beyond those natively supported by the ServiceNow AI Platform base system.
Offline mode -- Configure offline mode to enable your users who have no internet connection to continue working from a mobile device.
Mobile experience components -- Use the tables to view the various components and features that are either fully, partially or not supported in offline mode.
Offline mode setup options -- Review the setup options to determine which configurations apply to your offline mode requirements. Each option explains what to configure and why, helping you make informed decisions. Before configuring, identify your target users, the screens they need, expected data size, and connectivity patterns such as field versus office use.
Install and enable -- Configure the offline mode for your mobile app to control how and when users access data without connectivity. Users can download the cache manually, or receive it automatically based on schedules you configure.
Request -- Activate offline mode for mobile by requesting the activation of the SG Offline support plugin (com.glide.sg.offline).
Deactivate offline mode -- Deactivate the offline mode by creating the property glide.sg.offline.enabled and setting the property to false.
Align apps, screens, and functions -- ServiceNow mobile apps are organized into three hierarchical levels, apps, screens, and functions that work together to define the mobile experience for each user role. You can configure offline mode at each level, controlling what users can access and work on without network connectivity.
Offline mobile apps -- Consider which native applications are available in offline mode. The available apps are Mobile Agent app, Now Mobile app or a custom branded app created through the Mobile Publishing plugin.
Set up offline mode for mobile apps -- Setup offline mode for your mobile applications so that users can work without an internet connection.
Supported screens -- Consider which screen types to use in offline mode.
Setup screens for offline mode -- Setup offline mode for your mobile screen so that users can work without an internet connection.
Configure data items -- Define a separate data item for offline mode, giving you the flexibility to define the amount of data to display when a user is offline.
General guidelines -- When working with data items keep these general guidelines in mind for usability and a good user experience.
Define how many records -- Define the number of records to display to users in offline mode. Choose between 0 through 1000 records. This range gives you the flexibility to display different amounts to the user in online and offline modes.
Supported functions -- Functions define the actions users can perform from a screen, such as tapping a button, icon, or menu option. In offline mode, only functions configured as available on offline are accessible to users without network connectivity.
Display/hide functions -- Define whether to show or hide buttons while users are in offline mode on their Mobile Agent app.
Configure function instances -- Determine if the function instance available to users in online mode is also available in offline mode. This option gives you more control over how users manage their offline tasks.
Action items/action steps -- Action items or writeback actions are user-initiated actions that send data changes to the ServiceNow instance. While offline, writeback actions are queued and automatically synced back, once connectivity is restored.
General guidelines -- When working with action items keep these general guidelines in mind for usability and a good user experience.
Configure action items/steps -- Configure action items to execute actions like create, edit and delete records while in offline mode. For an action item to perform multiple processes you must define separate action steps.
Offline record reconciliation -- Configure offline mode to include associated records in the offline cache when users perform an action in online mode.
Register records -- Configure a write-back action step by adding an execution script that registers newly created instance records for synchronization. Local and server-side records are then reconciled when connectivity is restored, preventing duplicate records.
Configure offline cache to devices -- Control when and how the offline cache is refreshed on user devices to maintain relevance, performance, and bandwidth efficiency.
General guidelines cache downloads -- When working with cache downloads keep these general guidelines in mind for usability and a good user experience.
Scheduled offline caching -- Schedule automatic cache downloads at defined intervals, to keep offline data current and consistent. This approach prepares users for working offline at specific times without requiring them to manually download the cache.
Configure scheduled offline caching -- Configure offline caching so your field technicians can receive scheduled updates to their offline data cache. Scheduled downloads are based on the user's work schedule.
General guidelines -- When scheduling offline caches keep these general guidelines in mind for usability and a good user experience.
Incremental offline caching -- Incremental offline synchronization downloads only the changes to records, rather than the full dataset. This approach keeps offline data current while reducing network and battery usage.
General guidelines -- When working with incremental offline caching keep these general guidelines in mind for usability and a good user experience.
User-triggered cache updates -- Use action-triggered cache updates to define specific user actions that automatically refresh the offline cache in the background. This process reduces reliance on manual cache updates and helps to verify that users have current data when its needed.
Configure writeback action caching -- Trigger offline cache download is an optional button attribute (sys_sg_button_atribute_name) that will generate an offline cache after a successful completion of the assigned writeback action.
Manual offline caching -- Users can manually download or refresh the offline cache at any time. This option gives users control over when their device data is updated, before working without connectivity.
Input forms in offline -- Input form screens in offline mode support viewing, editing, and creating records without network connectivity. The ServiceNow apps use locally cached data to display forms, populate fields, and apply form logic, so users can continue working without interruption. Well-designed offline input forms, reduce rework and minimize sync conflicts.
Configure reference inputs -- Configure reference inputs so that users can see a list of records in offline mode on their Mobile Agent.
Associate attachments to activity stream -- Attachments added through input forms aren't displayed in the record activity stream by default, when working offline. Configure the write-back action step to associate attachments with the activity stream, so they appear immediately alongside other record updates.
Reference field attributes -- Configure the fields that you want to use and the data you want to display in offline mode by using various input attributes.
Attachments in offline -- Learn about the size and type limits applied to attachments in the offline cache.
General guidelines -- When working with attachments in offline mode, keep these general guidelines in mind for usability and a good user experience.
Security and compliance -- Learn how to manage offline mode access and determine which users can use it, helping to secure sensitive data.
General guidelines -- When working offline mode, keep these security and compliance general guidelines in mind for usability and a good user experience.
Siri shortcuts -- Configure Siri shortcuts to give your users quick access to common app functions app using their iOS devices.
Configure -- Change the destination screen of your Siri shortcuts to direct your users to a different screen than the default.
Barcode scanning -- Use the camera on your mobile device to scan barcodes into your instance using mobile applications.
Multi-scan -- Use multi-scan to quickly scan multiple barcodes or groups of codes. With multi-scan, you can input information for your assets faster than manual entry or individual scans.
Configure grouped input -- 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.
Create UI parameters -- Create UI parameters to contain the values that your users scan in with your grouped input.
Configure action items -- Configure the action item on your button so that you can use the values that your users scan in.
Plugins & upgrades -- Learn about upgrading to ServiceNow mobile, and how to install plugins to get your users started with the ServiceNow mobile platform.
Mobile plugins -- Learn about the plugins used to enable ServiceNow mobile on your instance.
Mobile Agent -- Use these plugins to extend functionality for the Mobile Agent app.
Now Mobile -- Use these plugins to extend functionality for the Now Mobile app.
Migrate from ServiceNow Classic -- Migrate from the Mobile Classic app to the Mobile Platform to take advantage of features such as rapid development, offline capabilities, and native mobile device feature integrations.
Migrate to New York & later -- Migrate your mobile applications in New York or later releases to take advantage of the improved features and continue editing within Studio.
Run migration script -- Run the mobile migration script to convert Madrid mobile applications you have created or modified to use the new mobile hierarchy.
Resolve common issues -- Find solutions to common issues after running the mobile migration script.
AppConfig -- Use AppConfig to define a default instance and browser for your managed mobile apps.
Device management -- Learn how to configure mobile device management software from supported vendors to distribute ServiceNow mobile apps.
Workspace ONE UEM -- Use VMware Workspace ONE UEM to distribute and manage the ServiceNow mobile apps on user devices.
Add iOS app -- Configure the ServiceNow app for iOS for Workspace ONE UEM distribution.
Add Android app -- Configure the ServiceNow app for Android for Workspace ONE UEM distribution.
BlackBerry UEM -- Use BlackBerry UEM (Unified Endpoint Management) as a mobile device management system to distribute and manage the ServiceNow mobile app on user devices.
Managing apps -- Learn how to manage ServiceNow mobile applications in the BlackBerry UEM (Unified Endpoint Management).
Configure access -- Configure the BlackBerry Access browser to authenticate ServiceNow mobile apps.
Citrix XenMobile -- Configure Citrix XenMobile to distribute and manage the ServiceNow mobile app on user devices.
Add app -- Configure the ServiceNow for Cetrix XenMobile distribution.
Configure app -- Configure apps that support managed configuration by deploying an XML configuration file to users' iOS devices.
IBM MaaS360 -- Use IBM Maas360 to monitor and manage smartphones, tablets, and other mobile devices from a web-based portal. Add the ServiceNow mobile app to the IBM Maas360 portal to monitor and manage distribution.
Add iOS app -- Configure the ServiceNow app for iOS for IBM MaaS360 distribution.
Add Android app -- Configure the ServiceNow app for Android for IBM MaaS360 distribution.
Intune -- Microsoft Intune uses Azure to manage mobile devices and apps. With some additional configuration, you can manage the ServiceNow mobile app in Intune.
Add app to Azure -- Configure your ServiceNow app for distribution with Microsoft Intune.
Add app to protection policy -- Learn how to add your ServiceNow mobile apps to your existing Microsoft Azure protection policies.
Configure auth browser -- Learn how to configure the default authentication browser for your ServiceNow mobile apps managed by Microsoft Azure.
Jamf Pro -- Use Jamf Pro to distribute and manage the ServiceNow mobile app on user devices.
Configure app -- Use app configuration to pre-configure the instance URL in Jamf Pro.
MobileIron -- MobileIron is a cloud-based service you can use to manage applications for your users. Users can access apps from MobileIron while you manage and secure content on the network.
Add iOS app -- Configure the ServiceNow app for iOS for MobileIron distribution.
Add Android app -- Configure the ServiceNow app for Android for MobileIron distribution.
Google Play -- Android for Work may not be able to find the ServiceNow application. If that is the case, the ServiceNow App might not be approved for your organization. You can approve the app by finding it in the Google Play store.
System properties -- Several system properties are available for you to further configure the mobile app. For example, use system properties to require a PIN, hide the image on the app homepage, configure the blur in background option, or disable sharing attachments from the mobile app.
Require app PIN -- Require users to enter a PIN when the application has been inactive for five minutes. To require the mobile user to set and enter a local application PIN, add the system property glide.sg.require_mobile_application_pin.
Re-authentication -- Set mobile re-authentication system properties so users must re-authenticate their login credentials when performing specific actions.
Configure login method -- Define the re-authentication method to be either single sign-on (SSO) or local login, depending on your security requirements.
Configure SSO login -- Define which identity provider to use for the SSO login. If this property is not defined, the system reuses the default identity provider used for a regular login.
Configure single/multiple use re-authentication -- Define whether each mobile action requires re-authentication. Alternatively, define whether the user can perform multiple actions without the need to re-authenticate each time.
Configure re-authentication timespan -- Define a time period in seconds that a user is not required to re-authenticate themselves. This parameter only applies when a user has permission to re-authenticate multiple times.
Blur app option -- As a security feature, administrators can configure the mobile app to blur or appear blackened, depending on the operating system, when not in focus on a mobile device. When you double-click the home button on your mobile device to close apps or navigate back to where you left off, the ServiceNow app appears blurred or blackened.
Rooted/jailbroken status -- Define whether jailbroken (iOS) and rooted (Android) devices are permitted on your mobile device. The default value is set to false to increase security and to minimize possible disruption to your system.
Clear clipboard/block sharing -- To have the mobile app clear the pasteboard when the app enters the background, as well as block the ability to share content, add the system property glide.sg.clear_pasteboard_when_backgrounded.
Max number data item records -- To set the maximum number of rows retrieved for the table defined in the data item, add the system property glide.sg.data_item.row_count.
Search list page size -- To configure the amount of search list results that load to the screen as the user scrolls down, add the system property glide.sg.choice_list.window_size.
List UI parameter records returned -- To configure the maximum number of records returned for a list of parameters, add the system property glide.sg.list.max_items_number.
Placeholder image -- You can specify an image on your instance as a placeholder for missing images. This image appears in your mobile apps when a record has an image field with an empty value, such as a user avatar or catalog item. You can select a different image to use for each table on your instance.
Deep linking apps -- Administrators can define which external apps can be used in deep links with the glide.sg.allowed_external_deeplinks property.
Block download/share attachments -- Set the glide.sg.block_mobile_attachments_sharing system property to true to hide the sharing button in the mobile app native viewer.
Group ACL -- Use the glide.sg.group_acl.enabled system property to control the validation of access control lists (ACL) during aggregation requests that are related to displaying results from data items that use grouping.
Android attachment viewing -- Set the glide.sg.block_mobile_attachments_external_viewing system property to true to prevent Android users from opening attachments in third-party applications.
Mobile properties -- Mobile properties enable admins to turn on or turn off features in ServiceNow apps without upgrading the ServiceNow instance.
Auto-app refresh -- Use the clientRefresh mobile property on your ServiceNow instance to turn on or turn off automatically refreshing your mobile apps. You can also use the clientRefresh property to adjust the scope of refresh on your mobile app.
External user attachment access -- Enable users who have been assigned the snc_external role to be able to view, upload, and download attachments on their ServiceNow mobile app.
Date/time fields -- Use the ShowDateTimeInUTC mobile property to determine whether the date/time field values in the Now Mobile app are displayed in the time zone of the user's device (default) or are converted to UTC.
Date/time format -- Set the useDeviceSettingsForDateTimeFormats mobile property to True to configure the date/time fields in mobile apps to use the date/time format that is used on the mobile device.
Hide date/time seconds field -- Set the mobileCardsShowSeconds, recordScreenDetailsShowSeconds, or the activityStreamShowSeconds mobile properties to False to hide the display of seconds in date/time fields.
Embedded web sessions -- Extend embedded web sessions to keep mobile users logged in until the mobile OAuth token expires.
Barcode scanning -- Add the EnableCameraFocusEnhancement and the EnableMaxCameraResolution mobile properties to enhance barcode scanning for Android devices.
External scanners -- Set the externalScanEnabled mobile property to True to enable barcode scanning with an external scanner while the device camera is available in other parts of the mobile app.
Android mobile attachment -- Use a combination of system properties and mobile properties to enable different users on Android devices to share, download, or view attachments in external applications based on roles.
Active authentication for Android -- Use the preventAppKillOnAuth property on your ServiceNow instance to help prevent Android devices from killing the mobile app when put to background during login. Use this configuration to allow for a smoother authentication experience by keeping the app active until users complete or cancel the login process.
Zero Trust Access -- Learn how to turn off the banner on mobile app screens where Zero Trust Access (ZTA) is enabled.
PIN timeout -- Configure the PINIdleTimeout property to define the PIN timeout for different ServiceNow mobile apps. You can use this property to enhance security by controlling how long users are allowed to remain inactive before being required to reenter their PIN.
Asynchronous attachment uploads -- Set the AsyncAttachmentsUploadEnabled mobile property to true to turn on background file uploads in the ServiceNow mobile app.
User roles/criteria permissions -- User roles and user criteria permissions are access control mechanisms that enable you to define roles or segment users into groups within the mobile platform. With these permissions, you can show or hide different components of your mobile app to either individuals or groups.
Component support -- Lists of mobile components that can be applied to user roles, user criteria, or to both these access control mechanisms.
User role permissions -- Control the visibility of different components of mobile apps by applying user role permissions.
Assign mobile user roles permissions -- Apply user roles to determine which components are accessible within mobile apps for specific groups of users.
User criteria permissions -- Control the visibility of different areas of your mobile apps by defining user criteria permissions. User criteria permissions enable you to segment your users into different groups, such as location, department or company. You can change information within a single area of a group to update all users' details associated within that group.
Assign mobile user criteria permissions -- Apply user criteria permissions to segment your users into different groups, such as location, department, or company.
Mobile pop-ups -- Display configurable mobile pop-ups based on real-time conditions. Mobile pop-ups are a way to transmit information to users and to encourage them to perform actions. You can display a mobile pop-up at the login page or when a user taps a button.
Create -- Learn how to display configurable mobile pop-ups based on real-time conditions. You can display these pop-ups at the mobile app login phase or after a button tap.
Assign predefined functions to mobile pop-ups -- Use predefined functions within mobile pop-ups to perform actions like dismiss the pop-up, proceed with the suggested instruction, or log out of the instance.
Indoor Wayfinding configuration -- Indoor Wayfinding enables ServiceNow mobile app users to locate an asset, such as a desk or meeting room, on a map and then reserve it.
Configure indoor positioning -- Indoor positioning enables end users to see their live location on an Indoor Wayfinding map and get guided navigation to their desired destination.
Mobile App Bridge -- Learn about Mobile App Bridge, which can be used to enable seismic pages, service portal pages, or classic web pages on mobile web screens. You can use this feature to support a playbook on mobile web screens and to enable other components.
Configure mobile web screens -- Configure mobile web screens with Mobile App Bridge to enable seismic pages, classic web pages, or service portal pages that are hosted within embedded web views. Using this feature, you can access native mobile functionality on ServiceNow mobile apps.
Create Now Experience Framework page -- To configure mobile web screens that use Mobile App Bridge to leverage a playbook on mobile devices, the first step is to create a Now Experience Framework page in UI Builder.
Mobile security -- Learn about the security features of the ServiceNow mobile platform.
Device security -- This document applies to current ServiceNow apps for iOS and Android for Australia. This document may be subject to change for future mobile releases.
Components and architecture -- The ServiceNow mobile apps consist of the ServiceNow server instance and native apps for iOS and Android. The apps use fully native code and are not a hybrid approach. The mobile client applications communicate over a wireless connection with the server and pull live data for the end user.
Identity & access -- Learn about user authentication, third party authentication, and user session termination for mobile applications.
User authentication -- ServiceNow mobile apps support platform authentication using OAuth 2.0. Authentication mechanisms include multi provider SSO, MFA, LDAP, Local DB, and Digest.
Mobile data flow -- Data can be retrieved, downloaded from, and written back to a mobile device.
Retrieval -- The following describes how data is retrieved from ServiceNow mobile apps.
Write-backs -- The following describes how data is written back from ServiceNow mobile apps.
Internal app distribution -- Internal distribution of ServiceNow mobile apps is supported through all major EMM vendors.
Data security -- ServiceNow mobile apps use SSL/TLS for Over-the-Air (OTA) communication encryption for data security. The OAuth authorization endpoints are HTTPS.
Push notifications -- Administrators create push notifications and users are able to receive them.
Security practices -- Mobile security practices include mobile-specific system properties, attachment control, password reinforcement, security patching, and controlling shared data.
Security controls -- Configure security controls to restrict copy/paste, enforce PIN, or block attachment functionality.
Security patching -- In the event a security patch is needed, the mobile development team aligns with standard SDLC properties in order to patch.
User data collection -- ServiceNow mobile apps do not specifically collect any user data.
Shared data -- ServiceNow mobile apps communicate with a third party software for app crash reporting. No customer information is shared.
Incident reporting -- ServiceNow mobile app issues should be reported through the standard support channels. You can report incidents by contacting Customer Service and Support.
Edge Encryption -- Users can view and edit data protected with Edge Encryption within their mobile device. The data appears in readable form on the mobile device but is encrypted in the database.
Domain separation -- Domain separation is supported in mobile. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Control app use -- To support your organization's authentication policies, admins can control which mobile apps can log in to ServiceNow instances.
Allowed app list -- As an admin, configure a system property that contains a list of mobile apps that can log in to ServiceNow instances.
Advanced app allowance -- Configure a scripted extension point with a list of mobile apps that can log in to the ServiceNow instance. When a user attempts to log in with an unauthorized app, the admin can add a link that redirects the user to an authorized app.
Advanced app allowance example script -- Users with the admin role can use the example JSON script to configure a scripted extension point. Admins can use these scripted extension points to limit which mobile apps can log in to ServiceNow instances. These scripts can also be used to specify a redirect link to authorized mobile apps.
External users -- Define external users to have availability to access your instance, but without access to all the capabilities allocated to internal users. External users are usually third parties, contractors, or external agents. External users are not employees of your organization.
Mobile authentication -- Users are required to log in to an instance on their mobile device. Depending on how you configure authentication for mobile devices, users may be required to enter additional information.
QR code for login -- Create and use a QR code containing JSON to provide a method for your users to log in with pre-defined parameters.
App token lifespan -- Configure the length of time it takes for the app to time out.
Force local login -- Configure the force local login option to provide local login experience on mobile apps even when the instance is configured with Single Sign On (SSO) configuration. You can configure this feature independently on any available ServiceNow app.
IP-restricted networks -- Enable ServiceNow mobile apps to access IP-restricted networks when adaptive authentication is activated on your instance.
Configure access -- Configure mobile access to ServiceNow instances that use adaptive authentication, which restricts access outside a defined IP address range.
Adaptive authentication -- Use these system properties to configure access to IP-restricted networks for ServiceNow mobile apps.
Identify providers -- You can configure a login experience that is specific to a mobile app and different from the web login experience. For example, Now Mobile app users can be automatically redirected to an identity provider (IdP) that is different from the IdP that is defined for the web session.
Authentication browser -- Admins can configure an external browser for mobile apps. This external browser is used during authentication so external URLs that are opened by the same browser can maintain sessions and cookies.
Zero Trust Access -- Limit end-user access to your ServiceNow instance by opting in to Zero Trust Access. This adjusts user roles and permissions according to security policies defined by the admin based on factors such as IP address, location, and identity provider attributes.
Configure -- Configure Zero Trust Access (ZTA) on mobile to reduce end-user access based on factors such as IP address, location, and identity provider attributes.
Mobile impersonation -- Use mobile impersonation to impersonate authenticated users for testing purposes and view impersonation logs.
Enable/disable -- Learn how to enable or disable impersonation in your ServiceNow mobile apps.
Mobile URLs -- Create mobile URLs to direct users to areas, screens, and features within specified mobile apps. Using mobile deep linking, these re-directional links can be placed within emails, texts, and push notifications.
Deep linking -- 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.
Structure -- Familiarize yourself with how to construct and use mobile deep links in any screen type within a mobile app.
Universal linking -- Mobile universal links enable you to drive users to specific screens within a mobile app, that they would not be able to access via the ServiceNow platform web experience.
Enable -- Enable the universal linking option if you want a web banner displayed on specified pages of the ServiceNow platform website. By default the mobile universal linking option is not available in the base system.
MESP pages -- Enable the expanded universal linking option to display the web banner on mobile browser pages when the user does not have the appropriate mobile app installed. By default this mobile universal linking option is not available in the base system.
Supported URLs -- Use mobile universal linking to display a web banner on specified platform web pages to encourage users to work within a ServiceNow mobile app. Configure the supported URLs that facilitate this functionality to ensure that the banners are displayed on the correct web pages. These URLs also direct users to a defined location within the appropriate mobile app.
Path segments & supported URLs -- Create path segment records and supported URLs records for universal linking to display a mobile banner. Users see this banner when they land on specific platform web pages. Within each supported URL, you define the page where the banner appears, the mobile app and the screen type the user views, and the data displayed within the screen.
Mapping for links -- Configure universal links for screen mapping so a user is redirected to a previously styled record screen or list screen. Use this option to provide a customized experience for the user.
Bookmark screens & web pages -- Configure the saved views feature to allow users to bookmark screens and web pages. Users can instantly access these saved views via an icon in the navigation bar.
Saved views -- Make the ability to save views available for specified mobile apps.
Disable -- Disable the saved views feature for some or all of your mobile apps.
Disable saved views -- You might want to remove the option for users to save specific views and screens for security or privacy reasons.
Custom branded apps -- The ServiceNow Mobile Publishing application enables you to publish secure and branded mobile applications. These mobile apps use your unique company identity and management method.
Prerequisites -- Before submitting your first branded app request with Mobile Publishing, it's important to set up some prerequisite tools.
Distribution -- Learn about making your mobile apps available for download to Android and iOS devices.
Privately distributed apps -- Private or enterprise distribution can be used to distribute Android and iOS branded applications. Private distribution includes all means of distributing apps outside of public app stores.
Publicly distributed apps -- Public distribution can be used to distribute iOS or Android branded applications on public app stores.
Request, test, & publish -- Publish secure custom mobile apps with your unique company identity by requesting branded versions of ServiceNow mobile apps.
Build statuses -- Learn what the Mobile Publishing build statuses "Build in progress" and "Ready for testing" mean and what actions they require from you.
Request private Android app -- Request, test, and publish a custom Android app that has your unique company identity. Then make the app available for private distribution.
Request private iOS app -- Request, test, and publish a custom iOS app that has your unique company identity. Then make the app available for private distribution.
Request public Android app -- Request, test, and publish a custom Android app that has your unique company identity. Then make the app available for public distribution on the Google Play Store.
Request public iOS app -- Request, test, and publish a custom iOS app that has your unique company identity. Then make the app available for public distribution on the Apple store.
Update a branded app -- Request and publish an update to a ServiceNow mobile app that has been branded with your unique company identity. Updates can only be requested for approved, completed builds of branded apps.
Custom branded apps -- Request and create custom-type mobile apps that are equivalent to Mobile Agent and Now Mobile apps with Mobile Publishing and Mobile App Builder.
Mobile Publishing resources -- Here are some additional resources to help you plan and publish branded mobile applications.
Mobile Publishing use cases -- Here are several reasons to use Mobile Publishing to brand the mobile apps of your company.
Next Experience theming -- Use Next Experience theming to give your mobile apps color scheme consistent with your instance web experience.
Configure theming -- Learn how to enable Next Experience theming, and create and apply themes for your mobile apps.
Color theme considerations -- Learn how to use color in your mobile applications to improve user experience. Using the right colors for your environment can help guide your users through your app and quickly identify important information.
Dark theme -- Switch between theme variants in ServiceNow applications.
Legacy theming -- Use themes on your mobile applications so that your customers and employees can recognize your unique company identity.
Create a theme -- Use mobile themes to give your applications a unique appearance that works with your company identity.
Assign a theme to your mobile application -- After you configure a mobile theme that reflects your company identity, you can assign the theme to your mobile applications.
Color guidelines -- Learn how the colors that you select in your mobile themes are applied on your mobile applications.
Button emphasis -- Use button emphasis to define the appearance and color of function buttons throughout your mobile app. The appearance and color of function buttons helps users identify the types of actions they trigger.
Configure -- Configure button emphasis in different locations within your mobile app to help users identify the type of functions they can activate.
Screen reader support -- Screen reader support (known as VoiceOver for iOS devices and TalkBack for Android devices) in mobile provides an audible description of what is displayed on your mobile screen. These can be elements like the content of mobile cards, the icons of the navigation bar, or the data within a list screen.
Card button voiceover text -- Screen reader support provides voiceover text for elements on the screen. However, elements like buttons that are defined as icon type may require additional configuration. Alternative text is added to these elements enabling the screen reader to read the content of the button within cards.
Card template button voiceover text -- Screen reader support provides voiceover text for elements on the screen. However, elements like buttons defined as icon type may require additional configuration. Alternative text is added to these elements enabling the screen reader to read the content of the button within card templates.
Displaying campaigns -- Use campaigns to deliver messages and important information to your users. You can set up and display a campaign on ServiceNow mobile.
Card appearance templates -- Create item card templates that contain information about the appearance of each type of card displayed in a mobile campaign.
Campaign cards -- Configure item views to provide the details that define the appearance of cards within a mobile campaign to enhance display options and make your campaign more effective.
Campaign components -- Configure components to display the image, video, and text cards in a campaign for your users to view and interact with on mobile devices.
Using the mobile apps -- Learn how to use ServiceNow mobile apps to get your work done from anywhere using your mobile device.
Working with mobile accounts -- An account is your ServiceNow environment — it includes your company's URL address (also known as an instance), a nickname, and your sign-in credentials.
Access secure instances with mobile devices -- Learn how to log in with your mobile device to a ServiceNow instance that uses adaptive authentication to restrict access based on IP addresses.
Change accounts on mobile devices -- Use multiple ServiceNow accounts on a single mobile device to quickly change to different accounts without the need to log out and log in. You can also automatically receive notifications from any of the accounts you're logged in to.
Access instances on mobile web browser -- Access an instance from anywhere using your mobile device. Connect using the mobile app or a web browser on a mobile device.
Mobile web UI -- Access an instance using the browser on your mobile device.
Tablet interface -- Use a tablet to access your instance either app or from a browser.
Mobile app structure -- Learn how components and settings are organized within ServiceNow mobile apps to understand how to find the tools and data you're looking for.
Using a shared device with multiple users -- Use a single device between multiple users to have a secure and personalized experience, where each user accesses their account through a unique PIN.
Mobile app settings -- Use the settings in your mobile applications to manage accessibility, notifications, location tracking, and more.
App PIN settings for mobile -- Improve the security of your ServiceNow mobile apps by setting a security PIN.
Enable notification settings -- Enable push notifications on your mobile device to receive information and messages directed to you.
Enable dark theme -- Use a dark theme on the Mobile Agent and Now Mobile apps to improve focus and readability, and accessibility.
Using location tracking -- Use location tracking so that you can keep a record of your location, either for a defined period of time or while you perform tasks .
Define banner display time -- Define the length of time a banner notification is displayed at the top of your screen. Increasing the display time provides additional time to read a message before it disappears, and for the screen reader to read out the entire message.
Display screen performance data -- Display performance-related data, like SQL counts, business rules, and REST API responses in a debug drawer at the bottom of the screen. This data enables administrators to measure the performance of each mobile screen and to identify any performance issues.
Offline mode for mobile -- Access and submit actions to records in your mobile apps, even if you don't have an internet connection.
Refresh mobile app meta-data -- See the latest updates your administrators have made to your ServiceNow mobile apps by refreshing a screen launcher page.
Languages on your mobile device -- Select a language for your ServiceNow mobile app that may differ from the language defined for your mobile device.
Selecting languages -- There are two areas where you define the language for your ServiceNow mobile apps: the instance language setup and the mobile app language setup.
Mobile search -- Learn how to use global search to find information within search sources configured for your mobile apps.
Mobile text search -- Find items, articles, and people by entering text in the search area.
Mobile voice search -- Find items, articles, and people using native speech recognition from an app on their mobile device.
Mobile photo search -- Configure photo search to give your users the ability to perform image-based searches using the objects around them.
Filtering and sorting results -- Use mobile filter capabilities within list, map, and calendar screens to help you search for specific data and streamline your results. Sorting lets you define how to view the filtered results.
Interacting with mobile activity stream -- Use the activity stream to submit and list work notes, files, images, and videos to a record within your mobile app.
Mobile notifications -- Mobile notifications appear as badges on your ServiceNow mobile app screen. The notifications alert you to required actions or events.
Handling mobile alerts -- Mobile alerts are an overlay pop-up window that displays over a record screen. The mobile alert displays an important message and a button to redirect you to an alternative screen.
Enabling critical alerts -- Receive critical alerts, even if you have configured your mobile device to a Do Not Disturb or Silent mode setting. Critical alerts are a more acute form of push notifications, where your mobile device is set up to receive visual and audio alerts usually when an issue needs immediate attention.
Mobile saved views -- Use saved views to gain quick access to frequently used screens and views.
Bookmarking saved view -- Create bookmarks for mobile views like forms, maps, and charts. Decide how you want to display these saved views, and deselect them when you no longer need them.
Using the calendar screen -- Use the calendar screen to create and view events related to specified dates. Scroll in either the calendar interface or the events list, to view corresponding information for the selected date or event.
Mobile platform dashboards -- Use a mobile dashboard to display data visualizations in graphical format. Adding data visualizations KPI Details and charts helps users more easily identify trends and turning points through indicator scores and visual representation.
Displaying KPI details -- Use KPI Details charts to help identify trends and turning points through indicator scores and visual representation. These charts are used when reporting on KPIs and metrics.
Using data visualizations -- Use data visualizations to help identify trends and turning points through indicator scores and visual representation. These data visualizations display the current state of instance data and are used when reporting on metrics.
Time series reports -- Learn to use time series reports for mobile, which enable you to display a series of data points over successive intervals of time. For example, the number of incidents opened over a certain period. The mobile platform supports the following time series reports, line, spline, and step line.
Single score reports -- Learn to use a single score reports for mobile. This report is a single value that you can use to share metrics or scores that are key to your business needs. For example, the number of high priority incidents opened by your team.
Donut reports -- Learn to use donut reports for mobile, which enable you to see the portions and percentages between different priorities at a single glance. For example, a donut report showing open incidents by priority, enables you to see whether incident counts of different priorities are within acceptable ranges.
Pie charts -- Learn to use pie charts for mobile, which show segments that make up a whole. This data visualization enables you to see the portions and percentages between different priorities at a single glance. For example, a pie chart report showing open incidents by priority, enables you to see whether incident counts of different priorities are within acceptable ranges.
Bar reports -- Use bar reports to compare individual or aggregate scores across data dimensions. Each bar represents a specific category of data. A stacked bar report helps you differentiate between each segment within a category. Mobile dashboards support vertical bar charts.
Mobile app feedback -- Learn how to provide feedback regarding your ServiceNow in-app experience.
Using the map screen -- Use the map screen to see highlighted locations associated with records. You can switch between the map view and list view to help you understand the information displayed within a map.
Indoor Wayfinding and reservations -- Use your ServiceNow mobile app to locate indoor resources at your site. You can also use this feature to get step-by-step directions to the office or to other resource locations.
Find and reserve an indoor resource -- View an interactive map of the interior of your building to locate available resources such as desks or conference rooms. After locating a resource, you can then reserve it.
Indoor positioning -- If an admin has configured your mobile app for indoor positioning, you can get guided directions in real time to a resource on your device's Indoor Wayfinding map.
Find resources with indoor positioning -- When indoor positioning is enabled on your device, you can get step-by-step interactive directions to resources in a building that has been mapped for this feature.
Accessibility features in mobile -- To make the user interface of the ServiceNow Mobile Platform accessible to users with disabilities, ServiceNow includes features that support several specifications in the Web Content Accessibility Guidelines.
Screen reader support -- Screen reader support (known as VoiceOver for iOS devices and TalkBack for Android devices) in mobile provides an audible description of what is displayed on your mobile screen. This can be elements like the content of mobile cards, the icons of the navigation bar, or the data within a list screen.
Change mobile analytics views -- You have the option to change the data analytics views from color segments to black and white patterns. This option can be used for accessibility purposes.
Define font size settings -- Adjust the size of text labels in the main screens of your mobile applications to enhance the readability of texts. This typography option can be used for accessibility purposes.
Enable map accessibility features -- Maps can use patterns or colors to identify locations. The accessibility toggle in the mobile device settings page controls how the map identifies locations.
Building mobile apps -- Create and modify mobile app components using ServiceNow low-code application development tools.
Terminology changes -- Starting from the Rome version ServiceNow mobile has updated the mobile terminology. The updated wording helps you better understand which items you are configuring within a mobile app, how the configurations affect the on-screen view, and how the items relate to one another.
Design considerations -- Use mobile design and product principles to give your users the best mobile experience.
Mobile SDK -- The ServiceNow mobile SDK enables users to develop native iOS and Android mobile apps using an integrated development environment and give mobile apps access to existing ServiceNow data and workflows.
Mobile hierarchy -- Learn the components of ServiceNow mobile and how they work together to assist you in configuring, modifying, and creating applications.
Usage Insights -- Usage Insights helps you understand usage and adoption of your mobile applications.
Building tools -- Use these low-code tools to build your mobile apps.
Mobile App Builder -- The ServiceNow Mobile App Builder (MAB) is a configuration tool to build and manage screens and records that make up workflows within ServiceNow mobile apps. The organizational layout and navigation options in the Mobile App Builder facilitate a faster and more intuitive creation of ServiceNow mobile applications.
Access MAB -- Access the Mobile App Builder to start the process of creating workflows for your mobile apps.
MAB categories home screen -- Use the Mobile App Builder categories home screen to select or create the most commonly used configuration options. Select category options like Screens or Cards & Icons to create and edit records.
Menu options -- Familiarize yourself with the various menu options in the Mobile App Builder categories home page.
Record screen -- Use the Mobile App Builder record screen as the workspace where you perform all your mobile configurations.
ServiceNow AI Platform configuration tree -- The ServiceNow AI Platform configuration tree shows all your records in a hierarchical display. Instantly locate and select any record component in the tree to display the record's field types in the configuration panel.
Configuration panel -- The configuration panel is the main work area of the Mobile App Builder where you perform the editing of your records.
Interface preview panel -- The mobile interface preview panel helps you to identify the UI element you’re working on in the configuration panel within your mobile device. Record types with preview support display a live preview of how the components will appear on a mobile device instead of showing examples.
UI elements -- Familiarize yourself with the various elements contained within a record screen.
Input field types -- Familiarize yourself with different field types and their usage in the Mobile App Builder record screen.
Tables -- Use tables in the Mobile App Builder record screen to reference child records to a parent record. These records can consist of either single reference records or multi-reference records.
Create new records -- Select existing records or create new records in the Mobile App Builder categories home screen to build your mobile app.
Duplicate existing records -- Using Mobile App Builder (MAB) you can duplicate existing records with their associated child records. You can then use these duplicated records as a template from which you can create new screens and cards.
Now Assist component recommendations -- Now Assist reduces manual work and saves you time by recommending components based on context like the current record name and configuration tree information when you’re configuring records.
Create reference record entries -- Create new entries in the record screen tables of the Mobile App Builder. View where the Now Mobile configuration tree displays the new entry in the hierarchy.
Save changes -- Save all the changes you make within the Mobile App Builder with a single action. There is no need to save each change individually before moving onto another screen or record.
Delete records -- Use the Delete button to delete records in the Mobile App Builder. This button exists in the same location throughout the tool. When deleting a record, all child records are removed from the configuration tree, but they are not deleted from the database.
Access MCB within MAB -- Access Mobile Card Builder without leaving Mobile App Builder. By selecting Open in Mobile Card Builder, you can create and edit personalized cards and card templates without needing to open a new browser tab.
Web to mobile component conversion -- Use guided UI to configure native mobile components using an existing web component as a starting reference.
Enable the mobile card generation skill -- Activate the mobile card generation skill to let Now Assist generate mobile components using existing web components as a reference.
Mobile Card Builder -- Use Mobile Card Builder to create or modify card templates using a graphical interface.
User interface -- Learn about the Mobile Card Builder user interface to get started building and modifying your mobile cards.
MCB components -- Learn about the components that make up mobile cards
Create a card template -- Use Mobile Card Builder to create a card template to use for cards in your mobile screens.
Customize a screen -- Use Mobile Card Builder to modify the cards for your screens.
Assign field values -- Use Mobile Card Builder to show field labels and values from your tables in mobile cards.
Card actions -- Design and add actions to cards that you create within the Mobile Card Builder. You can use buttons to enable your users to perform actions directly within a card. For example, to accept or reject suggestions, call listed contacts, and to add items to a cart.
Light and dark modes -- The Mobile App Builder and Mobile Card Builder tools can configure both light and dark mode options, allowing users to easily switch between a bright or subdued interface, enhancing comfort, readability, and battery efficiency.
ServiceNow Studio integration -- Mobile App Builder and Mobile Card Builder are both available within ServiceNow Studio, allowing you to do all of your development work in one place.
Navigation bar -- User the navigation bar in your mobile apps to access launcher screens, screens, settings, and notifications.
General guidelines -- When creating a navigation bar, keep these general guidelines in mind for usability and a good user experience.
Configure navigation bar and tabs -- Configure the navigation bar that appears at the bottom of the mobile app. Use navigation bar tabs to navigate to screens, launcher screens, as well as saved records, settings, and notifications pages.
Configure badge counts -- Configure navigation bar launcher screen tabs and screen tabs to display badge counts. These badge counts indicate how many rows in the Badge Count [sys_sg_badge_count] table match a condition that you can configure. For example, how many work orders are waiting for your attention or how many new and unread Sidebar messages have been received.
Launcher screens -- Launcher screens serve as landing pages or home pages. Using a launcher screen, you can access screens in various formats, as well as search, do quick actions, and find user information.
Create a launcher screen -- Use launcher screens in a dashboard layout, for users to access mobile screen types, as selected by you.
Configure a header -- Create a launcher screen header to define how the title of the screen appears.
Global search -- Give your users the ability to search for information within the defined search sources from a mobile app.
Enable global search -- Enable global search using the Zing search engine on your screen launcher, to give your users the ability to quickly find information within the defined search sources.
Configure global search options -- Configure global search options, using the Zing search engine, to control how your app presents search results to your users.
Populate search suggestions in the mobile apps -- If you are upgrading from a previous release, run a script to populate search suggestions with data from a platform search table to provide search suggestions to your users. Alternatively, you can wait until users search for keywords instead of running this script.
Configure search criteria -- Create a custom search for your launcher screen to help your users find related information quickly. Administrators can configure which search sources the search uses, as well as options like search result limits.
Create a search source -- Create a search source to define what records can be found in your search bar.
Create a search configuration -- Create a search configuration. This record connects your launcher screen with the other records used to configure search.
Enable voice search -- Enable your users to search for items, articles, and people using native speech recognition from an app on their mobile device.
Mobile photo search -- Configure photo search to give your users the ability to perform image-based searches using the objects around them.
Configure photo search -- Configure photo search for your mobile applications by enabling photo search in system properties, creating a Firebase account, and connecting your account to your ServiceNow instance.
Enable photo search -- Enable photo search on your launcher screen record in Mobile App Builder to present the photo search option for your users.
Configure an empty state for search results -- Configure a customized empty state for search results to provide users with information and actions to help improve their search criteria. This information will replace the default empty state that is provided for search results.
Mobile dashboard preview -- Dashboard previews display a preview of data visualization charts and single score reports in your launcher screen’s analytics section.
Create a mobile analytics preview -- Use a mobile analytic preview within a mobile dashboard to display data visualizations on your launcher screen pages.
Data visualization fields -- Mobile data visualizations show data relevant for mobile device display. Create the data visualizations within the Analytics Center of the ServiceNow platform. All settings and configurations that are available for display in the mobile platform are listed in this topic.
Configure chart views -- Give users the option to change chart views from color segments to black and white patterns. This option can be used for accessibility purposes.
Launcher screen UI sections -- UI sections contain the screens, analytics previews, and record information on your launcher screens.
Configure a record UI section -- Use the record UI section type to display records from a selected list as cards with important information. These cards enable users to access your record screens. Select how you want to represent this option visually.
Configure additional capabilities -- Define additional record section capabilities like the number of rows, specifying the card size, and the type of card-swiping action. These features are configured in the web-based UI as opposed to the Mobile App Builder.
Customize card size -- Customize the size of cards in a record section if the default options do not suit your requirements.
Configure action functions -- Add action functions, like buttons to the footer area of record sections to enable users to trigger functions within a record section and quickly perform repetitive processes. This capability can be added to launcher screens and section screens within a record section.
Configure an analytics UI section -- Use the analytics UI section to display previews of your data visualization charts. Use it to show different visualizations for data sources and provide access to a specific chart or list screen.
Configure an icon UI section -- Use the icon UI section type to navigate to screens, launcher screens, and functions.
Adding images to an icon section -- Upload images or icon-style images to use within your icon sections. Use personalized images to brand your mobile application. This feature is configured in the web-based UI as opposed to the Mobile App Builder.
Configure a content UI section -- Use the content UI section type to display text, images, and videos as campaign cards at the top of your screen. Use these campaigns to deliver messages and important information to your users.
Configure a media UI section -- Configure a media UI section type to display images or videos on your launcher screen.
Add a UI section to the launcher screen -- Associate a UI section to the launcher screen to display the relevant data visualization preview on your mobile device.
Quick actions -- Define quick actions for your launcher screen so that your users can access commonly used functions, such as transferring records or using a template in the mobile app.
Mobile screens -- Learn how to create and use screens in ServiceNow mobile apps. Use screens to make your mobile app functionality available to your end users.
Mobile screen types -- Learn how to use screens in ServiceNow mobile. Use screens to make your mobile app functionality available to your end users.
Create a screen -- Create a screen for a specific task, within your mobile app. Each screen comprises of one or more embedded screens displayed to your user to complete a task.
List screen -- Use a list to display a list of records. Records in lists display in a card format, showing a limited selection of the information in the record.
List screen configuration -- Configure a list screen so that your users can see a list of records from their mobile app. To access a record from the list, a user can tap the record name.
Configure a record screen -- Use a record screen as part of a list so that your users can see the details of a record from their mobile app.
Configure a parameterized list screen -- Configure a list screen to query a user for a parameter, which the screen uses to filter the records that appear on the screen.
Mobile list screen filters -- Use mobile filters in list screens to enable your users to find what they need in your instance's records.
Configure a custom filter -- Manually create a filter experience for your users. Custom filters can include fields that are not in the list pattern.
Filter condition attributes -- Use these filter condition attributes to customize how your data is filtered for condition types that are set in your mobile apps.
Add Boolean fields -- Add Boolean fields, such as 'Active: Yes / No', within mobile filters, so users can more easily search for specific data and streamline their results.
Configure sorting capabilities -- Use the sorting option in lists and maps to help users organize their filtered results and enable them to view the most relevant information. Examples of configurable sorting options are: recently added, assigned to (ascending), assigned to (descending), and highest priority first.
Configure a dynamic screen name -- Configure a screen to dynamically inherit a name from a parametrized list screen. This setup enables users to view a passed parameter as the screen name instead of the screen record name.
Configure an empty state -- Configure an empty state to display on empty list screens, to provide information to further direct users. These features are configured in the web-based UI instead of in the Mobile App Builder.
Record screen -- Record screens display content for a specific single record.
Configure a parameterized record screen -- Configure a record screen to query a user for a parameter. The screen then uses this parameter to determine the record that appears on the screen.
Configure an activity stream screen -- Configure an activity stream screen on your form to give your users access to comments, work notes, and attachments relating to the record they are viewing. In addition, use activity stream segments when you want to show the history of updates for a record.
General guidelines -- Consider these general guidelines when configuring your activity stream.
Configure an embedded browser screen -- Add an embedded browser screen to display content from a URL within a browser section. This enables users to access information in a ServiceNow instance or on a page outside of your instance.
Manage attachments -- Add, remove, rename, and view attachments in your mobile record screens.
Add functions -- Add functions to your details screens to enable your users to take actions or view additional information.
Add a field function to screen -- Add field functions to the details screen in your record screens using Mobile App Builder.
Add a footer function to screen -- Add footer functions to the details screen in your record screens using Mobile App Builder.
Screen fields -- Screen fields improve the usability of your form screens. With screen fields, your users can view and edit attachments, view and complete checklist items, or display a field without a label.
Add screen fields to a record screen -- Add screen fields to improve the usability of your record screens. Screen fields enable you to change how information is shown in your form or you can provide access to additional elements, such as attachments, videos, or links.
Dynamic variable support in record screens -- Use the script screen field in record screens to display dynamic field values. The script runs to determine the field value before it displays in your form. The value returned by the script doesn't replace the database value. For example, you can display translated content for dynamic variables within an email.
Configure the script field for records screens -- Configure script screen fields to display calculated or personalized content in your mobile forms, without modifying the underlying database values.
Configure a dynamic screen name -- Configure a record screen to dynamically inherit a name from a field in a previous record. This setup enables users to view a single specified field as the screen name instead of the screen record name.
Configure a record UI section -- Enrich your record screen with the addition of record UI sections displayed in a card format. This capability presents content and users can trigger actions without the need to navigate to an additional list screen.
Configure an alert -- Configure a mobile alert overlay for a record screen to inform users of an important message and to redirect them to a specific screen. Only one mobile alert is available per instance.
Using dynamic segments to display data -- Dynamic segments in a record screen enable users to see a subset of relevant records rather than a whole list of records.
Configure a dynamic segment to display selected data -- Configure a record screen with a dynamic screen segment so users can view records that correspond to selected segments, rather than view a complete list of records.
Customize segment button colors -- Customize the color of segment buttons to help users identify a tapped segment button. For example, use a darker color to indicate that it is a selected button.
Embedded lists -- Use an embedded list to place a list of information that is related to your current record within a segment on your record screen so that your users don't have to navigate to a related list.
Configure an empty state -- Configure an empty state to display on empty record screens to provide information to further direct users. The display of an empty state for an embedded list in a record screen takes priority over an empty state defined for a list screen.
Configure a related list screen -- Create a related list screen to give your users easy access to records related to the record they're already viewing.
Create a parametrized data item -- Create a parametrized data item to contain the records that display in your related list.
Create a list screen to use as a related list -- Create a related list using your parametrized data item. This list appears for your users when they select the related list tab on their form screen.
Display a related list -- Update your record screen to display a list of related records.
Disable attachments -- Disable attachments for mobile apps by using access control rules.
Grouped list screen -- Grouped list records display a list of records that are grouped by a specific field.
Configure a group list screen -- Create a group list to provide a view of a list of records grouped by a field you specify.
Map screen -- Map screens display a map with locations that are associated to the records in a data item.
Configure a map screen -- Configure a map screen so that your users can see location-based information on a map from their mobile app. The map highlights points of interest, and users can switch between a map view and list view to help them understand the information displayed on a map.
Mobile map screen filters -- Use mobile filters in map screens to enable your users to find what they need in the records on your instance.
Calendar screen -- Calendar screens display a calendar interface and records associated with the selected date.
Configure a calendar screen -- Create a screen that displays a calendar with a list of related records. Users can see which records are related to dates on the calendar.
Mobile web screen -- Mobile web screens open an external URL or a relative URL within your instance.
Configure a mobile web screen -- Use a mobile web screen to open a URL from within a ServiceNow mobile application. You can configure relative URLs to open pages within the ServiceNow platform.
Add a Virtual Agent launch button -- Admins can configure a button on a mobile web screen that end users can use to launch Virtual Agent from their mobile device.
Chart screen -- Chart screens display data visualizations created in the Analytics Center and are displayed in the analytics section of your launcher screen. Adding data visualizations helps users more easily identify trends and turning points through indicator scores and visual representation.
Add a navigation function to an analytics preview -- Configure your analytics preview to use a navigation function. This function directs your users to your chart screen from the analytics preview on your screen launcher.
Create a navigation function -- Create a navigation function to direct your users from the chart screen to a parametrized list.
Assign the navigation function -- Assign your navigation function to your chart screen so that your users can tap the chart to access the list of records.
Input form screen -- Use input form screens to provide an interface for your users to enter information in mobile apps.
Configure an input form screen -- Configure an input parameter so that your users can see a list of records from their mobile app. To access a record from the list, a user just has to tap the record name.
Loading mechanisms for input form screens -- 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.
Data sources -- A data source is a loading mechanism that maps UI elements to specific database fields using element identifiers. Use data sources to retrieve and display data onto input form screens.
Configure data sources -- Configure data sources to map UI elements to specific database fields using element identifiers, enabling the retrieval and display of data on input form screens. This mapping verifies that each UI element accurately reflects the corresponding data field within a record.
Data source script examples -- Use data source scripts to map input values, descriptive elements, and input actions. Alternatively create a dedicated data source for each of these elements.
Configure descriptive elements -- Add descriptive elements, such as an image, simple text, rich text, or a mobile card, before an input field within an input form screen. This additional on-screen information provides a context to your users, enabling them to better understand what is required as they enter data into an input form.
Configure a card descriptive element -- Add a card descriptive element before an input field, within an input form screen. This additional on-screen information provides a context to your users, enabling them to better understand what is required as they enter data into an input form.
Configure inputs -- Configure the input fields that your users use to enter information. You can use screen inputs to determine the input type, question text, placeholder values, and other attributes.
Input form screen attributes for inputs -- Different types of inputs are available for use in input form screens, and you can use different attributes to configure the inputs.
Number render types and compatible input attributes -- Use the tables to determine which input attributes are compatible with different number render types. The available number render types are integer, line, percentage, and slider.
Configure a slider option for a number input -- Create a slider option for a number input on your input form screen. Sliders help users visualize the input range and reduce errors by limiting choices to defined minimum and maximum values.
Slider types and attributes -- Review the sections to see slider type examples and learn which input attributes are used to create them.
Configure a decorative slider -- Create a colored slider option for a number input on your input form screen. Decorative sliders contain sections that can be associated with a specific color and label to aid visual representation. These labels are translatable.
Date/time input setup for action items -- After you create an input form screen and define its IncludeTimezone attribute for date/time inputs, you must associate the input form screen with an action item. How you set up the date/time inputs depends on the type of action item you use.
Configure attributes for input form screen variables -- Use screen variables to collect information from the user automatically or define default information. Variables can include information like user IDs and GPS coordinates.
Input actions and input sources -- Configure actions that you want to appear in an input field in your input form screen. You can add a menu button next to input form fields to perform various input actions like add a comment, attachment, or navigate to another screen. Additionally, create an input source to trigger UI rules to summarize actions for GenAI.
Input form actions -- Learn about adding a button next to input form fields. This button allows users to add comments, attach files, and navigate to other screens.
Configure input form actions -- Add a button next to input form fields to give users the ability to perform various input actions. These actions include adding a comment, adding one or more attachments, and navigating to other screens.
Script code for comment type and updates for input actions -- Use the following script to determine where user comments entered in an input form are stored. The script also records comment deletion, updates, insertions of new text, and tracking the timestamp of changes.
Configure input sources -- Configure the actions that you want to appear on an Input field to trigger a UI rule. These input source actions are shown above the keyboard, or next to the selected input. Use it to configure summarization actions for GenAI.
Configure input form screen actions -- Learn how to configure actions that affect the whole input form screen. These actions can be accessed with an icon or within a more menu button, located in the top menu bar. For example, you can configure a writeback action to save your work progress on the input form.
Configure input form pages -- Create input form pages to enable users to view data over multiple organized pages, rather than scrolling through a long list of entries. Input form pages host data from inputs and sections. You control the layout of the pages, and which inputs and sections belong to each page of the input form screen.
Configure input form sections -- Input form sections are reusable components consisting of grouped inputs. You can associate these sections with any number of input form pages.
Use timestamps to track user changes -- Use the following code to extract data to monitor the timestamp of changes made by different users on an input form screen.
Configure auto-fill inputs on input form screens -- Streamline form completion on input form screens by configuring auto-filled inputs based on one or more user inputs. Auto-fill inputs are configured by using mobile client scripts.
Configure input form screens with signature inputs -- Configure input fields that your users can use to sign electronically on the input form screen. Users can sign on the screen or type their name to record their signature.
Mobile fetch types -- Fetch type settings determine when data is loaded in your screens. Change your fetch type to optimize load time performance for your screens.
Cards and icons -- Cards are predetermined layouts that can show visuals, text, and data. Icons are symbols that act as actions or shortcuts when connected to other screens.
Configure card templates -- Create a card template to define the UI elements and layout to be used on a card.
Configure cards -- Use cards to visually display information from different records by mapping data to the UI elements defined in a card template. UI rules can also be used to define conditional styling on cards.
Data items -- Data items provide the data presented in a screen.
Configure a standard data item -- Configure a standard data item to query data for your screens that do not require parameter input.
Configure a parametrized data item -- Configure a parametrized data item to filter and view just the relevant data according to the selected parameters.
Assign to a list screen -- When you associate a parametrized data item with a list screen, additional fields appear in the screen configuration that you must complete for the parameter to be applied.
Assign to a record screen -- When you associate a parametrized data item with a record screen, additional fields appear in the screen configuration that you must complete for the parameter to be applied.
Configure an encoded query data item for chart screens -- Configure an encoded query data item to query data for chart screens. An encoded query data item is a parametrized data item that is the basis for a chart screen to be passed to a list screen. When tapped it enables users to drill-down to a list of items that the chart is created from.
Configure a group by data item -- Configure a data item for a grouped list screen. You group items in a data item to get a count. For example, you can group a list according to priority and then on a grouped list screen see a count of how many high, medium, and low items exist.
Mobile functions -- Configure functions in Mobile App Builder to determine which actions users can perform in the mobile app.
Action functions -- Action functions make changes to records on your instance.
Configure an action function -- 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.
Configure an action item -- 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.
Configure an action item with parameters -- Parameters determine the information you are passing into the action to ensure you are changing the correct record and to enforce required fields as needed. Create an action item with parameters to define the changes being made to an action and how the changes get made.
Create an action function with parameters -- Request additional information from your end users when they interact with an action. For example, you can allow your end users to provide a reason for rejecting an approval by adding a text input parameter to a Reject button. When you create an action item that has parameters, you must also configure the UI parameters for the action function.
Define banner display persistence -- Define if a message or banner displayed on a mobile device requires the user to acknowledge the receipt of the message.
Reference qualifiers -- Admins use reference qualifiers to create filters that streamline data returned for a reference field. The results of configured reference qualifiers are viewed within your mobile device.
Configure a contextual link to Virtual Agent -- Use Mobile App Builder to create a contextual link in your mobile application so that your users can connect to Virtual Agent and receive information that pertains to their issues. By using a contextual link, your users automatically receive the information that you define about the relevant record.
Create Virtual Agent UI parameters -- Create UI parameters to pass information from your record into Virtual Agent so that your users get the information they need for their issues.
Enable Virtual Agent -- Give your users the ability to chat with a virtual agent through a ServiceNow mobile application.
Navigation functions -- Navigation functions transition users from their current screen to another screen or launcher screen.
Configure a navigation to a screen -- Navigation functions enable you to define simple ways for end users to navigate within the mobile platform, for example, navigating to a record from a field on another record.
Configure navigation to a launcher screen -- Use a navigation function to direct your users to a launcher screen. Use this navigation function in a quick action, footer button, or top menu.
Use your navigation function as a footer function -- Footer functions enable your end users to take an action on a details segment of a form. You can use the navigation function you created to give your users access to the application launcher from within the details segment of your forms. Unlike the top menu function, the form footer button is visible at the bottom of the form.
Smart button functions -- Use smart buttons to interact with native applications on your mobile device, such as your phone, map, or email applications.
Configure a smart button -- 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.
Predefined button functions -- Use predefined buttons to quickly add prebuilt functionality to pop-ups in your mobile app.
Associate a function with an app location -- 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.
Mobile styles -- Use mobile style elements to change the appearance of your mobile applications.
Mobile UI Rules -- Use Mobile UI rules to build rules that modify the mobile UI. These modifications can include hiding and displaying fields, making fields mandatory, performing field value calculations, and applying UI styles to different UI elements.
Create a mobile UI rule -- Create a mobile UI rule to apply styling or field calculations for your mobile UI elements.
Mobile UI styles -- UI styles define the font and background color of fields in your applets.
Create text decorator icon -- Use a text decorator icon to selectively highlight list elements that need your users attention.
Mobile icons -- Use icons to provide unique identifiers for navigation and actions in your mobile applications.
Configure font type icons -- Configure font type icons that can be used in a variety of places in mobile apps. For example, you can use font type icons in screens, cards, functions for quick actions, and navigation bars and tabs.
Add a font icon -- Use Mobile App Builder to configure mobile apps that use a font family icon.
Configure user type icons -- Configure user icons that can be used to launch the user profile of the logged in user in mobile apps.
Configure using a user icon in a mobile app -- After you configure a user type icon, you must use Mobile App Builder to configure a header function in a mobile app to use the icon.
Mobile icon reference -- Use Mobile App Builder to insert these icons in your mobile apps.
Actions font icons -- Use actions font icons for functions. They can be used on buttons that are located on cards or for quick actions. Actions font icons are in the now-mobile-icons-buttons font family.
Screen font icons -- Use screen font icons for lists or section destinations. You can use them to represent a work flow or a screen that you want users to navigate to. Screen font icons are in the now-mobile-icons font family.
Mobile card font icons -- Use mobile card font icons in the body of mobile cards. Mobile card font icons are in the now-mobile-icons-cards font family.
Launcher screen font icons -- Use launcher screen font icons in the upper right corner of your mobile screen. They are used as navigation to another screen. Don't use these icons for quick actions. Launcher screen font icons are in the now-mobile-icons-ALPnavbar font family.
Image icons -- Use image icons on navigation bars and tab bars. Image icons are not font-type icons.
Empty state display -- Use an empty state to indicate to your users that the displayed page does not contain data. You can add an image, text, and buttons to direct users to perform an action, view a particular screen, or review specific information.
Configure an empty state -- Configure an empty state to inform users that a page currently does not contain data. Add an image, text, and buttons to customize the empty state and improve the user experience.
Working with images and attachments -- Learn how to turn off the image annotation option and define attachment sources when working with various mobile components.
Define available attachment sources -- 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.
Turn off image annotation -- By default users can edit and annotate images including actions like adding text, drawing, and highlighting areas. This feature is supported for all attachment locations, including: activity stream, functions with type “attachments,” and input form screens with field type “attachment."
Storing media locally -- Provide users with the option to save and retrieve pictures and videos taken with the camera on their mobile app, onto their device. By default, these images are saved for 24 hours on the phone’s local storage. You can set the storage time to be from 1 to 168 hours (1 week).
Now Assist for Mobile -- Use ServiceNow Now Assist for Mobile platform to summarize case information, generate case resolution notes, and more.
Exploring Now Assist -- With Now Assist for Mobile, your users can generate case resolution notes to wrap up cases faster, generate answers to search questions, and augment the Virtual Agent experience.
Now Assist AI Search on Mobile -- Use Now Assist Search on Mobile to provide actionable AI-generated or AI-selected answers to user searches. You can see citations for the sources that were used by Now Assist and navigate to them from the generated answer.
Now Assist in Virtual Agent -- Use Now Assist in Native Mobile Virtual Agent to deliver more direct, relevant, and conversational responses to questions using generative AI. Virtual Agent also enables you to provide feedback on AI-generated responses.
Now Assist AI agents -- Learn how the Now Assist AI agents can be integrated into Virtual Agent on your mobile app to help your organization improve live agent productivity by using AI agents to perform tasks.
Write with Now Assist -- Write with Now Assist enables generative-AI powered text generation and editing assistance natively in your mobile app.
Now Assist for Mobile Agent -- Use generative AI skills in your Mobile Agent app to get answers and complete tasks more efficiently.
Now Assist mobile SDK -- The ServiceNow mobile SDK with Now Assist enables you to use the power of generative AI in your custom mobile apps.
Now Assist Skill Kit -- The Now Assist Skill Kit plugin lets you create and activate custom prompts and skills for Now Assist on your mobile device.
ServiceNow AI Lens -- ServiceNow AI Lens enables you to harness generative AI to scan, extract, understand, and synthesize data directly from your phone or tablet, making it easy to optimize your workflows on the go.
Mobile AI Voice Agent -- The Mobile AI Voice Agent feature extends ServiceNow's voice agent capabilities to mobile devices, allowing users to receive automated support through natural voice conversations instead of text-based chat.
Configure a Lens launcher button -- Add a ServiceNow AI Lens button to input form screens to enable users to quickly extract data from attachments and complete forms faster.
Configure Mobile AI Voice Agent -- Follow these steps to enable the Mobile AI Voice Agent feature for your mobile app users. The AI Voice Agent can also be configured for a custom app.
Configure Now Assist button in search -- Add a conversational chat button to standard catalog search results in mobile. The chat button redirects users to a new Virtual Agent conversation for eligible catalog items.
Using Now Assist -- Use Now Assist for Mobile to enhance the mobile user experience.
Using standard chat -- Standard chat on mobile delivers an intuitive, text-based support experience within a static chat window, enhanced by AI-powered responses and integrated knowledge resources. You can interact with a Virtual Agent to resolve issues, access knowledge articles, and request catalog items all in one place.
Using enhanced chat -- Enhanced Chat on mobile offers a dynamic conversational support experience that integrates powerful AI-driven search and chat capabilities. You can seamlessly switch between multiple conversations, receive synthesized responses with inline citations, and access both knowledge articles and catalog items.
Using premium chat -- Premium Chat delivers a hybrid conversational experience that combines the flexibility of web-based Now Assist capabilities with the native mobile interface.
Using web search -- Web search mode for Now Assist lets you perform an internet search from within Now Assist, showing external results from outside your organization.
Generate a record summary -- Generate a summary of a record in your Now mobile app using Now Assist.
Using the prominent action button -- Use the prominent action button to quickly access your Now Assist agent chat no matter where you're in the app.
Using Voice Input for mobile -- The Voice Input feature allows users to easily transcribe spoken words into written text. Voice-to-text can be accessed directly from the search bar or Now Assist chat.
Using People Genius results on mobile -- Search for people in your organization and view their profiles by entering their name into your search bar.
Using Mobile AI Voice Agent -- Use Mobile AI Voice Agent to start voice conversations with an intelligent, AI-powered voice assistant.
Additional resources for Mobile Platform -- If you’re looking for Mobile Platform best practices, troubleshooting, or other implementation guidelines, select a feature or resource type to discover ServiceNow resources on other relevant websites.