Introduction

This document describes the changes introduced in this release of the Zivver Office Plugin.

Downloads

To download the Zivver Office plugin, please visit our download page.

Release highlights

Improvements

We have rebuilt this version of the Zivver Office Plugin from the ground up, focusing on an improved user experience and an enhanced performance.

The most noticeable improvements and changes are listed below.

• An increased performance speed when working with Outlook in Online Mode and in Cached Mode.
• Attachments are added faster when working with Outlook in Online Mode and in Cached Mode.
• The CPU load has been reduced by approximately 80% and the amount of network traffic has been reduced.
• An updated branding and an improved design
• Support for Microsoft Purview integration.
• Outlook 2013 is no longer supported in this version of the Zivver Office Plugin.
• Various improvements for Zivver Secure eSignatures

Bug fixes

• ENG-13547 – Various improvements related to connectivity.

Known issues

• IM-220 - When using an Outlook template for Zivver messages, the font switches size from regular to large upon entering text in the template.
• IM-785 - The Zivver Office Plugin does not recognize an attachment that the user added with Simple MAPI.
  Workaround: Use the Outlook attachment button to add an attachment, or use the Zivver attachment button for large attachments.
• IM-898 - The Zivver Office Plugin’s bar does not scale up, making the text difficult to read.
• IM-933 - Outlook crashes after having created any of the registry keys below.
  In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver\OfficePlugin\Settings’ , the ‘REG_SZ’ entry was created with the name ‘RemoteLoggingLevel’ and the value ‘info’. In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver\OfficePlugin\Settings’ , the ‘REG_SZ’ entry was created with the name ‘FileLoggingLevel’ and the value ‘info’.
  Workaround: For any of the registry keys that was created, change the value ‘info’ to ‘information’.
  Workaround: Deleting any of the registry keys above will have the Zivver Office Plugin default to the value “information”
• IM-939 - When using an MSG file to send Zivver messages, any attachments that are added to the MSG file are not added to the sent Zivver message.
  Workaround: Add any attachments manually to the Zivver message.
• ENG-5515 - Sending an attachment by right-clicking and selecting the Send to Mail Recipient option does not work when Outlook has not been started already.
  Workaround: Make sure Outlook has already been started.
  Workaround: Use the Outlook attachment button to add an attachment, or use the Zivver attachment button for large attachments.
• ENG-6373 - Updating earlier versions of the Zivver Office Plugin to v6.x of the Zivver Office Plugin “for everyone” is impossible due to an error “The installer has insufficient privileges to modify this file: C:\Program Files (x86)\Zivver B.V\Zivver Office Plugin\adxloader.dll.manifest.”
  Workaround: In the registry, under ‘HKEY_CURRENT_USER\SOFTWARE\Zivver B.V.\Zivver Office Plugin’ , create the ‘REG_SZ’ entry with the name ‘InstallScope’ and the value ‘1’.
  Workaround: Uninstall and reinstall the Zivver Office Plugin.
• ENG-7271 - Zivver attachments that have been added to an existing draft message are not removed when discarding the changes to that draft message.
  Workaround: Manually remove the Zivver attachment before closing the draft.
• ENG-7848 - The formatting of HTML signatures may be incorrect for Zivver messages that are sent using Plugin Assisted Mail Submission (PAMS) and that are received by Zivver users as BCC.
• ENG-8047 - Any human error business rules can only be closed after editing the subject or the body of the message.
• ENG-8065 - When the Zivver message is already in the process of being sent, clicking on the “Change” button will not prevent the Zivver message from being sent.
  Workaround: Clicking on either the “Cancel” button or the close window button will prevent the Zivver message from being sent.
• ENG-8158 - Logging out of Zivver while writing a Zivver message and then logging back in after having clicked on the send button will result in the message being sent insecurely.
  Workaround - Do not log out of Zivver while writing a Zivver message.
• ENG-10460 - Users may intermittently become stuck on the “checking message” screen in the Zivver Office Plugin after sending a message.
• ENG-11980 - The Forward button may be unresponsive for certain messages.