Riva On-Premise 2.4.42 (2017.02.03) - Release Notes

Release version:	2.4.42.34887
Release date:	2017.02.03 (Feb. 3)
Update procedure:	How to update Riva
Manual update procedure	How to update Riva from a ZIP file

The Riva On-Premise server is available for a free 15-day trial.

Benefits of This Release

• Increased scalability.
• Enhanced ability to manage multiple sync services from a single console.
• Updated technology.
• Enhanced error-prevention.
• Compatibility with Salesforce Summer '16.
• Salesforce connections are now licensed by Salesforce Organization ID.
• Support for Microsoft Dynamics 365 CRM and Microsoft Dynamics CRM 2016.
• Support for Infor CRM Windows Integrated authentication.
• More finely tuned sync for SAP C4C.

Increased Scalability

• Exchange Universal Change Detection (UCD):
  • Recommended for large Riva-Exchange deployments.
  • Recommended for most Riva-Office 365 deployments.
  • When Exchange UCD is configured in a sync policy, Riva subscribes to Exchange notifications for changes to the mailboxes being synchronized.
  • The Exchange UCD process collects the Exchange notifications to collect a list of mailboxes with outstanding changes. Riva then synchronizes those mailboxes.
  • The benefit is that Riva does not need to poll EWS for changes that occur in each mailbox every sync cycle: using Exchange UCD can significantly reduce systems resource usage and increase the scalability targets.
  • For more information, contact the Riva Success Team.

Enhanced Ability to Manage Multiple Sync Services from a Single Console

Riva 2.4.42 has added the following functionalities to remote management:

• Global Sync Configuration Service.
• Managing the execution units of sync policies.
• Global Sync Destination Registry (also known as the Global Destination Entity Registry).
• Change notification.
• Stopping the Riva sync for one user entity or group of entities.

Updated Technology

• .NET
  A minimum of .NET 4.5.0 must be installed on the Riva On-Premise server, but .NET 4.5.2 is recommended.
  Use cases:
  • A supported version of Windows Server has .NET 4.5.0 or .NET 4.5.2 installed:
    • Upgrading Riva from version 2.4.31 or higher to version 2.4.42 works without any issues.
    • To upgrade Riva from version 2.4.30 or lower to version 2.4.42, contact the Riva Success Team.
    • Installing Riva 2.4.42 for the first time on that server works without any issues.
  • A supported version of Windows Server has a previous .NET version installed:
    • Attempting to upgrade from Riva 2.4.31 or higher to Riva 2.4.42: A warning appears, saying that you must upgrade to the required or recommended version of .NET; and the upgrade to Riva 2.4.42 is cancelled.
    • To upgrade Riva from version 2.4.30 or lower to version 2.4.42: Upgrade to the required or recommended version of .NET, and contact the Riva Success Team.
    • Installing Riva 2.4.42 for the first time on that server: A warning appears, saying that you must upgrade to the required or recommended version of .NET; the upgrade completes normally; but you must upgrade to the required or recommended version of .NET before you can use Riva.
  To sync with Microsoft Dynamics 365 CRM or Dynamics 2016, .NET 4.5.2 must be installed on the Riva On-Premise server.

Enhanced Error-Prevention

• Ability to detect when transactions metadata has been misplaced:
  You can configure Riva so that if the records of previous transactions cannot be found in the expected location, the sync is stopped to prevent critical sync errors from occurring.
  An advanced option can be activated to allow you to make legitimate changes to the location of some of the transactions metadata.
  For more information, see Detect when transactions metadata has been misplaced.
   
• Salesforce state and country pick lists:
  You can configure Riva to provide a default state, province, or country if the name or code found in the email system does not match anything in the Salesforce pick lists.
  For more information, see Support for Salesforce state and country pick lists.
   
• Microsoft Dynamics CRM:
  In Riva 2.4.42, there is a solution for the error "Number of conditions in query exceeded maximum limit. [8004430C]".

Compatibility with Salesforce Summer '16

• Support for the Salesforce Summer '16 Enhanced Email feature:
  Salesforce's new feature is described at https://releasenotes.docs.salesforce.com/en-us/summer16/release-notes/rn_sales_productivity_email_enhanced.htm.
  For information on how Riva supports Salesforce's new feature, see Support for the Salesforce Summer '16 Enhanced Email feature.
   
• Support for Salesforce's updated attendee management:
  Now that Salesforce has fixed a limitation with regards to event relations, Riva no longer needs to work around the limitation. Riva can now sync location or time changes in Salesforce events more quickly, with fewer API calls.
   

Salesforce Connections Are Now Licensed by Salesforce Organization ID

• All new licenses for Salesforce are now directly linked to a Salesforce Organization ID (OrgId). Previously generated licenses are still supported. All Salesforce license renewals will transition to this new license type. For more information, see Salesforce Organization Id in Riva license.

Support for Microsoft Dynamics 365 CRM and Microsoft Dynamics CRM 2016

• Requirement: .NET 4.5.2.
  Support is effective in Riva On-Premise 2.4.42.33657 or higher.

Support for Infor CRM Windows Integrated Authentication

• In Riva 2.4.42.34083 or higher, you can select the Use Windows Integrated authentication check box when creating or editing an Infor CRM connection.

More Finely Tuned Sync for SAP Cloud for Customer

• In Riva 2.4.42.33439 or higher, you can filter SAP C4C opportunities by Account Team membership.
  To do so: On the SAP C4C Connection Edit window, on the Pre-defined Filters page, set Opportunity Visibility to Account Team.
  This means that opportunities related to a user are synced to that user if the user owns the opportunity or is a member of the Account Team.
  This setting overrides the default ownership filtering used by sync policies.