Release Notes - 2015.11

  • Updated

Riva Cloud. Release date: 2015.11 (November).

What is new:

Microsoft Dynamics CRM 2015, 2013, or 2100 Rollup 10 or higher

  • For users who have SmartConvert enabled with the following option: “If the recipient is not matched, create lead instead of contact.”
    When Riva syncs an email from Exchange to CRM and SmartConvert creates a new lead for a non-matched recipient, the CRM lead topic is formatted as follows:
    “[company name], [lead's first name], [lead's last name], Created by Riva”.
    Example: Riva uses an email sent to to create a lead in the CRM with the topic ", Ian, Sample, Created by Riva".


  • Request-level authentication.
    The user's credentials are sent along with every request, which eliminates the need for session management and separate logins.
    If you want a login to be required to authenticate to NetSuite, contact the Riva Success Team.

  • Contact sync filters are subsidiary-aware by default.
    By default, when Riva syncs contact from NetSuite to the email system, Riva limits the scope of the All Visible and By Owner filters to the defined subsidiary.
    If you want to disable this default behaviour, contact the Riva Success Team.

Sage CRM

  • By default, Riva detects when opportunities are closed and removes the corresponding AssignTo drop folders.
    The definition of which statuses constitute a closed opportunity can be changed.
    Example: An organization can define the closed status to be Won (default) or Completed (which is equal to "Win") or Lost (default) or Aborted (which is equal to "Lost").
    To set custom statuses to indicate a closed opportunity, contact the Riva Success Team.


  • Riva records the "Date Received" or "Date Sent" in converted emails.
    When Riva syncs an email to Salesforce, the description now includes either "Date Sent:" or "Date Received:", and it reflects the user's local time.
    Example: Date Received: 2015-02-03 13:26:12 -07:00.

  • Force Riva to set the owner of the email to be the sender of the email if the sender is a user.
    By default, the owner is set to be the current sync user.
    In some deployments, it makes sense to set the owner to the sender of the email. For example, in an Auto-Inbox, Auto-SentItem deployment with duplicate removal based on ExternalID, everyone who gets a copy of an email is the potential syncer of the email. In these cases, the owner ends up being random, based on who syncs the email first.
    If you want to force Riva to set the owner of the email to be the sender of the email if the sender is a user, contact the Riva Success Team.

Universal Change Detection (UCD)

  • UCD is used to prioritize user sync polls based on user updates to CRM data. UCD triggers immediate user sync polls for users who have created, deleted, or updated an item in the CRM. To use UCD, contact the Riva Success Team.

Was this article helpful?




Article is closed for comments.