Riva Insight 2024.3 Release Notes

New! Login with Microsoft

• What's New!
  
  • You can now use your existing Microsoft account credentials to log in to Riva Insight. This eliminates the need to manage separate login credentials and simplifies the access process.
    
    
• How to Enable
  • In Riva Cloud, go to the settings for your email connection.   Check the "Enable for Insight Sign-on" option to enable.

• Availability
  • Login with Microsoft is presently only available for Insight Cloud.

New! User Experience

• What's New!
  
  • Riva Insight's user interface has been redesigned to be cleaner, more intuitive, and easier to navigate.
  • The context view, Track in CRM, and sales engagement features are available in separate tabs (labeled 'Related', 'Track' and 'Actions').
  • The Search has been moved to the top application bar.
  • Login with Salesforce will default to the last used login.
  • Ability to "Quick Track" a meeting or email.
• Riva Insight User Guide 2024.3

New! Leads in the Context View

• What's New!
  • Additional support for Leads has been added to Riva Insight
  • Meeting attendees and email recipients that have leads within CRM will now show in the context view (related tab).
  • Track in CRM will autopopulate with leads if there are no matches to contacts.

Enhancements

• Riva Insight Cloud (with Web Add-in client)
  
  • 9d52660b - Added feedback option to Riva Copilot to allow improvements/suggestions to be submitted.
  • 2024.3.9.5608 (2024.1.9.6462) - Updated Riva Copilot to provide contact suggestions for meetings/appointments.
• Riva Insight Cloud and On-Premise (any client)
  • 2024.3.9.6764 (2024.1.9.6800) - Added a setting that will allow multi-select related item controls to be autopopulated with multiple accounts instead of the first one. To enable, add the key  to the related item control in the track configuration file.
    

    • <IsRelatedContactControlPopulateAll>true</IsRelatedContactControlPopulateAll>

  • 2024.3.9.7299 (2024.1.9.7440) - Autopopulate leads in Track in CRM if no contacts are autopopulated. Available by default in 2024.3 when leads are enabled.  Must be enabled for 2024.1 by adding the key to the company settings configuration file.

    • <add key="Insight.ContextView.ShowLeads.IsEnabled" value="True" />

• Riva Insight Cloud and On-Premise (with Web Add-in client)
  • 2024.3.9.6826 (2024.1.9.6849) - Added a setting that will allow a new meeting to be created and tracked without sending out the meeting invitation to the meeting attendees.  Add the key to the advanced options of the track configuration file to enable.

    • <add key="Track.MailItems.TrackAndCloseForNewMeeting.IsEnabled" value="True" />

  • 2024.3.9.7568 (2024.1.9.7573) - Added the ability to copy the email or meeting/appointment subject to a text field in Track in CRM.
  • 2024.3.9.7547 (2024.1.9.7637) - Added the ability to automatically and manually copy the email or meeting/appointment description to a text field in Track in CRM.
  • 2024.3.9.7682 (2024.1.9.7683) - Added the ability to specify search strings that will determine what text to copy up to when copying the email or meeting/appointment description to a text field in Track in CRM.

Bug Fixes and Other Changes

• Riva Insight Cloud (with Web Add-in client)
  • 2024.3.9.5402 (2024.1.9.5383) - Fixed issue where Riva CoPilot does not show the 'added' or 'updated' status after creating or updating a suggested contact.
  • 30444766 - Added descriptive error for when Riva Copilot is unable to analyze a message due it being too large.
  • 2024.3.9.5891 (2024.1.9.5971) - Show error message when Graph secret has expired.
  • 4b766691 - Added an error message when there is a missing security token between Riva Insight and Riva Copilot. 
  • 2024.3.9.6290 (2024.1.9.6287) - Fixed issue where Riva Copilot prevented clicking on buttons are links that appear near the Riva Copilot button.
