DayBack Status – Search Results

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

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.

Read More »

DayBack Beta: Event Streaming & Helper Functions

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 first round of event streaming features (which are disabled by default). It includes a few small fixes to clean up console messages as well.

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 »

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

Read More »

DayBack Beta: Cache Improvements

This update fixes an issue where restoring a snapshot in draft mode could leave some settings being fetched from local cache. It also adds some improvements under the hood for us to use internally allowing a quick migration from Salesforce to Salesforce Connect.

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 »

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 »
Current Status
 
Updates by Category
Subscribe to Updates

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