Mobile deep link structure

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Mobile deep link structure

    This content explains how to construct and use mobile deep links within ServiceNow mobile apps, including Now Mobile and Mobile Agent. Mobile deep links enable direct navigation to specific screens or actions inside these apps by using a structured coding approach consisting of a variable name, a mobile app reference, and a public method to generate the link.

    Show full answer Show less

    Key Features

    • Variable Name: Assign any identifiable name to the deep link variable for easy reference in code.
    • Mobile App Call: Specify the target mobile app by name, such as Request for Now Mobile or Agent for Mobile Agent, to generate links specific to each app.
    • Public Methods to Generate Links: Several methods tailor deep links to different screen types and use cases:
      • getButtonLink(buttonId, tableName, recordSysId): Links to an input form screen launched by a specific button.
      • getFormScreenLink(formScreenId, tableName, recordSysId): Links to a non-parameterized form screen.
      • getLauncherScreenLink(launcherScreenId): Links to a launcher screen.
      • getPrefillLink(forceLocalLogin): Provides a pre-filled instance login link for first-time mobile users; controls whether login details are auto-filled.
      • getScreenLink(documentId, uiParams): Links to any list or non-parameterized screen, optionally accepting UI parameters.
      • getSSOPrefillLink(sysid): Generates single sign-on pre-filled links tied to a specific identity provider (IdP); requires Multi-Provider SSO plugin activation and an active IdP.
      • getUniversalLink(url): Creates links to lists, forms, or browser views based on a URL resource.

    Practical Applications for ServiceNow Customers

    By using mobile deep links, customers can streamline mobile app navigation, improve user experience, and automate workflows by directing users exactly where they need to go within the Now Mobile or Mobile Agent apps.

    For example, admins and developers can embed links that open specific forms, launcher screens, or lists directly, and can facilitate easy onboarding with pre-filled login links or secure access via SSO links tailored to different identity providers.

    Activating the Multi-Provider SSO plugin and configuring identity providers is necessary to leverage SSO deep links, enhancing secure mobile authentication.

    Overall, understanding and applying these mobile deep link structures enables ServiceNow customers to create efficient, user-friendly, and secure mobile experiences tailored to their organizational needs.

    Familiarize yourself with how to construct and use mobile deep links in any screen type within a mobile app.

    Mobile deep links essentially consist of three components. The name of the variable, a reference to a mobile app, and the public method used to pull the mobile deep link. The following mobile deep link has a variable with the name deepLinkGen, where a specified screen opens in the Mobile Agent.

    var deepLinkGen= new global.MobileDeepLinkGenerator('Agent');
 return deepLinkGen.getScreenLink('73f3d135532033002d96ddeeff7b1212');
    Variable name
    You can give any variable name for the mobile deep link, although it should be identifiable for future reference.
    Mobile app call
    Enter one of the mobile apps that the mobile deep link points to. You can enter either Request for the Now Mobile app or Agent for the Mobile Agent app. For example, to generate a link using the mobile deep link generator that points to the Now Mobile app, use the following code: new global.MobileDeepLinkGenerator('Request');
    Public method
    Use one of the public methods that can be used to create a mobile deep link. Reference the table for an explanation of each method, and the reason for its use.
    Method Reason for use Method parameters
    getButtonLink(buttonId, tableName, recordSysId) getButtonLink is used to link into any input form screen. buttonId (required): sys_id of the button you want to launch the input form screen

    tableName (optional): name of the table for the current context

    recordSysId (optional): sys_id of the current context record
    getFormScreenLink(formScreenId, tableName, recordSysId) getFormScreenLink is used to link into any non-parameterized form screen. formScreenId (required): sys_id of required form screen

    tableName (required): table name of required form screen

    recordSysId (required): sys_id of record from tableName
    getLauncherScreenLink(launcherScreenId) getLauncherScreenLink is used to link into any launcher screen. launcherScreenId (required): sys_id of the required launcher screen.
    getPrefillLink(forceLocalLogin) getPrefillLink is useful for first-time ServiceNow mobile users. This link format pre-fills the instance link for users who have not yet added an instance to their mobile app. This method is the default authentication experience.

    This method does not generate a link to a specific screen.

    		 forceLocalLogin (required):

    Enter true for the system to pre-fill the instance login details of the user.

    Enter false, for the user to manually enter login details.
    getScreenLink(documentId, uiParams) getScreenLink is used to link into any list screens, including both parameterized and non-parameterized types. Can also be used for any non-parameterized screen type. An optional UI parameter can be passed into this method. documentId (required): sys_id of desired screen

    uiParams (optional): Parameter of a data item
    getSSOPrefillLink(sys_id) getSSOPrefillLink generates a link that uses the identity provider (IdP) that is identified by the sys_id parameter. This link can be used to authenticate end users that use different IdPs. For example, pre-hires might use Microsoft Azure as their IdP, and on-boarded employees might use Okta as their IdP. A common use of these SSO (single sign-on) pre-filled links is to embed them in emails sent to employees. These emails contain a link that can be used to log in securely to a ServiceNow instance using their mobile apps.
    Important:
    You must activate the Multi-Provider SSO plugin and have an active IdP to use this method. For more information, see Activate Multi-Provider SSO plugin
    		 sys_id (required): Enter the sys_id of the IdP you want to use from the Identity Providers [sso_properties] table.
    To get the sys_id of the IdP:
    1. Navigate to All > Multi-Provider SSO > Identity Providers.
    2. Right-click an identity provider record and select Copy sys_id.
    getUniversalLink(url) getUniversalLink generates a link into either a list, form, or browser. A screen is generated based on the content of this URL. See Universal linking for mobile. url (required): a link to a resource on an instance