ServiceNow Onboarding - Intune for Android v11.5.0
Summarize
Summary of ServiceNow Onboarding - Intune for Android v11.5.0
The Android v11.5.0 release of the ServiceNow Mobile app introduces several fixes and enhancements aimed at improving user experience and functionality. The update is available for download from the Google Play store, and users can also explore the app through a demo account.
Show less
Key Features
- Accessibility Improvements: Fixes related to Talkback functionality to ensure users can better identify controls and headings within the app.
- Error Resolutions: Multiple bugs fixed, including issues with adding favorites, performance instability, and attachment handling in incidents created via Virtual Agent.
- Offline Mode Enhancements: Addressed issues in offline mode where certain UI parameters would not return data as expected.
- Visual Improvements: Color contrast issues were corrected to enhance accessibility compliance.
- Search Functionality Fixes: Resolved issues with the SearchList UI where no results were not displayed correctly.
Key Outcomes
With this release, ServiceNow customers can expect:
- Improved accessibility features, enhancing usability for all users, especially those relying on assistive technologies.
- A more stable application with reduced crashes and improved performance during ticket creation and navigation.
- Better functionality in offline mode, allowing for seamless data entry and synchronization when online.
- Corrected visual aspects for better compliance with accessibility standards, ensuring all users can interact effectively with the app.
The Android v11.5.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) PRB1461022 |
Talkback does not announce a role for the 'My incidents' control | Users are unable to identify the purpose of the control. This issue can be replicated for all the controls present throughout the application on an Android device. |
Observe whether Talkback announces role for 'My incidents' control. |
Mobile Android (non-classic) PRB1462783 |
Service Portal in the Now Mobile Android app has a Favorite/Ribbon icon that does not work as expected | It displays the error 'Error adding screen to favorites'. | |
Mobile Android (non-classic) PRB1472982 |
The app has performance instability due to exceeding the parcelable 1MB buffer when creating a ParamsActivity | ParamsActivity cannot start because the size of the extras in the intent is too large. |
Expected behavior: The user should be able to create a ticket. Actual behavior: The application crashes. |
Mobile Android (non-classic) PRB1472364 |
Talkback does not announce 'EUSE Mobile' as a heading | Android Agent doesn't announce the page header as a header. The issue does not exist in the iOS client, only the Android client. |
Expected behavior: Talkback should announce 'Hello, [Name]. Header'. Actual behavior: Talkback announces 'Hello, [Name]'. |
Mobile Android (non-classic) PRB1463087 |
Talkback does not announce the confirmation message after activating the Clear control | Users will not get the information about the action performed by activating the Clear button. |
Expected behavior: Talkback should announce something like 'Cleared Successfully'. Actual behavior: The entries you made will clear, and the Clear button will become inactive. Talkback does not read out a status message. |
Mobile Android (non-classic) PRB1422908 |
Choice lists do not work in offline mode | When the offline mode plugin is enabled, and applets and their functions have been deemed to be available offline, any UI parameters in the functions that reference other fields do not return any data. |
'Category' and 'Subcategory' are not updating properly and their values match the choice field on the platform incident table for the edited record. After changing the inputs offline, they are synced properly when going back online. |
Mobile Android (non-classic) PRB1458769 |
The Appsee Open Applet event can have a null title | Appsee requires a title for the Open Applet event. In some cases, there isn't a title to send. |
Observe that the applet name is missing for 'My approval', and only for the data coming from an Android device. |
Mobile Android (non-classic) PRB1452827 |
In Virtual Agent in the Mobile app, attachments are not added to incidents created from the chat | They are, however, being added to the sys_cs_ conversation_task table. |
Expected behavior: Navigate to platform and validate the attachment is added to the newly created incident. Actual behavior: The attachment is in the sys_conversation_task table, but not in the incident table. |
Mobile Android (non-classic) PRB1451988 |
Color contrast issues on the clear cache/offline mode pages |
Color contrast issues are seen on several pages, like offline mode/clear cache. Notice that clear cache/offline mode does not have sufficient color contrast of 3:1, since they are large text. |
|
Mobile Android (non-classic) PRB1447554 |
'Provide Virtual Agent Feedback' loops when trying to enter extra information | This issue is observed while using Now Mobile on an Android device. When the 'Provide Virtual Agent Feedback' agent topic is present to a user, if the user selects Bad and tries to enter a reason, the topic loops and they are asked for a reason again. This issue does not happen in a browser or on iOS. There are no errors, just a message that Virtual Agent does not understand the entered text. |
Expected behavior: The topic should accept the text and close the chat. Actual behavior: The topic loops. |
Mobile Android (non-classic) PRB1473743 |
The SearchList UI parameter does not update the screen when no results are found | When searching a SearchList, if the search returns no result, the screen does not refresh appropriately on an Android and the 'Total Found' count still displays. |
On iOS, you see 'No results found', which is correct. On Android, you see nothing on the main screen, and under the search dialog the 'Total Found: xxx' text is still there showing the total record count, which is incorrect. |
This version also includes other minor bug fixes and performance improvements.