Article ID: 564
Last updated: 15 Mar, 2016
WARNING: The Riva for Salesforce Single Sign-On connection strategy described in this article is not supported for new Riva On-Premise installations.
New Riva On-Premise installations include a new strategy to provide impersonation access into Salesforce: the Standard Impersonation Model. For instructions on implementing the Standard Impersonation Model, see Prepare Salesforce for Riva and Create and test a Salesforce connection. For current Riva On-Premise installations that use Salesforce Single Sign-On, administrators are encouraged to upgrade their Riva for Salesforce connection setup to the Standard Impersonation Model. For assistance, contact the Riva Success Team. The procedures in the following article have been deprecated. The information is being retained for clients who have not yet converted to the new Standard Impersonation Model. In most environment, customers elect to deploy the Riva for Salesforce.com by enabling the Riva DA-SSO service provider. In those deployments, the typical configuration involves creating:
This article describes management tasks for target Salesforce users:
How to disable/enable synching for target users in a sync policyUse these procedures to temporarily disable and re-enable data sync to all target users in a sync policy. To disable data sync for a sync policyDisable a sync policy to stop data sync to all target users of that policy. As soon as the policy is disabled, Riva will stop syncing the target users on the next full sync cycle.
To enable data sync for a sync policyEnable a sync policy to start data sync to all target users of that policy. As soon as the policy is enabled, Riva will start syncing the target users on the next full sync cycle.
How to disable/enable synching for single target userUse these procedures to temporarily disable and re-enable data sync to a specified Salesforce user. Remove the user to disable data sync temporarily to a target userTo temporarily stop syncing to a specific target user, remove them from their assigned sync policy. As soon as the policy is saved, Riva will stop syncing data to the removed target user.
Note: The removed user will remain visible in the user queue in the CRM Monitor application until the service is stopped/started or restarted. Add the user to re-enable data sync to a target userTo re-enable sync to a target user previously removed, re-assign them to the sync policy. As soon as the policy is saved, Riva will start syncing data to the re-enabled target user.
How to permanently remove a userThe following steps are required to permanently remove a target user. They are described in detail below:
How to remove the target user's transaction dataUse this procedure to permanently remove the transaction data files for the recently removed target user.
How to remove the target user's sync log files
How to Release the LicenseRiva will only recalculate license counts when the CRM Agent sync service is started or restarted.
How to add a new target userAdditional users can be added to a Salesforce SSO-enabled sync policy once initial data sync testing has been completed and the sync policy has been modified so that you are satisfied that Riva is synching data between Exchange and Salesforce in an expected manner. There are two methods to add target users:
Add new target usersTo add new target users to the SSO-enabled sync policy:
Once the user has been added to the sync policy, Riva will perform an initial sync to prepare the Exchange mailbox, and then continue with normal sync cycles between Salesforce and Exchange. How to handle pre-existing target users (how to move users between sync policies)If there are pre-existing Salesforce connections and sync policies for individual target users, it is possible to move those target users into the new SSO enabled sync policy. Ensure that you follow the correct procedures to prevent possible duplication of records or sync errors:
This article was:
Helpful |
Not helpful
Report an issue
Article ID: 564
Last updated: 15 Mar, 2016
Revision: 4
Views: 4596
Comments: 0
|