These release notes provide a quick overview of what is new in the following release:
Release version: | 3.0.59.17593 |
Release date: | 2020.May.5 |
Update procedure: | How to update Riva |
Manual update procedure: | How to update Riva from a ZIP file |
What's New in This Release
Architectural Changes
Most of the improvements made in Riva On-Premise 3.0.59 are architectural changes that will be used in future releases to support new features.
Fixed Defects
The most notable fixed defects are the following:
Inconsistent use of categories when an item was skipped because there was no matching contact in the CRM:
- Background:
- When a mail item is synced to CRM, the sync process attempts to match at least the sender or a recipient to a CRM contact. If no matching CRM contact is found for the sender or any of the recipients, one of two things occurs:
- If the sync policy is configured to create a CRM contact or lead in such a case, a contact or lead is created.
- If the sync policy is configured to create nothing in such a case, the mail item is not synced to CRM. By default, the mail item is assigned the category Skipped item - No matching Contact.
- When a mail item is synced to CRM, the sync process attempts to match at least the sender or a recipient to a CRM contact. If no matching CRM contact is found for the sender or any of the recipients, one of two things occurs:
- The defect and its fix:
- When tracking an email with the Riva Insight Track in CRM, if no matching CRM contact was found, the wrong category was assigned: Error: Skipped Item - No matching Contact.
- Now, by default, the correct category is assigned: Skipped item - No matching Contact.
Issue when syncing SmartCloudVerse to SAP C4C:
- The issue: When the Description of an appointment created in SmartCloud Verse was updated, the update was not synced to SAP C4C. Other appointment updates in SmartCloud Verse were correctly synced to SAP C4C.
- The fix: Now all updates to appointments created in SmartCloud are synced to SAP C4C.