Mobile Agent - Intune for Android v17.3.0
Summarize
Summary of Mobile Agent - Intune for Android v17.3.0
The Android v17.3.0 release of the Mobile Agent app provides essential fixes and improvements to enhance user experience. Customers can download this latest version from the Google Play Store and try a demo using a demo account available at the initial post-download or instance list screens.
Show less
Key Features
- Bug Fixes: The update addresses several key issues, including:
- Attachment viewing errors, where users previously encountered a 'Can't open file' message.
- Problems with banner push notifications leading to infinite loading screens.
- Inconsistencies in currency field displays between Android and iOS.
- Issues with mandatory fields not functioning correctly when deselected.
- Barcode scanning requiring manual focus shifts after scanning.
- Corrupted attachments after uploads that were not viewable.
- Paging issues in the item section screen not functioning as expected.
Key Outcomes
By upgrading to v17.3.0, ServiceNow customers can expect improved functionality, including:
- Smoother interactions with attachments and notifications.
- Enhanced consistency in user experience across platforms.
- Overall performance improvements and minor bug fixes.
This release aims to provide a more seamless and efficient use of the Mobile Agent app for Android users, ensuring better service delivery and customer satisfaction.
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.