Mobile Agent - Intune for Android v18.0.0
Summarize
Summary of Mobile Agent - Intune for Android v18.0.0
The Android v18.0.0 release of the ServiceNow Mobile Agent app addresses various issues and enhances the overall performance of the application. Users can download the latest version from the Google Play store and test the app using a demo account upon installation.
Show less
Key Features
- Bug Fixes: Several critical bugs have been resolved, including app crashes, barcode scanning issues, and navigation problems.
- Improved Usability: Enhancements to the user interface and experience, including better handling of input fields and clearer navigation.
- Performance Enhancements: General performance improvements have been implemented to ensure a smoother user experience.
Key Outcomes
With this release, users can expect a more stable application that reduces crashes and improves functionality, such as:
- Successful opening of records without the app crashing.
- Accurate processing of multiple barcode scans.
- Correct navigation behavior using the Android Back button.
- Consistent display of values across iOS and Android platforms.
Overall, this update enhances the mobile experience for ServiceNow users by addressing known issues and ensuring a more reliable and efficient application.
The Android v18.0.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 PRB1751431 |
The Agent Mobile App crashes when opening an applet | The Agent Mobile App crashes when opening an applet using a button in a card template referring to Next Experience CSS variables if Next Experience UI is disabled |
Expected behavior: The record should be opened successfully in the Agent Mobile App. Actual behavior: The record is opened but the Agent Mobile App crashes. |
|
Mobile Android PRB1754838 |
Multiple barcode scans get appended instead of being processed separately using an external barcode scanner connected through Bluetooth |
Expected behavior: Multiple barcode scans should be processed separately. After one barcode is scanned, the app should automatically move to scan for the next value instead of appending the next value to the first scan. Actual behavior: Multiple barcode scans get appended instead of being processed separately. This occurs for multiscan and groupscan. |
|
|
Mobile Android PRB1771121 |
The user is unable to copy some fields on the details screen | ||
|
Mobile Android PRB1759490 |
The Activity Stream crashes if any comment contains HTML with an IMG tag that doesn't have a source link | A malformed image tag passes a null URL parameter to the code, which is not expecting a null. This results in a crash. |
Observe that the app crashes and closes. |
|
Mobile Android PRB1735791 |
The Back button on an Android device sends the user to the main list rather than the previous screen | The behavior is different when using the Back button of the Now Mobile App and the Back button of the Android phone. If the user selects the back arrow on the upper left corner of the screen, they navigate back to the list of articles as expected. However, if they select the Android Back button, they are sent back to the main screen. |
Expected behavior: The user should be navigated one step behind the current step. Actual behavior: It goes back to the screen. |
|
Mobile Android PRB1749164 |
The Cost field on the Log Incidental Input form screen shows discrepancies in certain values between iOS and Android | This discrepancy only occurs during the creation process of logging an incidental. Once the user submits, the same value is displayed on both iOS and Android clients. |
In iOS, the user observes the value 3.4 in the Cost field. In Android, the user observes the value 3.4000000000000004. |
|
Mobile Android PRB1751891 |
Selecting the Accept footer button multiple times causes a server error | When the user selects the Accept or Mark as complete button, there is no indication to the user that the action was submitted. If the user selects one of these buttons again, an 'Insufficient privileges' error displays because the button was already selected. |
Observe the 'Insufficient privileges' error. |
|
Mobile Android PRB1744211 |
A comma character is not accepted in a Number input field in an Agent Mobile instance with the language set to German | In German, a comma is used instead of a period as a decimal separator. However, a comma character is not accepted in a Number field. |
Observe that a comma is not allowed in the field. |
|
Mobile Android PRB1761248 |
Offline related lists don't display multiple pages | Only the first 20 records in a related list are shown because multiple pages can't be loaded in offline mode. |
Expected behavior: The user can scroll to view all records. Actual behavior: Only the first 20 records are returned and no additional pages are loaded. |
|
Mobile Android PRB1703985 |
An indoor map crashes when there is no location to display or no floor selected | When the user tries to load a map by selecting the Next button, the app quits and loads again, taking the user to the home screen. |
Expected behavior: Notice an empty state screen showing, 'Nothing matched your search/Try adjusting your search criteria'. Actual behavior: The app crashes (but only the Parameter Activity. The Tabs Activity may still run in the background). |
|
Mobile Android PRB1756967 |
Delays in deactivating the Submit / Next page buttons on an input form screen with mandatory barcode input | If an input form is configured with a mandatory barcode input and the input is filled and then removed, there is a moment that the Submit (or Next page) button is still enabled. Users can proceed with form submission (or proceed to the next page), resulting in a skipped mandatory field in form submission. |
Expected behavior: The Submit (or Next page) button should be activated/deactivated immediately with a reflection of the changes in the barcode input field. Actual behavior: There is a delay in activating/deactivating the Submit (or Next page) button. It allows user to submit (or proceed to the next page) by skipping the mandatory field. |
|
Mobile Android PRB1768949 |
The WebRTC API doesn't work on Android |
Observe the banner, 'Please allow your browser to access your microphone and camera.' |
|
|
Mobile Android PRB1726816 |
Text color is hard to read | The light text color is too low contrast to read against the white background. |
Notice that the text is too low contrast to read. |
|
Mobile Android PRB1748251 |
The 'Uploading' dialog is not dismissed |
Observe that the number of 'Uploading files' is incorrect. |
|
|
Mobile Android PRB1735812 |
Selecting the Back button brings to the user to the wrong screen. | The Back button navigates the user to the Home tab and shows a different launcher tab. |
Expected behavior: The Back button navigates to the 'Support' or another launcher tab screen. Actual behavior: The Back button navigates to the Home tab and shows a different launcher tab. |
This version also includes other minor bug fixes and performance improvements.