Riva On-Premise 2024.2 Release Notes (2024.May)

  • Updated

These release notes provide a quick overview of what is new in the following release:

Release version: 2024.2.XX
Release date: 2024.May.19
Update procedure: How to update Riva
Manual update procedure: How to update Riva from a ZIP file
Free trial: Schedule a consult.

 

What's New in This Release

New Re-Initialization Option

Developed a new Re-initialization option that will allow Riva to resync all appointments with unmatched email flag in certain time range.

  • General - Filtered Resync - Re-scan and force update CRM data for items matching specific filter criteria [Exchange only]
  • Currently only supports Calendar appointments Exchange -> CRM
  • Can be scheduled to run at a specific date/time, or scheduled at regular intervals as a maintenance job
  • How to configure
     
  • User Benefits: Calendar appointments which were skipped from syncing on an earlier sync, can now be synced to CRM allowing for calendar parity.
    • Only appointments that have the "unmatched flag" can by synced
    • Riva can only apply the "unmatched flag" to appointments created after these options are enabled on the policy
       

New Updates!

  • Salesforce Education Cloud Exchange EWS Support
    • Education Cloud (Formerly SSH) sync support for Exchange EWS
    • Sync support for new "Shift" object, recurring and single item
      • Configuration that works for Exchange EWS that will synchronize the Education Cloud Shift object to Advising Shift Appointments in Exchange EWS.
      • User benefits: User will have the ability to sync the new Shift object
         

Bug Fixes

  • Issue: On first sync for users, syncing email (*inbox and *sent items) noticed that Riva keeps on retrying after receiving the "server busy" error, the sync cycle is extended to 9 hours.
    • Fixed by adding the option to set the retry limit to 60 mins (adjustable)
  • Issue: Riva is updating the start date of the meeting to different times in different user's sync cycles in certain edge case scenarios
    • Fixed by minor code changes
  • Issue: The option Sync.Salesforce.CustomEventRelation.UseUsersContact is not implemented for Interaction sync
    • Updated code  Sync.Salesforce.CustomEventRelation.DisableUserRelation=False, then the field Status__c  gets updated correctly.
  • Issue: Multiple instances of error "Object Reference not set to an instance of an object"
    • Updated various areas of code to handle this error

       
 
 
 

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.