Riva CRM Integration - Documentation and Knowledge Base

Riva On-Premise 2.4.48 Release Notes

Article ID: 1700
Last updated: 15 Jul, 2019

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

Release version: 2.4.48.50620
Release date: 2018.07.27
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, performance enhancements, and bug fixes for Riva On-Premise.

CRM-Specific Updates

Email-Specific Updates

Exchange

  • Central location to rename the primary Exchange categories:
    Enhancement. The primary Exchange categories are used by Riva to identify items that need to be synced to the CRM and items that have been synced from the CRM.
    Now, in one new window, it is possible to rename any or all of the applicable primary categories.
    For more information, see Set primary categories.
  • Improved protection against unintended deletions:
    Enhancement. If an Exchange appointment cannot be updated to the CRM for an attendee sync user due to a lack of CRM permissions, that appointment is now disqualified from being deleted from Exchange on subsequent sync cycles.
    After the permissions are restored, it is possible to re-initialize the affected users with the Delete Disqualify Resync re-init option to reprocess the appointment and update it in the CRM.

Google

  • Central location to rename primary labels:
    Enhancement. The primary G Suite labels are used by Riva to identify items that need to be synced to the CRM and items that have been synced from the CRM.
    Now, in one new window, it is possible to rename any or all of the applicable primary labels.
    For more information, see Set primary labels.

Support for AWS Key Management Service (KMS) Cryptography

  • In addition to the ability to manage encryption keys on individual machines, a new feature allows private encryption keys to be stored with the AWS Key Management Service (KMS). Using KMS allows many Riva servers to share the same set of private encryption keys from a central location.
    For more information, see Default connection credential encryption and Per-connection override encryption.

Sync Configuration Improvements

  • Enhanced Delete Safety error message:
    To make it easier to determine whether the items should be deleted or not, the Delete Safety error message can now be configured to log the ID numbers of the items that were marked for deletion.
    The number of logged items slated for deletion is also configurable. For more information, see Adjust the number of logged items.
  • Improvement for the change management Configuration Mode:
    Configuration Mode change entries are stored only in memory.
    As a result, exiting from the Riva Manager application has the same effect as stopping the current Configuration Mode.

New Troubleshooting Report

  • A new feature makes it easier for end-users to see processing errors within a sync cycle.
    For more information, see Item Issues Summary report.

Improved Scalability

  • Global Sync Configuration Service enhancement:
    It is now possible to clear the existing Consumer Key registration of a node to allow another Riva instance to become that node.

Article ID: 1700
Last updated: 15 Jul, 2019
Revision: 31
Views: 3412