DayBack Status – Search Results

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.

Read More »

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.

Read More »

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.

Read More »

Security Changes

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.

Read More »

DayBack Beta: Security Changes Part 2

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.

Read More »

DayBack Beta: Security Changes

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.

Read More »

New Actions

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.

Read More »

DayBack Beta: New Actions

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.

Read More »

Map and Unscheduled Side by Side

We’ve deployed the update from beta that allows users to show the map side by side with unscheduled. This also 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.” Under the hood, this release adds two new seedcodeCalendar methods called setPersistent and getPersistent. These create a place to store global values that don’t get cleared out when navigating to admin settings and back and be useful for devs who are managing event listeners and such in their custom actions.

Read More »

DayBack Beta: Map and Unscheduled Side by Side

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.”

Read More »
Current Status
 
Updates by Category
Subscribe to Updates

Subscribe to receive updates of new features and infrastructure status changes: