---
sourceDocument: Brazil Mobile Configuration and Navigation
sourceDocumentLink: https://www.servicenow.com/docs/r/mobile

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Mobile experience components

# Mobile experience components available in offline mode {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Experience Components Available in Offline Mode

This guide outlines the support status of various mobile experience components within ServiceNow's Now Mobile app and related applications when used offline.
It categorizes components as fully supported, partially supported, or not supported in offline mode.
Understanding this helps ServiceNow customers effectively configure and optimize mobile workflows for users who need to work without continuous internet connectivity.
Show full answer Show less  

## Fully Supported Offline Components

* **Mobile Applications:** Now Mobile app, Mobile Agent app, Custom apps, and Mobile Publishing can be enabled for offline mode. However, enabling offline requires configuring each screen and function individually for offline use.
* **Navigation and UI Sections:** Launcher screens, navigation tabs, and UI sections such as record UI sections and icon sections are fully available offline when configured.
* **Record and List Screens:** Cached records and related lists are accessible offline, with lists supporting up to 1000 records.
* **Execution Functions and Action Items:** Buttons and actions configured for offline can modify local data with offline steps and sync changes when back online. Scripted write-back actions are not supported offline.
* **Input Forms:** Various input types including string, number, Boolean, date/time, barcode inputs, and attachment inputs are supported offline if configured with appropriate write-back actions. Descriptive elements for user instructions are also supported offline.

## Partially Supported Offline Components

* **UI Media Sections:** Media assets must be cached locally; remote media like YouTube videos are unavailable offline.
* **Record Screen Details:** Local record data is required; certain field types like checklist and video fields are unsupported offline.
* **Map Screens:** Offline support is limited to list views only, with a 1000-record cap.
* **Input Forms and Data Items:** Screens must be configured for offline use, but client scripts are unsupported, and some dependent data may fail if not cached.
* **Mobile Cards and Execution Functions:** Mobile cards display cached summaries, though video content is unsupported. Functions require offline configuration for button visibility and supported actions.

## Not Supported Offline Components

* **Analytics and Dashboard Components:** KPI dashboards, chart screens, and embedded web content like catalog items or knowledge articles are not available offline.
* **Advanced Input Types and AI Features:** Signature inputs, custom map inputs, and AI summarization capabilities are unsupported offline.
* **Action Dialogs and Chat Features:** Mobile pop-ups for warnings and real-time chat tools such as Virtual Agent and ServiceNow Sidebar are not functional offline.

## Practical Implications for ServiceNow Customers

To enable effective offline mobile experiences, customers must:

* Explicitly configure each mobile screen and function for offline availability, beyond enabling offline mode on the app itself.
* Pre-cache necessary data, including records and media, to enable offline access and interactions.
* Design workflows considering limitations such as lack of client script support and capped record counts.
* Use declarative offline steps for write-back actions and ensure corresponding online steps exist to sync changes.
* Expect some advanced features and multimedia content to be unavailable offline, and plan fallback experiences accordingly.

By understanding these capabilities and constraints, customers can better deliver mobile solutions that support users working in low or no connectivity environments while maintaining data integrity and workflow continuity.  
Use the tables to view the various components and features that are either fully, partially or not supported in offline mode.
The three table listed are categorized as follows:

