Introduction

This document describes the changes introduced in Zivver Office Plugin release 5.0.1

Release highlights

Version 5.0.1 is a major release which contains a breaking change, namely ending support for Outlook 2010. Zivver follows the product life cycle of Microsoft, which no longer supports Outlook 2010 since October 13, 2020.

Alongside this breaking change there are some important bug fixes that solve issues when printing Zivver messages containing tables, as well as issues when sending attachments from other programs.

New or improved functionality

• updated urls from zivver.eu to zivver.com.
• updated the plugin version number to be more granular when going to about Zivver.
• updated the minimum supported Outlook to the 2013 version in the system requirements.
• updated TLS to 1.3
• improved error messages when entering a wrong password

Removed functionality

• removed support for Outlook 2010.

Bug fixes

• fixed multiple issues with sending attachments from 3rd party programs.
• fixed the issue where tables were not displayed correctly when printing or exporting to pdf.
• fixed the issue where the lock icon was not shown at Zivver messages in the sent items folder.
• fixed the issue where Zivver messages were not loaded.
• fixed the issue where the close icon for the conversion details screen was not actionable.
• fixed the issue where email and full name of the original account were not displayed correctly under delegates’ accounts.
• fixed a typo in the settings menu.
• fixed the issue where sent Zivver messages were not stored in the sent items folder
• fixed the issue where Zivver was not automatically turned on when a business rule had been triggered that should have enforced Zivver use.
• hot-fixed two issues discovered during regression where BCC participants were not clickable from Sent Items and nothing was happening when clicking on message info.

Known issues

Adding attachments to an unencrypted copy of a sent/received message is done in the background.
If a message is archived before this process is finished, not all attachments might have been added to the unencrypted copy.
The workaround for this is to manually store an unencrypted copy. You can do this from within the Zivver conversation itself in Outlook.
This video (nl) explains how to do this: