Customer facing release webinar is scheduled for September 18 at 2PM ET, register here.
Multiple enhancements and fixes were deployed for calendar sync and task sync.
Meeting AI now supports multiple Accounts.
A minor bug in dashboard drop down menus was fixed.
Enhancements
Calendar Sync - Location Field Character Limit
In some situations the location field of an event can have more than 255 characters in it, which exceeds Salesforce’s character limit, resulting in the event failing to sync.
Calendar Sync now truncates the text in the location field to 255 characters to prevent sync failures.
Calendar Sync - Add Users to Events
When a person exists in Salesforce as a Contact and as a Community User, the sync would prioritize the Community User instead of the Contact.
An update was made to ensure that Contacts are prioritized over User records when the Add Users to Events setting is enabled.
Meeting AI - Multi Company Support
When a meeting had more than one company invited to a meeting, Meeting AI would research the first company it found. Any other company would not be displayed anywhere.
An update was made so that multiple companies are displayed in the Accounts tab when viewing a researched meeting. All the researched contacts on the event from every researched company are displayed in the Contacts tab.
Fixes
Dashboard - Dropdown Menus
On some pages that have blades with drop down fields, the fields would not close when clicking outside of the field.
A fix was implemented to ensure that drop down fields behave correctly when the user clicks in and out of the fields.
Calendar Sync - Event Sync failing
For some orgs that had the Enable Salesforce Invitees setting turned off, users experienced recurring sync failures. This was a result of a bug that was introduced in last week’s release.
A fix was implemented to ensure that sync runs correctly when the Enable Salesforce Invitees setting is turned off.
Task Sync - Task Sync failing (Outlook Only)
Customers on Outlook and using task sync experienced failures. This was a result of changes made in the Microsoft Graph API v5.
Updates were made to account for the changes and the sync issues should now be resolved.