Mobile Onboarding for Android v15.3.0
Summarize
Summary of Mobile Onboarding for Android v15.3.0
The Android v15.3.0 release enhances the Mobile Onboarding app by addressing various performance issues and bugs. Customers can download the latest version from the Google Play store and test the app using a demo account available post-download.
Show less
Key Features
- Performance Improvements: The release fixes issues that degraded performance when navigating deep within tab stacks.
- Input Enhancements: Issues related to composite character input for Korean keyboards have been resolved.
- UI Fixes: Adjustments have been made to ensure mobile UI rules function correctly and improve visual consistency across various elements.
- Accessibility: Enhancements have been made for users with visual impairments, ensuring that controls are properly labeled.
- Bug Fixes: The update addresses various minor bugs, including attachment management and display issues in different languages.
Key Outcomes
By updating to v15.3.0, ServiceNow customers can expect improved app performance, a more user-friendly experience with better input support, and enhanced accessibility features. This version aims to provide a smoother and more efficient mobile onboarding experience, which is essential for user satisfaction and productivity.
The Android v15.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 Mobile Onboarding 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 (non-classic) PRB1622705 |
Navigating deep into a tab stack causes performance issues |
Expected behavior: The UI should still behave without an affect on performance. Actual behavior: The UI starts to drop frames and the performance degrades. |
|
Mobile Android (non-classic) PRB1621875 |
The user is unable to enter composite characters on a Korean keyboard when entering text on the input form screen | The user can only observe composite characters by posting a work note or comment in an activity stream. |
Expected behavior: Composite characters are formed. Actual behavior: Only a single character is allowed. |
Mobile Android (non-classic) PRB1612984 |
Mobile UI rule does not work as expected in Android | The field does not hide when assignment group changes for the first time but gets hidden if you try to change it a second time. | |
Mobile Android (non-classic) PRB1612041 |
Label for grouped input from bar code scanning is not showing up in Android | Refer to the listed KB article for details. |
|
Mobile Android (non-classic) PRB1609815 |
Font size decreases in the Android NOW mobile app after upgrading to 14.5.0 when the language is traditional Chinese |
Observe that the font of the opened record gets smaller. |
|
Mobile Android (non-classic) PRB1609551 |
On the ServiceNow Mobile Agent app for Android, a user can always delete attachments on a form | ||
Mobile Android (non-classic) PRB1602165 |
The Edit Case > Product options shows text in many sizes |
Expected behavior: The list of available products has the same font size. Actual behavior: The list of available products has many different font sizes. |
|
Mobile Android (non-classic) PRB1597243 |
After submitting a reservation request in Now mobile app by Android mobile, the app returns to the same page after editing | ||
Mobile Android (non-classic) PRB1596466 |
Quantity and Cost are missing in the Agent app when creating incidental expenses in WOT |
Expected behavior: The Quantity and Cost fields are visible. Actual behavior: The Quantity and Cost fields are NOT visible. |
|
Mobile Android (non-classic) PRB1596400 |
The filter buttons in 'My Approvals' are described as 'unlabelled ' | All filter buttons contain 'unlabelled' as a description. | |
Mobile Android (non-classic) PRB1572307 |
Talkback does not have focus on play button |
Actual behavior: The video play control does not inform a user they can play a video. Expected behavior: Non-vision users need to be informed that the control will play a video. |
This version also includes other minor bug fixes and performance improvements.