This update adds a new app action trigger called “After Analytics Chart Drawn”. This action trigger will fire any time the calendar’s analytics chart is drawn and will fire for each chart line. The primary use case of this trigger is to modify specific chart lines. You can add css classes, change visibility etc.
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.
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.
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.
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.
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.
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.
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.
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.
Deployed DayBack 2.14.5. This is a small under-the-hood update that adds a new API endpoint for updating environment variable values.
© SeedCode, Inc. 2013–2025 855-733-3263