Riva On-Premise 2.4.51 (2018.11.23) Release Notes

  • Updated

These release notes provide a quick overview of what is new in the following release:

Release version:
Release date: 2018.11.23
Update procedure: How to update Riva
Manual update procedure: How to update Riva from a ZIP file


Try our free 15-day trial of Riva On-Premise.


What's New in This Release

Learn more about the latest features, user experience improvements, and fixed defects for Riva On-Premise.

For more information, follow the links from these release notes or contact the Riva Success Team.

CRM-Specific Updates


  • New! Link directly to Salesforce Lightning in the ConnectBar:
    • Background: A Riva-generated summary email (of an opportunity, for example) has a Riva ConnectBar that provides direct links to the item in the CRM.
    • What is new: The links can now be easily configured to point directly to "Salesforce Lightning", "Custom", or "Default".
    • Location: The links are configured on the Salesforce connection's Options page, in the URL Type field.


  • New! Ability to sync a contact list to an opportunity:
    • Works for REST- and SOAP-based connections.
    • The contact list can be synced to an opportunity as secondary contacts so that the secondary contacts can carry on the activity if the first user needs to move on to another activity.
    • This requires configuring an advanced option for the connection.

Email-Specific Updates

Office 365 and Exchange

  • Enhanced abilities to rename the primary categories:
    • Now, it is possible to rename primary categories when syncing a separate address book. (In versions 2.4.48 through 2.4.50, the renaming was supported only when syncing the default address book.)
    • Now, when previously synced items are modified, the new primary categories are automatically assigned to them. (In versions 2.4.48 through 2.4.50, new primary categories were not automatically assigned to any previously synced items.)
    • For more information, see Set primary categories.
  • New! Troubleshooting test for the "Aborting first sync" error:
    • Background: In Riva 2.4.43 or higher, a user's sync may stop with the following message: "Aborting first sync. This mailbox appears to have already been synced by Riva".
    • Now, a new test, Sync Configuration, is available to help troubleshoot the error.
      In the Riva Manager application, in the Connection Edit windows, on the Connection Test page, selecting the Show Advanced Tests check box displays the Sync Configuration tab, where the new test can be run.
    • Note: The advanced tests on other tabs are used for diagnostics and testing by the Riva advanced configurations teams (the Success Team and the Client Engagement Team). We do not recommend using the other advanced tests.


  • Enhanced ability to rename the primary Google labels:
    When previously synced items are modified, the new primary labels are automatically assigned to them. (In versions 2.4.48 through 2.4.50, new primary labels were not automatically assigned to any previously synced items.)
    For more information, see Set primary labels.

New Sync Features

  • New! Configurable automated onboarding process for new syncing users:
    An onboarding sequence of sync policies can be used to initialize new syncing users before integrating them into the business-as-usual sync policy for the other users.
    For more information, see the Onboarding process for new Riva syncing users.
  • New! Ability to identify in the CRM which email-system attendee privatized a meeting:
    For information, contact the Riva Success Team.

Sync Configuration Enhancements

  • New! Ability to use shared or unshared transactions when duplicating a policy:
    Riva admins can now set a duplicate policy to have the same transaction folder as the original policy or have its own transaction folder.
    To access the ability: In the Riva Manager application, in the new UI, right-click a policy, and select Duplicate.
    For more information, see Understand how transaction records are maintained.
  • New! The Configure Delete Safety Settings window:
    Background: What is Delete Safety?
    To access the window:
    1. Edit a policy.
    2. Select the Advanced Options tab.
    3. On the Advanced Options page, near the bottom, select Delete Safety.
  • New UI to manage user exclusivity:
    By default, the sync is prevented from syncing any user in more than one policy.
    Now, it is possible in the UI to permit syncing the same users in more than one policy.
    To do so: In the Riva Manager application, on the Tools menu, select Manage User Exclusivity.

Monitoring and Troubleshooting

  • Quicker way to start the Riva Service Monitor:
    In the Riva Manager application, the menu bar now displays Service Monitor as a menu item.
  • Improved connection test results viewer:
    If an advanced test needs to be run on a connection, one click is enough for a Riva team member to access the viewer.
    In the test results viewer, it is possible to cycle through keyword or character searches.
    Note: For security purposes, the test results are not saved to any temporary folder or browser cache. They can be saved, to a secure folder, for example, the Riva\logs folder.
  • New troubleshooting test for Office 365 and Exchange:
    See Enhanced troubleshooting for the "Aborting first sync" error.

Scheduled Policy Maintenance Jobs

  • New! Ability to schedule maintenance jobs at the sync policy level:
    Example: Scheduling a Clean Metadata re-initialization task to take place during blackout hours, when no user is synced and the administrator does not need to be around to start the task.
    To create, add, or remove scheduled policy maintenance jobs:
    • In the Edit CRM Synchronization Policy window's Advanced Options page, select Maintenance.

Fixed Defects

The most notable fixed defect is the following:

  • IBM Notes all-day events were not synced properly to Sage CRM in hybrid mode:
    The dates were not displayed in the Sage events for all the users and the event was not displayed on the Sage calendar.
    Now, the dates and events are displayed as expected.
    Note: For a description of limitations when syncing IBM Notes events to CRM, see Appointment durations.



Was this article helpful?




Article is closed for comments.