Today’s update fixes an issue that prevented the “After Calendar Rendered” app action from running when cookies were not available. This generally means Salesforce 1 mobile on iOS. We do not use cookies for our app action, but another internal error related to that check was causing the code execution to stop before it ran the app action. This was due to some very old code that we had from when we needed to detect cookies in FileMaker on windows and warn if they weren’t available. This code has not been necessary for some time.

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.

Today’s update fixes the “Go to sources” button in DayBack for FileMaker so it properly takes you to the correct FileMaker source config.

Today’s update also fixes an issue where an unscheduled event popover would remain on the screen when scrolling if an on-click app action was set to prevent default. Learn more about unscheduled items in DayBack.

Today’s update fixes a bug that wouldn’t allow users with existing Salesforce accounts to be added to a DayBack group outside of Salesforce.

Today’s update fixes an issue when loading a bookmark on mobile that is set to display the unscheduled sidebar. The unscheduled list isn’t available on mobile, but the bookmarks left space for it, making the mobile views unusably narrow for some bookmarks.