Riva On-Premise 2.4.41 (2016.04.18) - Release Notes

Article ID: 1416
Last updated: 18 Jan, 2017

Release version: 2.4.41.29563
Release date: 2016.04.18
Latest hotfix: 2.4.41.34202 (2017.01.06)
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

Note: The latest update to these release notes since Sept. 7, 2016, is found under Salesforce.

Improved Performance

Riva 2.4.41 includes several performance improvements, for example:

  • Reduced CPU usage.
  • Reduced disk usage.
  • Optimized Salesforce queries.
  • Earlier exclusion of unchanged items from the sync cycle.

Improved High Availability and Disaster Recovery

In version 2.4.41, Riva has improved its High Availability, High Performance, and Disaster Recovery features. To discuss your organizational High Availability, High Performance, and Disaster Recovery requirements, contact Riva Professional Services.

Increased Scalability

For large enterprise deployments, 64-bit Riva services are available upon contacting the Client Engagement Team.

Ability to Manage Multiple Sync Services from a Single Console

With remote management, a single Riva CRM Service Monitor console is all you need to remotely manage multiple sync services.

Compatibility with Sugar 7.7

  • "Unable to serialize result" errors do not occur in Riva 2.4.41.

Even More Finely Tuned Sync for Some Platforms

Salesforce

  • Master categories in email system based on Salesforce user profiles
    Riva 2.4.41.33120 or higher can assign master categories to email users based on the user profiles in Salesforce. The master categories are updated every 24 hours. To deploy this functionality, contact the Client Engagement Team by logging a support request. Fees apply.
  • New event syncing option
    Riva 2.4.41.33125 or higher can be configured to sync an Exchange meeting to a Salesforce event only if every attendee matches a contact in Salesforce.
    If any attendee has no matching contact in Salesforce,
    Riva does not sync the event to Salesforce, and
    the event is returned to the user's mailbox with a "Contact match not found" category along with the email address of the unmatched attendee.
    To deploy this functionality, contact the Client Engagement Team by logging a support request. Fees apply.
    Note: To be clear, this is how the new functionality differs from similar functionalities. Apart from the new functionality, Riva can be configured
    not to sync meetings to Salesforce;
    to sync all meetings to Salesforce and ignore attendees that do not match Salesforce contacts; or
    to sync all meetings to Salesforce and create contacts in Salesforce for attendees that have no matching contacts. At this point, a created contact is related to the matching account, but if there is no matching account, the contact is related to the collector account.

Microsoft Dynamics CRM

  • Appointments organized by non-CRM users who become CRM users:
    You can use an advanced custom option so that when Riva finds an appointment whose organizer is not a CRM user, Riva sets the syncing user (for example, Rivasync@domain.com) as the organizer; and when the organizer becomes a CRM user, Riva sets this new CRM user as the organizer of that appointment. For more information, see Handle appointments organized by non-users who become users.

NetSuite

  • Appointments organized by non-CRM users who become CRM users:
    You can use an advanced custom option so that when Riva finds an appointment whose organizer is not a CRM user, Riva sets the syncing user (for example, Rivasync@domain.com) as the organizer; and when the organizer becomes a CRM user, Riva sets this new CRM user as the organizer of that appointment. For more information, see Handle appointments organized by non-users who become users.

Oracle CRM On Demand

  • Appointments organized by non-CRM users who become CRM users:
    You can use an advanced custom option so that when Riva finds an appointment whose organizer is not a CRM user, Riva sets the syncing user (for example, Rivasync@domain.com) as the organizer; and when the organizer becomes a CRM user, Riva sets this new CRM user as the organizer of that appointment. For more information, see Handle appointments organized by non-users who become users.

SAP Cloud for Customer

Enhancements to Riva sync policies

Enhancement applicable to any sync policy:

  • User re-initialization options can now be applied to emails.
    In the Re-initialize Users window, the Modules drop-down list now includes the selectable item Emails.
    See step 5 of How to re-initialize users.
     

Enhancement for Riva sync policies for Exchange:



Article ID: 1416
Last updated: 18 Jan, 2017
Revision: 20
Views: 4045
Prev     Next
Riva On-Premise 2.4.42 (2017.02.03) - Release Notes       Riva On-Premise 2.4.40 (2015.11.27) - Release Notes


Back to Top