• Riva Insight Cloud and On-Premise (any add-in client)
  • 2024.3.9.5503 (2024.1.9.5536) - Fixed issue where the related item field in Track in CRM switches back to account after selecting a contact in the related person field.
  • 2024.3.9.6608 (2024.1.9.6696) - Added a clearer error message for when a user does not have access to a record type or record type does not exist.
  • 2024.3.9.7202 (2024.1.9.7216) - Addressed issue where calls to get CRM configuration details were not cached, resulting in repeated calls to CRM.
• Riva Insight Cloud and On-Premise (with Web Add-in client)
  • 2024.3.9.5369 (2024.1.9.5370) - Made change so that the most recent version of the sync configuration is used for each module when there are multiple sync configurations found.
  • 2024.3.9.5479 (2024.1.9.5497) - Fixed issue when selecting the 'limited' version of the manifest and then adding a title reverts back to the 'standard' version of the manifest.
  • 2024.3.9.6039 (2024.1.9.6041) - Fixed issue where notes from Track in CRM were not showing in the pop-out view.
  • 2024.3.9.6076 (2024.1.9.6077) - Fixed issue where the timezone autodetect sometimes uses the server timezone instead of the client.
  • 2024.3.9.6129 (2024.1.9.6152) - Added missing PersonObject and RegardingObject properties to the property inspector dev tool.
  • 2024.3.9.6390 (2024.1.9.6408) - Ensure StickyTrack is used instead of DirectTrack when tracking items in subfolders.  Show error message when Create New folder (required for StickyTrack) is missing or not in the Sync Configuration.
  • 2024.3.9.6588 (2024.1.9.6606) - Fixed issue when tracking that showed a changes detected working due to format differences of the meeting location between the client and server versions of the appointment/meeting.
  • 2024.3.9.6681 (2024.1.9.6700) - Added a "close" button to the login confirmation page due to Microsoft add-in bug with iOS not allowing the page to be automatically closed, which was preventing the ability to log into Riva Insight.
  • 2024.3.9.6713 (2024.1.9.6745) - Fixed issue where meeting cannot be found when tracking a delegate appointment. Fixed issue where special characters in the meeting location caused tracking to fail.
  • 2024.3.9.6812 (2024.1.9.6813) - Fixed issue where the related person/item property is not set when tracking, resulting in the attendees not being added to the interaction record in CRM.
  • 2024.3.9.7154 (2024.1.9.7144) - Changed inline replies and forwards to automatically close after tracking and sending, to address issues where changes made after tracking and sending are not kept. Previously after tracking and sending, the email would still be open, even though it was already sent.
  • 2024.3.9.7164 (2024.1.9.7217) - Allow user to turn off autosave drafts for Track in CRM due to Microsoft bug in Outlook Mac that switches to the Outlook attendee list (from Insight) whenever a save occurs. Setting can be toggled by the user in the user settings page.
  • 2024.1.9.7229 - Fixed issue where the 'back' button was missing when navigating between records.

Post-release Bug Fixes and Enhancements

