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

Bug Fixes, Improvements, and Supabase
This update adds a new Supabase calendar source. It adds a new app action trigger “On Analytics Tooltip Show” which will trigger when showing a tooltip in analytics. A timezone encoding issue when using Salesforce Connect with the DBK API proxy has been fixed. A bug affecting the helper function dbk.updateDbkEnv where duplicate environment variable entries could be created has been fixed. It improves handling of resources changing where the calendar view could change the number of resources visible. And the color consistency of help button icons is improved while the instructions for customizing the display field have been improved.

DayBack Beta: Bug Fixes, Improvements, and Supabase
We updated beta to include a new app action trigger called “On Anayltics Tooltip Show”. This can be used to control what happens when hovering a point in analytics. It also includes new refinements hardening how we handle when the resource page no longer exists due to resource counts changing. The calendar should properly handle resetting that state without showing a blank calendar. It also fixes an issue when using the new helper function dbk.updateDbkEnv that could cause duplicate entries. There are many improvements to the new Supabase integration. It includes some lableing refinements in settings to make things more clear. It also fixes an issue where Salesforce Connect could fail to retrieve events when in a timezone with a positive offset when using our proxy server. Finally, it improves the consistency of help icon colors in both light and dark mode.

DayBack Beta: updateDbkEnv() Fix for Developers
If you’re using the new dbk.updateDbkEnv() helper function to streamline your actions with environment variables, this update addresses a bug that could cause the creation of duplicate keys.

Updated Routing’s Use of Traffic
We have updated the custom actions used in the map core to only use traffic aware routing when departure time is included and in the future. Previously, using a blank departure time or routing events in the past could create some unusual routes.

DayBack Beta: Supabase Calendars
Today’s update includes the first version of a new Supabase calendar source. It also fixes an issue where Salesforce Connect could fail to retrieve events when in a timezone with a positive offset when using a proxy server. Finally it improves the consistency of the calendar’s help icon colors in both light and dark mode.

Bug Fix for Related Resources
This update fixes an issue preventing save when changing the resource of an event in Salesforce when an Event object has a related resource mapped to the Users object. It also fixes an issue where events could appear offset when loading a bookmark in FileMaker that changes the sidebar state. Finally it adds the ability to set environment variable values from an app action. The new dbk.updateDbkEnv(key, value) function which persists dbkEnv changes directly to settings. See “Setting Values using App Actions” section for more details.

DayBack Beta: Bug Fix for Related Resources
This update fixes an issue preventing save when changing the resource of an event in Salesforce when an Event object has a related resource mapped to the Users object. It also fixes an issue where events could appear offset when loading a bookmark in FileMaker that changes the sidebar state. Finally it adds the ability to set environment variable values from an app action (thanks Michael).

Additional Hardening
This is a small update that improves query parameter handling when using built in Salesforce Connect methods in custom actions that use our proxy server.

Hardening for Online Booking
Just a small update to improve the performance of the backend used for online booking.

Performance: Respect Map Bounds
Deployed a small update that fixes an issue in FileMaker when using a map only source and enabling the “Limit to map bounds” option would result in all map events being fetched rather than properly limiting them to bounds.