Now Mobile - Intune for Android v17.3.0
Summarize
Summary of Now Mobile - Intune for Android v17.3.0
The Android v17.3.0 release of the Now Mobile - Intune app includes essential fixes and updates to enhance user experience. Customers can download the latest version from the Google Play store and try a demo of the ServiceNow Agent app using a demo account available after download.
Show less
Key Features
- Attachment Access: Fixed an issue where attachments could not be opened on Android devices.
- Notification Functionality: Resolved a problem with banner push notifications that previously led to an infinite loading screen.
- UI Consistency: Addressed inconsistencies in currency display between Android and iOS.
- Form Submission: Fixed an issue with mandatory choice fields that prevented form submission under certain conditions.
- Barcode Scanning: Improved focus shifting after scanning with an external device.
- Universal Link Compliance: Ensured that the app respects the disabled universal link properties setting.
- Attachment Integrity: Fixed issues with attachments becoming corrupted after upload.
- Paging Functionality: Resolved paging issues within item sections for offline records.
Key Outcomes
With this update, users can expect a more reliable experience with improved functionality for attachments, notifications, and form submissions. These enhancements contribute to a smoother workflow and better performance of the application, ensuring that ServiceNow customers can effectively manage their mobile tasks. Overall, this release focuses on resolving critical issues and optimizing app performance for Android users.
The Android v17.3.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 PRB1734432 |
The user is unable to view an attachment | An attachment in Android does not open when clicked and shows the message 'Can't open file. Try saving the file on the device and then opening it.' | |
Mobile Android PRB1733542 |
The user is unable to open a banner push notification | Tapping a banner notification leads to an infinite load screen in the app. |
Expected behavior: The App should open and navigate the user to the Notifications tab. Actual behavior: The page gets stuck and displays a spinning circle. |
Mobile Android PRB1726649 |
When an agent sends an image file to a mobile chat user, there's a false indication that the agent is typing | When workspace agent sends an image to mobile end user, the UI of the mobile app indicates that the agent is still typing when they are not. | |
Mobile Android PRB1729792 |
Inconsistency between Android and iOS in displaying currency fields in List view | For example, A$ 3.40 in Android is $AUD 3.40 in iOS. | |
Mobile Android PRB1733802 |
The input form screen mandatory choice submit field rule doesn't work when a choice is deselected | The user can't submit a form when a mandatory field is empty. However, they can get around this by populating then depopulating a field before submitting. | |
Mobile Android PRB1716477 |
Barcode scanning with an external zebra scanning device doesn't automatically shift focus to the next field after scanning | The user needs to manually tap the next field in order for the barcode scan to work. | |
Mobile Android PRB1734336 |
The client does not honor a disabled universalLink Properties rule. | The client does not honor SystemProperty.universal LinkProperties.enabled = false. |
Expected behavior: The client does not make an API call to Universal Links. Actual behavior: The client makes a request to the Universal Links API and displays the "Error loading URL" screen. |
Mobile Android PRB1735778 |
Attachments become corrupted and not viewable on Android or Web after being uploaded to the instance |
Expected behavior: The uploaded PDF should be viewable from the Activity Stream. Actual behavior: The PDF cannot be viewed/opened. |
|
Mobile Android PRB1735806 |
Paging does not work inside the item section screen | Pre-requisites:
Steps:
Expected behavior: Scrolling to the bottom of the list pages a new group of items. Actual behavior: Paging does not occur. For example, scrolling to the bottom of the list simply shows the bottom of the list. |
This version also includes other minor bug fixes and performance improvements.