• Riva Insight Cloud and On-Premises (any client)

  • 2024.4.9.8684 (2024.3.9.8688) - When encountering a module the current user does not have permission to, Riva Insight will now disable the module for the remainder of the session.
  • 2024.4.9.8713 (2024.3.9.8720) - Fixed an issue where date and time fields were not being locked when lock mode has been enabled for Track in CRM.
  • 2024.4.9.8776 (2024.3.9.8791) - Fixed an issue where users may see a "QuotaExceededError" in the Insight sidebar by moving data that is not required to be persistent from browser local storage to browser session storage.
  • 2024.4.9.8858 (2024.3.9.8874) - Added a configurable option that will show the record immediately after it was created or updated. To enable, add the following key in the CompanySettings.xml:

    • <add key="Feature.CreatesAndUpdates.GoToRecordAfterSave.IsEnabled" value="True" />

  • 2024.4.9.8925 (2024.3.9.8938) - Unmatched contacts will no longer appear for contacts and leads that are matched by a secondary email instead of just the primary one. 
    • Note: Ensure the CRM connection specifies the additional emails for this to work as expected.
  • 2024.4.9.8942 (2024.3.9.8943) - Updated the StackExchange Redis client library to version 2.7.17.
  • 2024.4.9.9008 (2024.3.9.9000) - Fixed a bug where a large recipient list in Outlook resulted in a 414 error.
  • 2024.4.9.9041 (2024.3.9.9091) - Added an option to prevent the browser autocomplete from populating the entire Track in CRM or Create/Update forms. To disable the form autocomplete, add the following key in the CompanySettings.xml:

    • <add key="Feature.Track.TextBoxAutoComplete.IsEnabled" value="false" />

  • 2024.4.9.9644 (2024.3.9.9619) - For datetime fields, when the date is blank by default, set the time to be blank instead of 12:00.  When the date has a value, ensured that the time must have a value.
  • 2024.4.9.9568 (2024.3.9.9441) - Fixed a bug where Insight displays the Track in CRM status badges under contacts and accounts in the side panel, instead of just the main email or meeting card.
  • 2024.4.9.9494 (2024.3.9496) - Performance enhancments by optimizing the use of Redis by moving a number of settings from the cache to session.
  • 2024.4.9.9427 (2024.3.9.9568) - Fixed an issue where the track status badges were appearring in the account or contact cards, and should not have been.
  • 2024.4.9.9698 (2024.3.9.9750) - Added a warning to turn off shared calendar improvements for when a meeting is tracked as a delegate and tracking fails due to shared calendar improvements being turned on.
  • 2024.4.9.9879 (2024.3.9.9880) - Fixed bug where the draft values for the multi-module control (i.e. "relate to") where not maintaining the values when switching between emails.
  • 2024.4.9.9962 (2024.3.9.9963) - Fixed an issue when making a change in appsettings, the change is not reflected in Riva Insight right away.

  Riva Insight Cloud and On-Premises (with Web Add-in client)

  • 2024.4.9.8224 (2024.3.9.8283) - Made changes to reduce instances that Track in CRM will create an autosave draft when autopopulating.
  • 2024.4.9.8261 (2024.3.9.8264) - Added a configuration option that will disable Quick Track from the email and event cards. 
    • To disable for all modules, add the following key in the CompanySettings.xml:

      • <add key="Feature.EventCard.QuickTrack.IsEnabled" value="false" />

    • To disable for email, add the following key in the CompanySettings.xml:

      • <add key="Feature.EventCard.QuickTrack.IsEnabled.Email" value="false" />

    • To disable appointments/meetings, add the following key in the CompanySettings.xml:
      • <add key="Feature.EventCard.QuickTrack.IsEnabled.Appointment" value="false" />
  • 2024.4.9.8695 (2024.3.9.8750) - Fixed issue where Track in CRM was not auto-populating hidden control types (hidden control types still get set, whereas control that are hidden due to visibility rules do not).
  • 2024.4.9.8361 (2024.3.9.8368) - Fixed an issue where Track in CRM was setting values for controls that were hidden by visibility rules (hidden control types still get set, whereas control that are hidden due to visibility rules do not).
  • 2024.4.9.8316 (2024.3.9.8326) - Fixed a bug where Track in CRM was setting an incorrect 'skip attachment' category name, resulting in attachments being synced.
  • 2024.4.9.8652 (2024.3.9.8653) - Fixed a bug where Track in CRM was not clearing custom property values when retracking an appointment/meeting.
  • 2024.4.9.9418 (2024.3.9.9418) - Fixed a bug where Login with Microsoft was not working for iOS devices. NOTE: Allow cross-website tracking must be enabled in the iOS settings.

  Riva Insight Cloud (with Web Add-in client)

  • 2024.4.10.0107 (2024.3.10.0105) - Fixed an issue where the connection to Salesforce is not maintained after logging out of and back into Riva Insight using "Login with Microsoft".
  • 2024.4.10.0742 (2024.3.10.0744) - Fixed an issue where adding a Sales Engagement license to an existing Riva Insight licence results in a vlank screen.

  Riva Insight Cloud and On-Premises (with Windows Add-in client)

  • 2024.4.9.9564 (2024.3.9.9574) Fixed a bug where the latest Windows add-in version was not properly displayed for the add-in upgrade notice.