Until recently, Salesforce did not support relating an enhanced email directly to the CRM contact that corresponded to the sender.
Riva used a workaround from version 184.108.40.206908 until now. The email sender was added to the To list, which related the email to the CRM contact that corresponded to the sender.
Recently, Salesforce has made an improvement. Now, the Riva sync can and does relate the email directly to the CRM contact that corresponds to the sender. The sender is no longer added to the To list.
New! Ability to lock fields on the Object Definition page: Background: By default, fields are unlocked and can be lost when the metadata is cleared. (The metadata is cleared when configuring the sync policy to sync email as enhanced email or when the re-init option Clear metadata is used.) Benefit: Locking a field helps preserve the integrity of customizations that may depend on it. Visibility:
On the Object Definition page, a locked field is identified with a lock icon.
In the Connection Advanced Options window, a locked field appears as a key in the following format: Crm.AdditionalFields.[Module] = [value], where
[Module] is the locked field's Object Type on the Object Definition page; and
[value] is the locked field's name in the Selected Fields box on the Object Definition page.
Note: A locked field can be unlocked. To lock or unlock a field:
On the Object Definition page in the Selected Fields box, right-click the field and choose the appropriate action.
Fixed defect: The defect: When tracking an email to Salesforce as an enhanced email and configuring the sync policy to include the original Mime and include the original attachments with the Mime attachment, the email was not tracked in Salesforce as a Mime attachment. Now, the email is tracked as expected.
New! Ability to sync a non-CRM-contact in the To field to the CRM without creating a contact:
Supported for appointments.
If an email address in the To field does not match a CRM contact, the email address is synced as is to the To field in Dynamics but does not create a contact in Dynamics. Format: In Dynamics, in the To field,
a CRM contact appears in the First Name - Last Name format.
a non-CRM contact appears as an email address.
The email address is fully functional in Dynamics. It is possible to send emails or appointments to that address from Dynamics. To activate the feature:
New! Push and streaming notifications support for Office 365 OAuth connections:
Note: Push and streaming notifications were already supported for Exchange and credentials-based Office 365 connections.
Obtaining change notifications from Office 365 can be up to 90% quicker than polling EWS for the changes.
For more information on push and streaming notifications, see Change notifications for Exchange UCD.
Enhancement: OAuth tokens are periodically and automatically refreshed:
The maintenance task is run once a week, at the beginning of the blackout period on Sunday.
The task refreshes the token, updates the Office 365 connection, and saves the connection.
The last refresh date and time are displayed on the connection's Connection Details page, under Authentication Details.
A warning is logged 30 days before the token expires.
Exchange and Office 365
Ability to sync faxes as emails:
Faxes can be synced from the Inbox, Sent Items folder, or CRM-related drop folders created by Riva in an Exchange or Office 365 email client.
Some configuration is required.
New or Enhanced Sync Features
New! Ability to sync modules in the order that is most urgent to your organization: By default, the order for any given end user is address book (contacts, then leads), calendar, task, opportunities, cases, contracts, and then email — assuming that all those modules have been configured for syncing. Other modules may be synced too, like custom modules. The availability of modules also varies depending on the CRM. Prioritization: If the default sync order is not optimal for your organization, the sync order of modules can be changed. To change the order:
If a syncing module is omitted from the advanced option, it is synced last.
Enhanced functionality of dry-run mode:
Originally, dry-run mode was designed to be only a testing tool. Now, it can be used as a development tool as well. If the sync policy is modified while in dry-run mode, then when Disable Dry Run Mode is selected, the Policy Changes Detected dialog box appears. In the dialog box, the admin can choose to keep the policy changes or dismiss them.
User Experience (UX) Enhancements
New! Templates can be used to improve the appearance of error notifications:
Three HTML templates are now available, one per type of error notifications:
If no template is specified, the error notifications are sent in plain text.
Simplified email conversation tracking configuration: General background: It is possible to configure a sync policy so that after an email has been tracked manually, all the replies to it are tracked automatically to CRM as an email conversation. Specific background: The configuration was difficult to find and unnecessarily complex. Simplification: Now, the configuration is performed on only one page, the SmartConvert page. Only one check box needs to be selected: "Automatically synchronize emails based on conversation".
Automatic renaming of the .policy file when changing the policy name: In previous versions, when a sync policy name was changed on the policy's General page, the change was saved in only one place: the policy name displayed in the Riva Manager application. Riva did not change the names of the corresponding .policy file and its backups, which are all found in the Riva\Configuration installation folder. Now, when a policy name is changed in Riva 2.4.53 or higher, the new name is applied both to the policy in the Riva Manager application and to the .policy file and its backups in Riva\Configuration. Note: If the names of a .policy file and its backups do not match a policy name changed in earlier versions, the mismatch persists. Only if the policy is renamed in Riva 2.4.53 or higher will the names be made to match.
Performance improvement in Universal Change Detection (UCD):
It is possible to configure a sync policy so that changes detected by UCD trigger only module-specific synchronizations. Details:
By default, when a change is detected on any module, a full cycle is initiated for the user.
Now, it is possible to configure the sync policy so that if a change is detected, only the affected module is synced. That configuration results in less work and improved performance.