What’s new in Zetadocs Expenses January 2020 update
Improve startup time for desktop app
This article describes the new features and other improvements in the January 2020 release of the Zetadocs Expenses service.
Zetadocs Expenses
|
Release date and version
|
Service
|
January 20, 2020 (version 3.4.20007)
|
Apple (iOS) app
|
January 20, 2020 (version 3.4.20007)
|
Android app
|
January 20, 2020 (version 3.4.20007)
|
Extension for Business Central
|
December 13, 2019 (version 1.2.5)
Availability on Microsoft AppSource typically seven working days after release date.
Not updated in this release
|
Connector for NAV
|
December 13, 2019 (version 3.4.19336)
Not updated in this release
|
Reporting Template
|
April 5, 2019 (version 1.0)
Not updated in this release
|
Changes in this update
Feature enhancements
Improve startup time for desktop app
We have improved the startup time for the desktop client app for users who have a large number of expenses. The desktop client now behaves like the mobile app, and saves a copy of your expense data when you close the browser so that it only needs to download any changes next time you run it.
This reduces the startup time significantly, improving usability for finance teams and other heavy users who close their desktop browser between operations.
Quality and performance improvements
This update includes a number of quality and performance improvements, including the following:
Unable to use vehicle type after settings are changed
Previously after editing a vehicle type which was restricted to specified users or user groups, in some circumstances the vehicle type would no longer be visible to some of the permitted users. This prevented affected users from creating mileage records for that vehicle type. The issue has now been corrected.
Unable to attach expense to report
Previously there was an infrequent issue where a draft expense which has been removed from a report could be left with a status of Submitted rather than Draft. This prevented the expense from being attached to a new report. The issue has now been corrected.
Additional upgrade steps
Extension for Business Central
Customers using the extension with a Business Central public cloud system can update this from Microsoft AppSource. Updates are typically available on AppSource within seven working days of release, and you can check whether it is available for your system by comparing the AppSource version number with the version number listed above.
Customers using the extension with a Business Central on-premises system can download the extension from the Equisys software updates page.
To upgrade from an older version of the extension please contact your Business Central reseller, or contact Equisys for further assistance if required.
This release is compatible with previous versions of the Extension for Business Central.
Connector for NAV
Customers using the Connector for NAV with a Business Central or NAV on-premises system can download the connector from the Equisys software updates page.
To upgrade from an older version of the connector, follow the instructions in this technote. Please contact Equisys for further assistance if required.
This release is compatible with previous versions of the connector (versions 3.3.18178 and later).
Versions of the connector before the June 2019 release (versions before 3.3.19148) are not compatible with Business Central on-premises systems using the April 2019 release of Business Central (BC14), or with older Business Central systems with cumulative update 4 (BC13 CU4).
Reporting Template
There is no update to the PowerBI reporting template with this release.
Mobile apps
Installed mobile apps will be updated automatically on mobile devices where this is enabled.
Known issues with released features
Map does not display correctly on Apple iOS devices
There is an issue with displaying maps when using the Zetadocs Expenses mobile app on some Apple iOS devices. This affects how the route is displayed in the mileage expense view and edit screens, causing it to be displayed on a solid grey background instead of overlaying it onto a map.
Moving or resizing the map corrects the issue, and the map will then be displayed correctly. The issue does not occur when using the mobile app on Android devices or in the desktop browser app.