Now Support for Android v17.4.0

  • Release version: Mobile
  • Updated April 4, 2024
  • 2 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 Now Support for Android v17.4.0

    The Android v17.4.0 release enhances the ServiceNow mobile application by providing critical fixes and performance improvements. Users can easily download the latest version from the Google Play store. A demo is also available for new users to explore the ServiceNow Agent app.

    Show full answer Show less

    Key Features

    • Link Navigation Fix: Addresses issues where users could not follow links to third-party applications.
    • PDF Rendering Improvement: Corrects the rendering of pre-filled PDFs that previously led to corruption due to non-embedded fonts.
    • Back Navigation Correction: Fixes the back button functionality to ensure users return to the previous screen rather than the main screen.
    • Offline Mode Stability: Resolves crashes and blank screens that occurred after actions were performed in offline mode with large documents.
    • Legacy List Optimization: Reduces unnecessary getGroup requests that caused duplicate list items when scrolling through legacy lists.

    Key Outcomes

    With the updates in v17.4.0, ServiceNow customers can expect a more reliable and efficient mobile experience. Users will benefit from smoother navigation, improved PDF handling, and enhanced offline functionality, leading to increased productivity and user satisfaction. Additionally, the performance improvements contribute to a more responsive app overall.

    The Android v17.4.0 release provides fixes for the application.

    Download the latest mobile app version

    To download the latest release, visit the Google Play store. Users can launch a demo to try the ServiceNow Agent app. You can use a demo account from the initial post-download screen or the instance list screen.

    Fixed in this release

    Problem Short description Description Steps to reproduce

    Mobile Android

    PRB1739688

    		 The user is unable to follow links to third party apps

    Mobile Android

    PRB1729686

    		 PDFs with pre-filled form data do not render properly Pre-filled PDFs with fonts that aren't embedded result in a corrupted file.

    Mobile Android

    PRB1735791

    		 The Back button sends the user to the main screen instead of the previous screen
    1. In the Now Mobile app, navigate to the 'Support' tab in the lower part of the screen.
    2. In 'Browse all topics' click See all.
    3. Click IT5.
    4. Click any topics in IT topics.
    5. Choose any topic that is available.
    6. Click an article.
    7. Click the Back button of Android mobile.

    Expected behavior: The user is directed to the previous screen.

    Actual behavior: The user is directed back to the Browse all topics > See all screen.

    Mobile Android

    PRB1741217

    		 A blank screen or crash occurs after an action is performed in offline mode When Android is in offline mode with large documents in memory, an action may result in the Android OS killing the activities in the back stack. If the action is on a form screen and requires user input from a form, the memory pressure increases. The TabsActivity may get killed by the OS, and the form screen view model is then cleared. As a result, the bundle containing the form template is no longer available. This results in a blank screen.

    Mobile Android

    PRB1744555

    		 Unnecessary getGroup requests are sent to mobile scripts when the user reaches the bottom of a legacy list Swiping up after reaching the end of the list sends additional getGroup requests to mobile scripts, resulting in duplicate list items.
    1. Configure a legacy list (related list) in a record screen using a scripted data item or a declarative data item with a parameter.
    2. Mark both the record screen and the legacy list as available offline.
    3. Download offline cache.
    4. Go offline.
    5. Tap the legacy list.
    6. Scroll to the bottom and swipe up again.

    Expected behavior: The client stops sending getGroup requests.

    Actual behavior: Additional getGroup requests are sent to mobile scripts, resulting in duplicate list items.

    This version also includes other minor bug fixes and performance improvements.