Mobile hierarchy
Summarize
Summary of Mobile hierarchy
The Mobile hierarchy in ServiceNow's Mobile Platform defines how mobile apps are structured and configured to deliver tailored user experiences. It includes components such as mobile apps, app configurations, navigation bars, screens, and data elements that work together to enable users to interact with ServiceNow data effectively on mobile devices.
Show less
Mobile App Configuration
- Mobile Apps: There are two primary mobile apps: the Now Mobile app and the Mobile Agent app. Each app targets specific user personas to support their organizational roles.
- Mobile App Config: Defines the user experience presented after login, based on configured conditions. Each app can have multiple configurations tailored to different user needs.
- Navigation Bar: Appears at the bottom of the app screen, containing up to five navigation bar tabs (icons). Additional tabs appear under a "More" tab. Default tabs include notifications and settings.
- Navigation Bar Tabs: Represent screens or launcher screens that users can access directly from the navigation bar.
- Launcher Screens: Act as home or landing pages with configurable headers, sections, search bars, and quick actions to facilitate common user tasks.
Screens and Screen Segments
- Screens: Enable users to view and modify instance data in various formats such as lists, maps, and records.
- Screen Segments: Subsections within screens that display specific data views like lists, calendars, maps, or records. Multiple segments can be accessed via tabs.
- Screen Types: Include Calendar, Chart, Form, Grouped List, List, Map, and URL. Additional segments for record screens include details, activity stream, related lists, and embedded lists.
- Icons: Visual representations of screens used in launcher screens and navigation bars, managed via the icons table.
Data Management Components
- Item Streams: Define the data sources for screen segments by associating one or more data items. They enable combining data from multiple tables (e.g., incidents and request items).
- Data Items: Represent datasets tied to specific instance tables, with optional filters to limit data returned. They supply the raw data for screens.
- Item Configurations: Control the layout and appearance of data within screen segments, ensuring data is presented in a user-friendly format.
Functions
Functions enable users to perform actions within the mobile app, such as assigning tasks or navigating between records. They can also trigger device-specific actions like sending emails, launching map navigation, or making phone calls, enhancing user productivity.
What This Enables for ServiceNow Customers
Understanding the Mobile hierarchy empowers you to configure and customize mobile apps to meet the specific needs of different user roles in your organization. By leveraging app configurations, navigation elements, and flexible screen and data components, you can create intuitive and efficient mobile experiences. This helps your users access and act on critical ServiceNow data anytime, anywhere, improving responsiveness and operational efficiency.
Learn the components of ServiceNow® mobile and how they 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.
Mobile App Configuration
- Mobile app
- A part of the ServiceNow® Mobile Platform, there are 2 mobile apps: the Now Mobile app and the Mobile Agent app. Each app focuses on a persona, which means the app experiences are tailored to support the tasks of specific roles in your organization. Each mobile app can have one or more mobile app configurations. For more information, see the following "Mobile app config" section.
- Mobile app config
When users download a ServiceNow Mobile Platform application, they are prompted to log in with their credentials. When a user logs in to the instance, they are presented an experience that is created by a single mobile app config. The mobile app config that defines the user's experience depends on conditions defined in the config.
- Navigation bar
Each mobile app config has a navigation bar that appears at the bottom of the screen. A navigation bar can have up to five icons, called navigation bar tabs. By default, navigation bars have a notification and settings navigation bar tab. For information about how to create a navigation bar, see Configure the navigation bar and navigation tabs.
- Navigation bar tabs
Each tab in the navigation bar represents a screen or launcher screen. When you add more than five tabs to the navigation bar, a More tab appears. Tapping the More tab opens a list view showing additional tabs.
- Launcher screens
Launcher screens serve as landing pages or home pages for your users. Launcher screens contain a configurable header, and sections to provide access to screens in several formats. You can also configure launcher screens with a search bar and quick actions, which give your users access to commonly used functions.
- Screens
Screens provide your users a method to view and modify data on your instance. Screens can display information as lists, maps, records, and other formats. You can find more detail on screen components in the next section.
Screens
- Screen segments
Screens contain one or more screen segments, which display information from your instances to your users. Screen segments represent the lists, calendars, maps, and records your users see within the app. If a screen has more than one screen segment, your users can switch between screen segments using a tabbed interface.
Screen segment records for lists, calendars, and maps are located on the screen segment [sys_sg_item_stream_segment] table. Screen segment records for record screens are on the record screen segment [sys_sg_form_segment] table.
- Icons
Each screen has an icon. This icon represents the screen when it is displayed in a launcher screen 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 screen. An item stream gets its data from a single source, called a data item. You can associate more than one item stream to a screen 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 item configurations. These item configurations provide a pattern controlling how the data appears in your screen segment.
Item stream records are located in the item stream [sys_sg_item_stream] table.
- Data items
Data items provide the data presented in a screen. 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 screens so that the screens can transform the dataset into human-readable information.
Data items are located on the data items [sys_sg_data_item] table.
- Item configurations
Item configurations provide a pattern for data in your screen, and control how your data appears within a screen segment. For more detail on how an item configuration controls the appearance of your data, see the item configuration section.
Item configurations are located on the item configuration [sys_sg_master_item] table.
- More information
- For more information, See:
Screen segments
- Screens
- Screen types determine what a screen looks like and how your users are able to interact with it. You can create these screen types:In addition to these types, you can add the following screens to segments in your record screen:
- Details screen
- Activity stream screen
- Related list screen
- Embedded list screen
- Functions
Your users can use functions to perform tasks in the mobile app such as assigning a task, or navigating between records. 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.