We have updated the custom actions used in the map core to only use traffic aware routing when departure time is included and in the future. Previously, using a blank departure time or routing events in the past could create some unusual routes.
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.
This update adds the ability to secure your DayBack account with multi-factor authentication using a one-time password (utilizing an authenticator app). Previously, only SMS was available for multi-factor authentication. You’ll also see a new feature called Environment Variables in administrator settings that allows you to define variables that can be referenced in actions. The transition when navigating from settings back to the calendar has been improved. It fixes a bug preventing map pins from highlighting when selecting the corresponding event when using the native Google map markers. It also fixes a bug that was causing DayBack to think an event was dragged when closing a popover if an event was initially dragged but the drag was cancelled and then the event was clicked open.
Today’s update fixes an issue where map pins weren’t loading in some cases. This was caused by a small change in the Google Maps API preventing a hover listener from being applied to child elements of a map marker.
Adds a new app action “On Startup”. This app action runs before all others and will be a great place to run custom code that isn’t attached to a specific activity but needs to run at the beginning of loading. This also fixes an issue when routing with map actions when the geocode field is mapped to a text field.
We’ve updated DayBack’s maps to no longer utilize the distance matrix api from Google as it’s now in legacy status. This has been swapped out for the new routes api. There are no user-facing changes. The changes are all in the “map-core-main-functions.js” file found here.
The two new features most recently in beta are now live in DayBack. If you have a ton of bookmarks, you can now filter them using any text in the name of the bookmark or who created it. And you can now map a geolocation field OR a text field for the new geocode field in DayBack. This should make it easier to use a formula field when grabbing the location of an upstream record like an Account.
We’ve deployed an update for maps to our extensions library. This improves messaging when geocoding events (adds toast when done). Routes now include a small loading animation in the map button when routing is in progress. This update also includes fixes to prevent “ghost routes” (where a route was doubled up and wouldn’t go away). The updates include changes to 3 files: “map-core-main-functions.js“, “map.css“, “geocode-location.js“
The core mapping action in DayBack now recognizes multi-select in the calendar. This means you can select a series of items and route them to different resources to see which route might be best. You can also use this feature to try including an item in an existing route before editing the item’s assignment. See both of these examples in action here: https://dayback.com/route-optimization/
This update adds unscheduled and maps to mobile devices. It fixes a bug when dragging an event to resize from the left when horizon view is in breakout mode. It improves behavior and messaging when attempting to drag events into the unscheduled view when there is no unscheduled field mapped. And it fixes an issue in Firefox where native scroll bars were appearing when they shouldn’t. It also adds a meta tag for mobile to prevent a warning in the Chrome dev console.
© SeedCode, Inc. 2013–2025 855-733-3263