* Component is fully supported, and the behavior is the same for both online and offline.
* Component is partially supported in offline with certain limitations.
* Component is not supported in offline.
{#offline-capabilities__ul_yfh_h4d_njc}

## Supported offline components {#offline-capabilities__section_w3d_mtd_njc}

{#offline-capabilities__table_fwk_jf5_njc__entry__6}

| Component | Sub-component | Conditions requited for offline flows to work | Optional dedicated offline configuration | Design considerations | Use case |
|-|-|-|-|-|-|
| Mobile application | Now Mobile app, Mobile Agent app, Custom app, and Mobile Publishing | Set the application to support offline mode. Note: Enabling the mobile app as offline is not sufficient, as every screen and function involved must also be configured for offline use. | n/a | n/a | Mobile Agent app: Used by employees such as technicians or support agents to view, update, and complete assigned tasks, incidents, or work orders while on the go. Now Mobile app: Used by employees to submit requests, report issues, and track the status of their tickets or service requests. |
| Navigation tab | Launcher screen / screen | The launcher screen or screen configured for the tab must be set as available offline. | n/a | n/a | Mobile home screen, navigation to different screens. |
| UI section | Record UI section, icon UI section, legacy UI icon section, content UI section | For the icon UI section and legacy icon UI section, the screen or function must be set as available offline. | n/a | Record UI section displays only cached records. | My tasks, recent records, quick navigation tiles. |
| Record screen | Related list segment, record sections segment, activity stream segment | Related records must be cached. | n/a | Limited to cached records. | Child records, task history. |
| Screen | List screen, calendar screen | Screen must be set as available offline. | n/a | Limited to 1000 records. | Scheduled tasks |
| Mobile cards | UI rules | n/a | n/a | n/a | n/a |
| Execution | Function instance | n/a | By default, all button instance locations are available offline; a specific location can be inactive. | n/a | The location of the button within the screen, for example the footer area, top menu, or a specific field. |
| Execution of operations on records while offline | Action items such as write-back actions and write-back action steps | n/a | * An offline step must be configured to support offline local database modifications that affect button conditions, displayed list records, or similar logic. * If an offline step is configured, an online step must also be configured to apply local database changes to the instance once the device returns online. {#offline-capabilities__ul_kfb_55v_njc} | * Scripted write-back action step is not supported. * The offline step supports declarative configuration only and can modify only the record currently used as context by the write-back action. {#offline-capabilities__ul_ojc_w5v_njc} | When a user performs an action offline, changes are marked for later sync with the instance. To confirm these changes are immediately reflected in app workflows such as list filtering and conditional button visibility, the admin must define logic for handling insert, update, or delete operations, keeping the local database consistent with the expected flow. |
| Input form | Data source | n/a | n/a | n/a | Enables the download of input form data for elements such as descriptive fields, input values, and values of input actions such as comments and attachments. |
| Input form | Input actions | Scripted write-back action required. | n/a | n/a | Add attachments, add a comment, navigate to another screen in the context of the input. |
| Input form | Descriptive element | n/a | n/a | n/a | Used to provide instructions to the user on how to respond to a question when completing questionnaires. |
| Input form | String input, number input, Boolean input, date/datetime input, barcode input | n/a | n/a | n/a | n/a |
| Input form | Attachment input | Scripted write-back action required. | n/a | n/a | n/a |
| Input form | Auto-fill inputs and input actions | Dependent data cached. | n/a | May fail if reference data is missing. | Forms pre-populated with data downloaded from the instance. |
| Input form | Save progress | Local save write-back action step is required. | n/a | n/a | n/a |
[ ]

{#offline-capabilities__table_fwk_jf5_njc}

## Partially supported offline components {#offline-capabilities__section_kx5_nnj_rjc}

{#offline-capabilities__table_lx5_nnj_rjc__entry__6}

| Component | Sub-component | Conditions requited for offline flows to work | Optional dedicated offline configuration | Design considerations | Use case |
|-|-|-|-|-|-|
| UI section | Media UI section | Media assets must be available locally.n/a | n/a | Remote media assets, for example YouTube videos, aren't available offline. | Campaigns with banners and images. |
| Record screen | Details segment | Record data must exist locally. | n/a | Checklist field type not supported. Video field type not supported. | Fields that represent the record, such as description, assignment group, and attached files. |
| Screen | Map screen | Screen must be set as available offline. | n/a | List view only is supported. Limited to 1000 records. | Task location view. |
| Screen | Input forms | The screen and function that triggers the form must be set as available offline. | Enable merge of any consecutive outbox items. | Client scripts not supported. Dependent inputs may fail if reference data is not cached. | Create or edit records while offline. |
| Screen | Data item | Configured for offline caching. | Dedicated offline data item, pre-cached before device download. | * Query limitations of 1000 records per screen segment. * Parameterized data item not supported. * Scripted data item conditions are evaluated only when the offline cache is generated. Once the data is downloaded and the user is offline, the script no longer runs. The app uses the pre-generated query string to filter the data as it was prepared at download time. {#offline-capabilities__ul_mx5_nnj_rjc} | Record data retrieval |
| Screen | Mobile cards | n/a | n/a | Videos not supported. | UI components used to display a compact summary of a record or information block in a visually structured way inside mobile screens. Mobile cards are commonly implemented in list screen and home tab sections. |
| Execution | Function | Function must be set as available offline. | Offline conditions for button visibility. | Supported types: navigation, action item (create, update, delete record), upload attachment. | Used across different screens to define the action performed when the button is tapped. |
| Input form | UI rules | n/a | n/a | Client scripts not supported. | n/a |
| Input form | Reference input | n/a | Specific offline attributes for the control can be configured. | 1000 records can be cached. | Assign a user to a task. |
[ ]

{#offline-capabilities__table_lx5_nnj_rjc}

## Non-supported offline components {#offline-capabilities__section_xf2_rnj_rjc}

{#offline-capabilities__table_yf2_rnj_rjc__entry__6}

| Component | Sub-component | Conditions requited for offline flows to work | Optional dedicated offline configuration | Design considerations | Use case |
|-|-|-|-|-|-|
| UI section | Analytics section | n/a | n/a | n/a | KPI dashboards |
| Launcher screen | Search bar | n/a | n/a | n/a | n/a |
| Screen | Chart screen, mobile web screen | n/a | n/a | Performance analytics and embedded web content such as catalog items or knowledge articles aren't supported. Use a record screen with HTML content instead. | n/a |
| Input form | Signature input type, screen input type, custom map input type | n/a | n/a | n/a | n/a |
| Input form | AI summarization | n/a | n/a | AI capabilities not supported offline. | AI text summarization for resolution notes. |
| Action dialog | Mobile pop-ups | n/a | n/a | n/a | Warning message that prompts the user to choose whether to proceed with the flow or cancel it. For example, notifying the user that their shift is about to end when they attempt to accept a task. |
| Chat | Virtual agent (VA) | n/a | n/a | n/a | Self-service chat for employees or customers. |
| Chat | Sidebar | n/a | n/a | n/a | ServiceNow Sidebar is a real-time, record-based collaboration tool that allows agents to privately chat and share knowledge with subject matter experts to quickly resolve tasks, cases, and incidents. |
[ ]

{#offline-capabilities__table_yf2_rnj_rjc}