DayBack Status
Official status page for DayBack Calendar. Follow for updates, new features, and infrastructure status.

New Timezone Part 2
Deployed DBK 2.30.2. This was a small deployment that properly adds the timezone updates that were missing from the last deployment. They were included in QA but missed the last release.

Bug Fixes and New Timezone
This update fixes an issue in Salesforce when changing just the start time in the native Events object– the bug would move the event to that time rather than change the duration of the event. It fixes an issue that was causing an error when duplicating an event from unscheduled by drag-duplicating it into the calendar. It fixes an issue where a bookmark could fail to load if it has an improperly mapped custom field combined with a before event rendered action specified. And timezone support has been updated to include new rules for Vancouver BC. This also includes updates to get the new enhanced popover (currently in silent release) working in mobile.

Small Fixes and a Silent Version of DayBack’s New Popover
Today’s update fixes an issue in dark mode where the location text box would still show the map behind it after a value was entered. Behind the scenes, it adds the new enhanced popover, which can only be enabled by setting a config property in an action. This new popover is disconnected from the event, so you can drag it around and navigate in the calendar interface without closing the popover. The popover won’t be available in customer deployments for several more deliveries. This is the first of several deployments that will eventually release a new popover that customers can opt into, while keeping the current popover if it’s been very highly customized. Eventually, the new popover will let customers see streamed updates made by other users behind an event they may have open, and it should let folks resize the popover while making it easier to customize.

Breaking Change in Mobile: Whitelist Trusted Domains
The latest version of the Salesforce Mobile application for both Android and iOS fails to support canvas apps unless you explicitly allow them. This means that DayBack will not load unless you make the change below. Fortunately, this can be done at the org level and doesn’t need to be done on every mobile device The Fix Ask your Salesforce admin to follow these instructions: Here are the docs Salesforce has published on this if it helps. That should get DayBack working on everyone’s mobile device. If you find a device where this isn’t working, you may want to clear the app cache on the device..

DayBack Beta: Silent Introduction of a New Popover
This update adds a new popover that is disconnected from the event, so you can drag it around and navigate in the calendar interface without closing the popover. It also fixes a bug with the background of the location text box when in dark mode. The popover won’t be available in customer deployments for several more deliveries. This is the first of several deployments that will eventually release a new popover that customers can opt into, while keeping the current popover if it’s been very highly customized. Eventually, the new popover will let customers see streamed updates made by other users behind an event they may have open, and it should let folks resize the popover while making it easier to customize.

Hardening the Online Booking Relay
Today we deployed a new version of the DayBack public booking relay (API-Connect) 0.7.0. We had not been including these deployments on this site, but the pace of change is picking up, so we’ll start including enhancements to the relay here. This update to the changes “Fetch Failed” behavior to retry 3 times, instead of just once, and puts a little more time in between each retry. It also improves the internal error logging we monitor if the DayBack token server request errors out.

Improved Repeating Events
This update adds repeating events to Supabase calendars. It also adds the ability to change a repeating event’s time and apply that change to “All Repetitions” or “All Future Repetitions” in Supabase, Google Calendar, and MS365 sources. MS365 error reporting is also improved and this release also fixes an issue when creating a new Salesforce event, choosing repeating and then switching that event to another calendar source before saving the event. That used to cause some unpredictable outcomes.

DayBack Beta: Improved Repeating Events
This update adds repeating events to Supabase calendars. It also allows rescheduling repeating events to different times and saving those changes for “All Repetitions” as well as “All Future Repetitions”. It fixes a bug when defining the repetition sequence first and then switching to a different calendar on a new event. It also improves error reporting in Microsoft 365 calendars.

Fix for “Hide Empty Rows” in Horizon View
This update fixes some issues with “Hide Empty Rows” when using “Breakout By” in horizon view. It also improves that feature by honoring the sort order of resources and statuses. We also added two new helper functions: dbk.mutateFilterFieldList(filterList); which can be used to properly format resources or statuses after DayBack had already expected them. This will properly maintain folder structure and sort order. dbk.trustAsHtml(htmlString); which can be used when binding a value to an angular element that contains html so it properly renders the html rather than convert to a string.

Better Token Errors
This update fixes an issue where manually de-authorizing Salesforce Connect would show error toast when it shouldn’t.