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.
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.
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.
This release completes the code required for the upcoming Salesforce changes. On top of the items deployed previously, this update adds a token-creation locking mechanism to prevent multiple tokens from being issued simultaneously (needed for Refresh Token Rotation). It also adds a notification into our internal systems if there are any token issues for customers using group level Salesforce authentication.
This update includes changes required to work with Salesforce’s upcoming security requirements. These changes should be backward-compatible and require no intervention from the user.
This change allows DayBack to asynchronously fetch all group settings at once and cache those settings locally in the browser using indexDB. This will make the speed at which DayBack loads more consistent, and testing shows up to a 200% speedup in loading group settings. DayBack now caches access tokens on the server to speed up reloads and navigation back to DayBack. Users will see this speed when they first open DayBack and when they arrive back at the calendar from other Salesforce pages or FileMaker layouts.
Deployed an update to beta that allows users to show the map side by side with unscheduled. This adds to the previous beta deployment, which includes a fix for events being offset when loading bookmarks, and a fix for part of the 3 dots menu not showing in some cases. If you’d like unscheduled events to show in the map (they don’t show by default), create a new App Action with the trigger “On Startup,” set override default to “no,” and use this as the code for the action: Note that using the map and unscheduled side by side requires a small change in two of the custom actions that are part of the map core. You can download these here, and the two updated actions are “map-core-main-functions.js” and “map-core-after-events-rendered.js.”
Deployed a small update to beta that fixes an issue where loading bookmarks that change the sidebar state could lead to the calendar or events being offset.
The latest beta deployment includes a big change to the way the app handles settings. This change allows DayBack to asynchronously fetch all group settings at once and cache those settings locally in the browser using indexDB. This will both speed up initial loading of DayBack as well as subsequent loads while making DayBack more resilient to slow networks. It will also now cache access tokens for all sources server-side to help speed up reloads and navigation back to DayBack. A new api endpoint has been added to update environment variables from an action or even outside DayBack. This deployment also includes a few bug fixes: preventing the DayBack loading image from covering the group selector on startup, and removing a potential gap at the top of the screen when disabling draft mode.
This update fixes an issue where dragging into unscheduled would change the date and time. It fixes an issue where events with no duration were not shown on the Month Schedule view. It improves the drag highlight on Horizon view when breaking out by a field so the highlight appears over the cell being dragged over and not the whole column. It includes a new helper function “resolveCustomFields()” that will create a “proxy event” object, allowing getting and setting custom fields more easily based on the field name and not the id. There is also an under-the-hood change that will help transition to using cached access tokens. This change allows backwards compatibility with this new token format.