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 have published a simple example showing how you can customize what happens when DayBack receives a streamed update that an event in your view has been updated. This example will show a message to let a user know something they are looking at has been changed or added. Users will see something like “<event title> was modified” or “… was deleted.” You can use this to get loud when updates are received, or as the start of a “streaming log” users can review later. Check it out: https://docs.dayback.com/article/361-event-stream#Reacting-to-Event-Streams-NM_wu
This update includes a Salesforce client library that is now part of the core codebase instead of an action (for making custom requests to Salesforce). It adds a new route for Supabase onboarding. It includes new helper functions for updating resources in Firebase directly. It also includes the preview of event streaming features (which are disabled by default). This also improves the Supabase onboarding process so Supabase is enabled by default if signing up from the Supabase route. It fixes an issue in the admin interface where enabling a source type then clicking on that source type could show the wrong toggle position. And it includes a few small fixes to clean up console messages as well.
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.
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 update includes changes required to work with Salesforce’s upcoming security requirements which we’d previously deployed to beta. This includes support for PKCE challenges and Refresh Token Rotation. It also improves error handling when using a group-level authorization token. These changes should be backward-compatible and require no intervention from the user. They are targeted at deployments accessing DayBack from outside of Salesforce, especially those using group level Salesforce authentication.
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.
We’ve deployed an update to beta that includes a new event action trigger “On Events Fetched” and another called “After Event Save”. It adds a sign-out button and displays the currently signed-in account on the subscription expired modal. It also adds the event count in the breakout header in horizon view when breaking out by a field and removes the “No Events Found” message in horizon view if events are found, but just hidden by collapsing a row. There are multiple bug fixes around user management that could cause DayBack to mark a member as inactive when there are enough licenses and users are being added or removed. We’ve also corrected a few misspellings.