Today’s update improves DayBack’s ability to render events that may contain unclosed HTML tags, like the </3 symbols for 💔s.
Today’s release fixes a bug in public bookmarks that use text filters: in some cases, events wouldn’t show in the share after modifying an existing event in DayBack.
Today’s update fixed a bug where events on shared views could contain stale data when field mapping was changed after an event was shared. This could present as an event not being visible on shared views created after an event was initially shared. A user would create a shared view, then change field mapping, then create another shared view, and the event would not be visible on that second view. Fortunately, this has now been fixed.
Today’s update improves the way DayBack fetches new-feature notifications so it happens less often and now prevents notification fetches from happening more than they should. These notifications are the new feature announcements you’ll find when clicking on the three-dots or envelope icon in the upper-right of DayBack. (The envelope appears when you have new, unseen notifications.)
Today’s update improves the initial load process when a mix of different sources are enabled so a “no events” dialog is no longer temporarily shown.
Today’s small update traps for a bug from the Microsoft 365 API where it was sending a malformed response when attempting to retrieve the list of users. This only affected personal Microsoft 365 accounts and not ones that are part of a Business / Organization.
Just deployed an update that repairs an issue in Salesforce Connect where views with more than 1k events could have some events that fail to display. DayBack’s Salesforce Connect lets organizations deploy live access to their Salesforec schedules to folks who don’t have a Salesforce license. DayBack offers a few different ways to grant this kind of access. Learn more here: Calendar Sharing in Salesforce.
© SeedCode, Inc. 2013–2024       855-733-3263
Â