This update fixes an issue preventing scrolling breakout items in analytics. It also adds a convenient click to copy method for subscription numbers in users and billing and group / org id’s in migrate settings. Finally, it also improves the styling of help icons in the popover so they no longer appear cut off at the bottom.
This update includes a new feature called “Draft Settings Mode”. When enabled this feature will scope all settings changes to your current session. These changes can be saved as a snapshot or published for everyone in your group. This update also simplifies settings migration. Settings migration is now enabled for everyone and settings can only be pulled into your currently signed in DayBack group. The ability for non admin users to set a default resource for calendars has been added. It also fixes an issue that could cause html in an event to make the event grow too large and affect the view. The app action helper for mutation observers has also been improved to allow for watching on an element that hasn’t yet been added to the DOM.
Michael has published a new extension showing how to add buttons to DayBack’s popover next to the Save & Close buttons. The example will add up to three buttons, and includes a few common Salesforce icons for related contact, account, etc. You can also use your own icons or any of the FontAwesome icons DayBack supports. Add Buttons: https://dayback.com/listing/add-buttons-to-event-popover/ Extension Library: https://dayback.com/extensions/
This update fixes an issue where public shares could show resources that weren’t enabled when the share was created and resources could appear outside their proper folder. It also fixes an issue where a modal dialog could appear below an unscheduled event popover. We’ve also improved the behavior in horizon view when breaking out by a date field so the breakout sections are now sorted by the breakout date. For developers, this update also adds a new helper function for custom actions allowing the use of mutation observers to detect when dom changes occur.
We’ve added a new sorting function you can use inside Event Actions to override the calendar’s default sort. This is in addition to the existing sort method that lets you add new tie-breaker criteria to the sort. This new sort is probably most useful on horizon view or on pivot-list view when it’s set to week scale; we added this for a customer who wanted to sort their projects by due date (instead of start date) on horizon view. Details are here: Sorting Events.
Today’s update fixes an issue that could cause non-Salesforce events to render improperly if they contain malformed HTML. It also fixes an issue with the After Events Rendered app action if Google was a calendar source, but no Google calendars were selected where the app action would not properly trigger. An issue where non-Salesforce admins who were set as DayBack admins could not create snapshots was resolved, as well as an issue where some Salesforce Orgs could not use the migrate settings feature. It also resolves an issue when editing an event with a custom action and supplying a blank value for a field could result in that field data not being applied.
The pivot-list view in DayBack can now be viewed at week scales–where the swim lanes are your resources, and each column is a week. Previously, each column could only be a day, and the view was capped at 30 days. Now, you can use this view at scales from one day up to 23 weeks. Details here: Resource Planning at Longer Timescales