What's New

• ROU-12823 - Google has deprecated the KML Layer, as an alternative, Google suggests using an external provider to render the layer. This update introduces a high-performance KMLLayer powered by deck.gl, and loaders.gl, ensuring continued support and enhanced visualization capabilities ahead of Google's planned removal of the KML Layer.

Fixed Issues and Improvements

• ROU-12857 - Fixed an issue that caused the RemoveDirections client action to raise an error. This occurred when the action was called before any routes had been added to the map, triggering a script failure that halted all subsequent logic execution.

What's New

• ROU-12633 - Added a new HeatmapLayer block using deck.gl as the provider. 
  This update introduces a high-performance HeatmapLayer, powered by deck.gl, replacing the native Google Maps HeatmapLayer. This ensures continued support and enhanced visualization capabilities ahead of Google's scheduled removal of the legacy library in Maps JavaScript API version 3.65 (May 2026).
• ROU-12638 - Updated Google Maps Drawing Tools to use TerraDraw as the new default provider. 
  This update replaces the native Google Maps Drawing Library with TerraDraw to ensure continued functionality following Google's announcement that the legacy library will be removed starting with Maps JavaScript API version 3.65 (May 2026).

Fixed Issues and Improvements

• ROU-12504 / RPM-6440 - Fixed an issue that caused the Map component to experience significant performance lag and unresponsiveness. 
  This occurred when handling large datasets with multiple markers, specifically when the MarkerCluster feature was enabled.

Fixed Issues and Improvements

• ROU-11655 - Fixed an issue that caused the LeafletMap to inadvertently scroll the background page when the component was placed in focus. 
  This fix ensures that map interactions remain contained within the widget, preventing unexpected page scrolls for the user.
• ROU-12285 / RPM-6181 - Added a new optional configuration called respectUserPosition to both the Map and Leaflet components.
  This allows the map to maintain the user’s current position when calculating the map center, rather than snapping back to a default location.
  Fixed an issue that caused the Map to snap back to the initial center point even after a user had manually moved or zoomed. 
  The logic has been updated to prioritize the user's current view if respectUserZoom or respectUserPosition is enabled.
  If those settings are disabled or the map is in its default state, the center will fallback to the developer-defined position, the first marker, or a calculated center of all markers when Zoom Auto is active.