These release notes provide a quick overview of what is new in the following release:
Release version: | 3.6.64.25681 |
Release date: | 2021.Jan.15 |
Update procedure: | How to update Riva |
Manual update procedure: | How to update Riva from a ZIP file |
Free trial: | With just a few short questions, you can get hands-on. |
What's New in This Release
- Salesforce: enhanced reporting of Riva's API usage.
- Exchange: Riva now supports OAuth connections that have no client secret (and no certificate).
- Microsoft Dynamics CRM: OAuth connections now support the Global Discovery Service.
- Fixed defect.
Salesforce: enhanced reporting of Riva's API usage
Now, in Riva, you can configure the Salesforce API Usage Last 7 Days report to display the number of API calls per user per ClientID. The data is rolled up into per-app calls and per-policy calls.
To configure the enhanced reporting on Riva's API usage, contact the Riva Success Team.
Exchange: Riva now supports OAuth connections that have no client secret (and no certificate)
Background: In the Azure OAuth flow, the client secret may or may not be required, depending on the use case.
For Riva On-Premise deployments that are using an OAuth app without a client secret, you can
- create an Office 365 OAuth connection without a client secret (and without a certificate); and
- edit an Office 365 OAuth connection to remove its client secret.
Microsoft Dynamics CRM: OAuth connections now support the Global Discovery Service
When creating a connection:
- In the Microsoft Dynamics CRM Wizard, when Dynamics 365 OAuth Client Secret is selected, the default Address below Microsoft CRM Online for Office 365 / Live ID Address is Microsoft Dynamics CRM - Global Discovery.
- Notes:
- If Microsoft Dynamics CRM - Global Discovery is selected, the Resource text box is cleared.
- The Global Discovery Service is not available for connections based on user credentials (user name and password).
Fixed defect
Fix resulting in a small performance gain:
- Defect: Some hidden files used by Riva in syncing mailboxes were saved every hour, whether there had been changes or not, which caused excess entries in the sync logs.
- Fix: Now, the files are saved only if there have been changes, to a maximum of once every 24 hours.