Riva Cloud 2025.1 Release Notes

New Features

This release introduces the ability to configure independent Insights for different groups within the same Salesforce Org. By eliminating shared configurations, it removes restrictions, reduces complexity, and improves performance, ultimately speeding up implementations. For more details related to this new feature, please refer to this Knowledge Base article.

Enhancements

Adding, Enabling, and Disabling Users Without Disabling the Policy in Riva Cloud

Overview:

In Riva Cloud, the previous process required disabling the policy to add, enable, or disable users. This often resulted in syncing disruptions and increased manual effort. With the latest enhancement, Riva Cloud now allows users to be added, enabled, or disabled without disabling the policy, streamlining user management and improving efficiency.

Previous Challenge:

Previously, when administrators needed to add, enable, or disable users, they were required to disable the policy first. This process caused syncing disruptions, as all syncing activities would stop during the policy disablement. Additionally, administrators had to manually re-enable the policy after making the user changes, creating unnecessary delays and manual work.

Enhancement to Address the Challenge:

In Riva Cloud, we don’t allow administrators to add or remove users if the policy is enabled. The procedure required disabling the policy, adding the users, and then re-enabling the policy. Originally, this requirement was put in place because anytime a policy modification occurred, Riva would stop all current syncing users, reload the policy, and then reschedule everyone to start syncing again. Forcing the disabling of the policy ensured that all users would stop syncing to guarantee a "clean" stoppage. We addressed this problem by making the change detection in sync more intelligent. If the only change to the policy is the user's list, Riva Cloud will now simply add the users without forcing a full restart of the policy. Therefore, we no longer need to force users in Riva Cloud to disable the policy before adding or removing users.

New! Graph Calendar Code Updates

We have made vast improvements to how we handle calendar syncing with Graph!

1. Batch Processing: Calendar module sync now uses batch requests for retrieving events in bulk. We should see a 3-4 times improvement in performance for bulk retrieval of items with batching enabled.
2. Calendar Poll Changes: The calendar module now has the ability to poll the changes with full or walking ranges. We will see a reduction in the number of 503 general exception errors if we poll changes with walking ranges.
   1. By default, Riva poll changes for the entire date range, but we can also configure it to poll changes using an incremental (walking) range
3. Graph Delta Tokens: Currently, we rely on the repoll maintenance job to refresh the Delta token for Graph policies. It refreshes the tokens after every week. Riva recently introduced a new class, GraphTokenRange, which is self-sufficient to refresh the delta tokens without relying on the repoll maintenance job.

Please Contact Us for assistance with enabling these Calendar updates.

Hot Fixes

1. Enhanced logging in Splunk for better tracking of existing exception-handling logic.
2. The verification code expiry time for the "Forgot Password" functionality in Riva Cloud process has been reduced from 30 minutes to 10 minutes.

Other Changes

1. Added the change to ensure the Track State Service is used by default for Riva Cloud.
2. When creating the application in Azure Enterprise Application via Riva Cloud, users will have the option to skip the admin consent step
3. Updated the default impersonation method for Client Credentials from "Delegate Full Access" to "Impersonation", ensuring successful connection tests via Riva Cloud or Riva Admin Center. Any necessary updates for customers previously onboarded have already been handled prior to the release.