Release date on Google Play Store |
January 31st, 2018 |
Release date on the Apple App Store |
January 31st, 2018 |
Enhancements
Feature | Description |
---|---|
User Interface (UI) Updates (MOBX-1796 to 1798, 1961 and 1847 to 1849) |
Our UI refresh continues. In this release, we have made several refinements which are listed below with accompanying screen captures. We hope you like them. What sort of changes are we talking about here? We are aiming for a cleaner interface with changes to context menus, date and time pickers, duration pickers, in line editing and new address and location views. UI Update: Create/Edit Activity. UI Update: Notes/Completion Notes. UI Update: Manage Times. UI Update: Attachments. For IOS11 users the share icon for attachments was too faint. We have made some alterations to counter this problem. UI Update: Online Sync, Offline and Trouble Connecting. We have made some changes to the pop-up information banners that appear from the base of the mobile app. When the mobile app goes offline, the message "Offline, functionality may be limited" will be displayed over a dark blue background. When the mobile app has trouble connecting to the server, the message "We're having trouble connecting to the server" will be displayed over an orange background. |
Add Alt Text for Chatter / Signatures / Attachments Buttons (MOBX-2063) |
Following some valuable feedback from our customers, we have added "Alt text" (or alternative text) to the three toolbar buttons at the top of the job details screen (Chatter, Signatures, and Attachments). This is to help screen readers identify important information on the mobile app. |
Issues Resolved
A couple of bugs that we are happy to have vanquished:
Reference | Description |
---|---|
MOBX-2034 |
Skedulo X "Manage Times" was using the resource's timezone rather than job's timezone. That's not right, so we have fixed that. |
MOBX-2060 |
Custom fields that were set in the web app to not show in the mobile were still being displayed. This is not the expected behavior, and it has been corrected. |
Comments
0 comments
Please sign in to leave a comment.