When you clear a resource filter in DayBack, the calendar will no longer clear your selected resources as well. In some cases, this used to put the calendar into an unfiltered state, asking it to show events from all the possible resources. In large deployments, this could cause things to slow down; now the calendar will preserve your selected resources until you de-select them or filter them out.
Today’s release also fixes a bug that could cause events to render more than once (or render when they shouldn’t) when toggling a calendar on and off quickly before the initial process of fetching the events has been completed.
Today’s update resolves an issue where the calendar could render more than once when switching views and a “no events found” message could appear in error.
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.)
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–2023 855-733-3263