Release Notes - 2016.04

Article ID: 1552
Last updated: 09 Sep, 2016

Riva Cloud. Release date: 2016.04 (April). Riva core version: 2.4.41.

Benefits of This Release

Improved Performance

Riva Cloud 2016.04 includes several performance improvements, for example:

  • Optimized Salesforce queries.
  • Earlier exclusion of unchanged items from the sync cycle.

Compatibility with Sugar 7.7

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

Even More Finely Tuned Sync for Some Platforms

Microsoft Dynamics CRM

  • Appointments organized by non-CRM users who become CRM users:
    Riva Cloud can be configured so that when it finds an appointment whose organizer is not a CRM user, it 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.
    To implement this enhancement, contact the Riva Success Team.
  • Prevent Organization.svc timeouts:
    Such timeouts look like this: "Server Timeout Error. Inner Fault: The HTTP request to 'https://xxxxxxxxxxxx/XRMServices/2011/Organization.svc' has exceeded the allotted timeout of nn:nn:nn. The time allotted to this operation may have been a portion of a longer timeout." To prevent Organization.svc timeouts, contact the Riva Success Team.

NetSuite

  • Appointments organized by non-CRM users who become CRM users:
    Riva Cloud can be configured so that when it finds an appointment whose organizer is not a CRM user, it 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.
    To implement this enhancement, contact the Riva Success Team.

Oracle CRM On Demand

  • Appointments organized by non-CRM users who become CRM users:
    Riva Cloud can be configured so that when it finds an appointment whose organizer is not a CRM user, it 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.
    To implement this enhancement, contact the Riva Success Team.

SAP Cloud for Customer

  • Sync SAP C4C visits to Exchange:
    When this feature is enabled, the visits are categorized, on the Exchange calendar, with the default category name: SAP C4C.
    To sync SAP C4C visits to Exchange, contact the Riva Success Team.

  • Sync deleted Exchange appointments as cancelled in SAP C4C:
    By default, Riva syncs deleted Exchange appointments as deletions in SAP C4C, but Riva can be configured to sync them as cancelled in SAP C4C.
    To sync deleted Exchange appointments as cancelled in SAP C4C, contact the Riva Success Team.

Enhancements to Riva sync policies

Enhancement applicable to any sync policy:

  • User re-initialization options can now be applied to emails.
    If you need to re-initialize users for the email module, contact the Riva Success Team.

Enhancement for Riva sync policies for Exchange:

  • Clutter prevention in the Deleted Items folder in Outlook:
    When Riva deletes items from folders it created for opportunities, cases, etc., it now deletes them permanently (what is called hard deleting) instead of moving them to the Deleted Items folder (what is called soft deleting). The reason for hard deletes is that there is no need to retain such deleted items, because Riva can always resync or reproduce them.
    If you want to revert to soft deletes, contact the Riva Success Team.



Article ID: 1552
Last updated: 09 Sep, 2016
Revision: 3
Views: 3707
Prev     Next
Riva Cloud 2017.1 Release Notes       Release Notes - 2015.11


Back to Top