DayBack Status – Search Results

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

Fix for “Hide Empty Rows” in Horizon View

This update fixes some issues with “Hide Empty Rows” when using “Breakout By” in horizon view. It also improves that feature by honoring the sort order of resources and statuses. We also added two new helper functions: dbk.mutateFilterFieldList(filterList); which can be used to properly format resources or statuses after DayBack had already expected them. This will properly maintain folder structure and sort order. dbk.trustAsHtml(htmlString); which can be used when binding a value to an angular element that contains html so it properly renders the html rather than convert to a string.

Read More »

Example Code: Reacting to Event Streams

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

Read More »

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

Read More »

New Action for Analytics

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.

Read More »

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 »

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. The new dbk.updateDbkEnv(key, value) function which persists dbkEnv changes directly to settings. See “Setting Values using App Actions” section for more details.

Read More »

Additional Hardening

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.

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 »

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: