{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":35033,"path":"mobile/offline-capabilities.md","title":"Mobile experience components available in offline mode","bundle":null,"doc_type":null,"release":"australia","body":"\n# Mobile experience components available in offline mode\n\nUse the tables to view the various components and features that are either fully, partially or not supported in offline mode.\n\nThe three table listed are categorized as follows:\n\n-   Component is fully supported, and the behavior is the same for both online and offline.\n-   Component is partially supported in offline with certain limitations.\n-   Component is not supported in offline.\n\n## Supported offline components\n\n<table id=\"table_fwk_jf5_njc\"><thead><tr><th>\n\nComponent\n\n</th><th>\n\nSub-component\n\n</th><th>\n\nConditions requited for offline flows to work\n\n</th><th>\n\nOptional dedicated offline configuration\n\n</th><th>\n\nDesign considerations\n\n</th><th>\n\nUse case\n\n</th></tr></thead><tbody><tr><td>\n\nMobile application\n\n</td><td>\n\nNow Mobile app, Mobile Agent app, Custom app, and Mobile Publishing\n\n</td><td>\n\nSet 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\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nMobile 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.\n\n Now Mobile app: Used by employees to submit requests, report issues, and track the status of their tickets or service requests.\n\n</td></tr><tr><td>\n\nNavigation tab\n\n</td><td>\n\nLauncher screen / screen\n\n</td><td>\n\nThe launcher screen or screen configured for the tab must be set as available offline.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nMobile home screen, navigation to different screens.\n\n</td></tr><tr><td>\n\nUI section\n\n</td><td>\n\nRecord UI section, icon UI section, legacy UI icon section, content UI section\n\n</td><td>\n\nFor the icon UI section and legacy icon UI section, the screen or function must be set as available offline.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nRecord UI section displays only cached records.\n\n</td><td>\n\nMy tasks, recent records, quick navigation tiles.\n\n</td></tr><tr><td>\n\nRecord screen\n\n</td><td>\n\nRelated list segment, record sections segment, activity stream segment\n\n</td><td>\n\nRelated records must be cached.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nLimited to cached records.\n\n</td><td>\n\nChild records, task history.\n\n</td></tr><tr><td>\n\nScreen\n\n</td><td>\n\nList screen, calendar screen\n\n</td><td>\n\nScreen must be set as available offline.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nLimited to 1000 records.\n\n</td><td>\n\nScheduled tasks\n\n</td></tr><tr><td>\n\nMobile cards\n\n</td><td>\n\nUI rules\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td></tr><tr><td>\n\nExecution\n\n</td><td>\n\nFunction instance\n\n</td><td>\n\nn/a\n\n</td><td>\n\nBy default, all button instance locations are available offline; a specific location can be inactive.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nThe location of the button within the screen, for example the footer area, top menu, or a specific field.\n\n</td></tr><tr><td>\n\nExecution of operations on records while offline\n\n</td><td>\n\nAction items such as write-back actions and write-back action steps\n\n</td><td>\n\nn/a\n\n</td><td>\n\n-   An offline step must be configured to support offline local database modifications that affect button conditions, displayed list records, or similar logic.\n-   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.\n\n</td><td>\n\n-   Scripted write-back action step is not supported.\n-   The offline step supports declarative configuration only and can modify only the record currently used as context by the write-back action.\n\n</td><td>\n\nWhen 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.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nData source\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nEnables the download of input form data for elements such as descriptive fields, input values, and values of input actions such as comments and attachments.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nInput actions\n\n</td><td>\n\nScripted write-back action required.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nAdd attachments, add a comment, navigate to another screen in the context of the input.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nDescriptive element\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nUsed to provide instructions to the user on how to respond to a question when completing questionnaires.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nString input, number input, Boolean input, date/datetime input, barcode input\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nAttachment input\n\n</td><td>\n\nScripted write-back action required.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nAuto-fill inputs and input actions\n\n</td><td>\n\nDependent data cached.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nMay fail if reference data is missing.\n\n</td><td>\n\nForms pre-populated with data downloaded from the instance.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nSave progress\n\n</td><td>\n\nLocal save write-back action step is required.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td></tr></tbody>\n</table>## Partially supported offline components\n\n<table id=\"table_lx5_nnj_rjc\"><thead><tr><th>\n\nComponent\n\n</th><th>\n\nSub-component\n\n</th><th>\n\nConditions requited for offline flows to work\n\n</th><th>\n\nOptional dedicated offline configuration\n\n</th><th>\n\nDesign considerations\n\n</th><th>\n\nUse case\n\n</th></tr></thead><tbody><tr><td>\n\nUI section\n\n</td><td>\n\nMedia UI section\n\n</td><td>\n\nMedia assets must be available locally.n/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nRemote media assets, for example YouTube videos, aren't available offline.\n\n</td><td>\n\nCampaigns with banners and images.\n\n</td></tr><tr><td>\n\nRecord screen\n\n</td><td>\n\nDetails segment\n\n</td><td>\n\nRecord data must exist locally.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nChecklist field type not supported.\n\n Video field type not supported.\n\n</td><td>\n\nFields that represent the record, such as description, assignment group, and attached files.\n\n</td></tr><tr><td>\n\nScreen\n\n</td><td>\n\nMap screen\n\n</td><td>\n\nScreen must be set as available offline.\n\n</td><td>\n\nn/a\n\n</td><td>\n\nList view only is supported.\n\n Limited to 1000 records.\n\n</td><td>\n\nTask location view.\n\n</td></tr><tr><td>\n\nScreen\n\n</td><td>\n\nInput forms\n\n</td><td>\n\nThe screen and function that triggers the form must be set as available offline.\n\n</td><td>\n\nEnable merge of any consecutive outbox items.\n\n</td><td>\n\nClient scripts not supported.Dependent inputs may fail if reference data is not cached.\n\n</td><td>\n\nCreate or edit records while offline.\n\n</td></tr><tr><td>\n\nScreen\n\n</td><td>\n\nData item\n\n</td><td>\n\nConfigured for offline caching.\n\n</td><td>\n\nDedicated offline data item, pre-cached before device download.\n\n</td><td>\n\n-   Query limitations of 1000 records per screen segment.\n-   Parameterized data item not supported.\n-   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.\n\n</td><td>\n\nRecord data retrieval\n\n</td></tr><tr><td>\n\nScreen\n\n</td><td>\n\nMobile cards\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nVideos not supported.\n\n</td><td>\n\nUI 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.\n\n</td></tr><tr><td>\n\nExecution\n\n</td><td>\n\nFunction\n\n</td><td>\n\nFunction must be set as available offline.\n\n</td><td>\n\nOffline conditions for button visibility.\n\n</td><td>\n\nSupported types: navigation, action item \\(create, update, delete record\\), upload attachment.\n\n</td><td>\n\nUsed across different screens to define the action performed when the button is tapped.\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nUI rules\n\n</td><td>\n\nn/a\n\n</td><td>\n\nn/a\n\n</td><td>\n\nClient scripts not supported.\n\n</td><td>\n\nn/a\n\n</td></tr><tr><td>\n\nInput form\n\n</td><td>\n\nReference input\n\n</td><td>\n\nn/a\n\n</td><td>\n\nSpecific offline attributes for the control can be configured.\n\n</td><td>\n\n1000 records can be cached.\n\n</td><td>\n\nAssign a user to a task.\n\n</td></tr></tbody>\n</table>## Non-supported offline components\n\n|Component|Sub-component|Conditions requited for offline flows to work|Optional dedicated offline configuration|Design considerations|Use case|\n|---------|-------------|---------------------------------------------|----------------------------------------|---------------------|--------|\n|UI section|Analytics section|n/a|n/a|n/a|KPI dashboards|\n|Launcher screen|Search bar|n/a|n/a|n/a|n/a|\n|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|\n|Input form|Signature input type, screen input type, custom map input type|n/a|n/a|n/a|n/a|\n|Input form|AI summarization|n/a|n/a|AI capabilities not supported offline.|AI text summarization for resolution notes.|\n|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.|\n|Chat|Virtual agent \\(VA\\)|n/a|n/a|n/a|Self-service chat for employees or customers.|\n|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.|\n\n**Parent Topic:**[Offline mode](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/mobile-offline-mode.md)\n\n"}}