Mobile Classic Android v2.1
Summarize
Summary of Mobile Classic Android v2.1
The Mobile Classic Android v2.1 release focuses on resolving key issues to improve user experience and stability. It is a maintenance update addressing several problems reported in the Android app related to Knowledge Management, incident email previews, reference fields, user record display, app crashes, and push notification actions.
Show less
ServiceNow customers are encouraged to download this update via the Google Play store to benefit from these fixes. Additionally, ServiceNow highlights several new mobile applications—Mobile Agent, Now Mobile, Mobile Onboarding, and Now Support—that offer enhanced features and capabilities beyond Mobile Classic.
Key Fixes and Improvements
- PDF Attachment Access in Knowledge Management: Fixed an issue where users could not open attached PDF files within knowledge articles on the Android app, while iOS and Android Mobile UI apps functioned properly.
- Email Preview in Incidents: Resolved the problem where tapping email preview cells in incident correspondence did not open email content on Android, ensuring parity with iPhone behavior.
- Reference Field 'Clear' Button: Added functionality to clear reference fields on forms, aligning Android app behavior with the iPhone app by introducing a 'Clear' button.
- User Record Display on Tablets: Corrected user record loading on Android tablets to open the user profile view instead of a generic record detail.
- App Stability and Crash Fixes: Addressed various random crash scenarios including issues with Connect chat input, loading large lists, quick navigation, and user avatar loading when user names are blank.
- Push Notification Interaction: Enhanced native Android app support for "Accept/Decline" buttons within push notifications for improved user engagement.
Benefits for ServiceNow Customers
By applying this update, customers using the Mobile Classic Android app will experience improved reliability and a smoother user interface. The fixes ensure important functionalities like accessing PDF attachments, viewing incident emails, and managing reference fields work as expected. Enhanced crash resilience reduces disruptions, contributing to a more stable mobile experience.
Customers should also evaluate the newer ServiceNow mobile apps mentioned to access the latest features and capabilities tailored for modern mobile workflows.
The Mobile Classic Android v2.1 release provides problem fixes.
Download the latest Mobile Classic version
To download the latest release, visit the Google Play store.
Fixed in this release
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
Mobile PRB718570 |
Users cannot open attached PDF files from Knowledge Management using the Android app | In an OOB Helsinki instance:
Notice that the that clicking on the link does not download the PDF attachment or open the knowledge article. If you repeat the above steps with the iOS app or Mobile UI on Android, you are able to access the article. |
|
Mobile PRB721868 |
In the Android app, tapping the email preview cell in an incident does not open up the email contents | This issue is not present for iPhone users. |
Expected behavior: This should open up a new page that displays the email contents. Actual behavior: Nothing visual occurs. |
Mobile PRB723229 |
On the Android app, reference fields on forms do not have a 'Clear' button like they do on the iPhone app | Without this 'Clear' button, there is no way to clear out reference fields. |
Note that there appears to be no way to clear out the field once it is no longer empty. Expected behavior: There should be a 'clear' button like there is on the iPhone app. Actual behavior: There is no 'clear' button. |
Mobile PRB734628 |
Loading a user record on an Android tablet should open the user profile | Loading a user record on an Android tablet should open a profile view of that user, but clicking on a user record opens a record detail for the user on the native Android app. | |
Mobile PRB734635 |
Fix Android application crashes reported via crash reporting tool | Various conditions can cause the Android application to crash. | The following example conditions do not always produce a crash, but these are the conditions where the crash may occur randomly:
|
Mobile PRB736838 |
Native mobile apps should support "Accept / Decline" push notification buttons |