Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Mobile Hierarchy

Log in to subscribe to topics and get notified when content changes.

Mobile Hierarchy

Learn the components of ServiceNow® mobile and how the work together to assist you in configuring, modifying, and creating applications.

Components of the ServiceNow mobile framework

This image represents the structure of the ServiceNow mobile framework. The next sections detail specific areas of the overall hierarchy, and descriptions of individual components.

Diagram showing how the mobile app is comprised of application launchers, applets, and functions.

Native clients

Components of the Native Client
Native client

Your users access ServiceNow® mobile from a native client such as ServiceNow Agent, Now Mobile, or Mobile Onboarding. After logging in, your users will see an applet launcher screen, and a navigation bar.

Navigation bar

The navigation bar is a configurable menu bar that appears at the bottom of all mobile application screens. The navigation bar has up to five icons, called tabs, which access settings and notifications for your users, as well commonly used applets or application launch pages.

Navigation bar tabs
Each tab in the navigation bar represents an applet or applet launcher. When you add more than five tabs to the navigation bar, a More tab appears. Tapping the More tab appears a list showing the tabs that did not fit in the navigation bar. You can configure these tabs so your users have quick access to the functions they need most often
Applet launchers

Applet launchers serve as a landing pages or home pages for your users. Applet launchers contain a configurable header, and UI sections to provide access to applets in several formats. You can also configure Applet launchers with a global search bar, and quick actions, which give your users access to commonly used functions.

Applets

Applets provide your users a method to view and modify data on your instance. Applets can display information as lists, maps, record forms, and other formats. You can find more detail on applet components in the next section.

More information
For more information, See:

Applets

Components of the Native Client
Segments

Applets contain one of more segments, which display information from your instances to your users. Segments represent the lists, calendars, maps, and forms your users see within the app. If an applet has more than one segment, your users can switch between segments using a tabbed interface.

Segments records for lists, calendars, and maps are located on the Item Stream Segment [sys_sg_item_stream_segment] table. Segments records for forms are located on the Form Screen Segment [sys_sg_form_segment] table.

Icons

Each applet has an icon. This icon represents the applet when it is displayed in an applet launcher or the navigation bar.

Icon records are located on the Icons [sys_sg_icon] table.

Item streams

An item stream is the source for the data shown in your applet. An item stream gets its data from a single source, called a data item. You can associate more than one item stream to a segment to include data from multiple tables. For example, you could create two item streams to display items from both the incident [incident] and request item [sc_req_item] tables in a single list.

Item streams are also associated with one or more master items, which provides a pattern controlling how the data appears in your segment.

Item stream records are located in the Item Stream [sys_sg_item_stream] table.

Data items

Data items provide the data presented in an applet. A data item is a dataset correlated with a table in an instance. A data item can include a filter condition to restrict what data the item returns. Associate data items with applets so that the applets can transform the dataset into human-readable information.

Data items are located on the Data Items [sys_sg_data_item] table.

Master items

Master items provide a pattern for data in your applet, and control how your data appears within a segment. For more detail on how a master item controls the appearance of your data, see the master item section.

Master items are located on the Master Item [sys_sg_master_item] table.

More information
For more information, See:

Segments

Components of the Native Client
Segments

Applets contain one of more segments, which display information from your instances to your users. Segments represent the lists, calendars, maps, and forms your users see within the app. If an applet has more than one segment, your users can switch between segments using a tabbed interface.

Segments records for lists, calendars, and maps are located on the Item Stream Segment [sys_sg_item_stream_segment] table. Segments records for forms are located on the Form Screen Segment [sys_sg_form_segment] table.

Screens
Screen types determine what an applet looks like and how your users are able to interact with it. You can create applets with these screen types:
  • List
  • Form
  • Employee directory
  • Map
  • Group list
  • Calendar
  • URL
In addition to these types, you can add the following screens to segments in your applets:
  • Details screen
  • Activity stream screen
  • Related list screen
  • Embedded list screen
Browser
In addition to the native screens, your mobile applets can display content in a browser. Use this capability to display information outside your instance, or access content within your instance, such as service portal pages.
Functions

Your users can use functions to perform tasks in the mobile app such as assigning a task, or navigating from a record to related record. Actions can also interact with your mobile device to send emails, navigate using map software, or make a phone call.

Functions are located on the Function [sys_sg_button] table.

Master items

Components of the Native Client
Item view

Item views determine the formatting and appearance for fields in your applets. When you select a screen template when creating an applet, you are actually selecting the item view. Item views use JSON to determine the configuration for fields in your applet.

Item views are located on the Item view [sys_sg_item_view] table.

Conditions
Master items include condition a Condition field. This field sets filter conditions which restrict what records appear when a master item is used. The conditions used by the master item are used in addition to those in place in the data item.
Table

Each item view record contains a Table field. This field determines the content the item view appears.

Pattern

Each item view record contains an Item view JSON field that contains a JSON. This JSON defines a pattern to control how data appears on the screen. The instance automatically creates this JSON when you select an applet template while designing applets in Studio. It is possible to manually create a pattern within an item view record, but Studio may not recognize these custom patterns.

UI styles

UI styles change the color of fields in an applet. You can associate an item view record with one or more UI styles. Each UI style applies to a single table, and only applies under conditions you set within the UI style record.

UI styles are located on the UI Styles [sys_sg_ui_style] table.

Screen UI Policies

Screen UI policies are similar to the UI policies that are used on forms in the instance, but screen UI policies are designed for the mobile app. Policies contain a set of conditions that you can use to determine when the policy applies. When a screen UI policy is triggered by a condition that you defined for the policy, all UI policy rules that are associated with that policy are applied.

More information
For more information, See:
Feedback