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.
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.
This update fixes an issue where manually de-authorizing Salesforce Connect would show error toast when it shouldn’t.
This update improves access token handling for Salesforce especially when using a shared account credentials for a group–as you would for online booking. Coinciding with this release we have also deployed API-Connect 0.2.1. This updates our public booking relay so we can easily add our customers to a standardized system which is more secure and handles token management better. Our own public booking is already using this and we are moving all customers to it one by one over the next few weeks.
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
We have deployed a hotfix update for DayBack. This fixes an issue that was causing Safari to forget that draft mode was selected due to the interaction of Safari and our minified codebase.
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 is a small update that fixes a bug where dragging a Supabase event could reset the duration if the All Day field wasn’t mapped. It also adds a new welcome page for Supabase sign ups.
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.
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.