Skip to Content (Press Enter)
Community › Forge › Assets list › OutSystems Maps
Login to follow
OutSystems Maps

OutSystems Maps (ODC)

Supported
Stable version 2.1.0 (Compatible with ODC)
Uploaded on 11 August 2025 by OutSystems
OutSystems Maps

OutSystems Maps (ODC)

Details
Detailed Description

Maps made easy, from developers to developers.

Use the OutSystems Maps to create visual rich enterprise-grade interfaces that help the user to quickly have map-based insights of the data.

Key features

  • Built for Web and Mobile apps
  • Simple to use and extend
  • Add Markers, and Directions
  • No javascript knowledge required


Developer experience using OutSystems Maps

To access a sample version of OutSystems Maps, you can download the OutSystems Maps Sample from Forge and launch it in Service Studio. These samples also have documentation.

We're continually improving this solution and adding more features. To help us cover more specific and complex scenarios, let us know what you'd like to see in this component's support tab.


Note: Currently, Google Maps and Leaflet are supported.
ODC Asset screenshot_0ODC Asset screenshot_1
Limitations
Release notes 

What's New

  • ROU-12040 - Added support for the new Google Routes API for all client actions related to Directions.
    This update ensures compatibility, as Google now classifies the older Routes APIs as legacy - read more.
  • ROU-12041 - Added a new component named SearchPlaces, which leverages the latest Google Maps Places API.
    The existing component was renamed to SearchPlaces_Legacy, as Google now classifies the older Places APIs as legacy - read more.

Fixed Issues and Improvements

  • ROU-11822 - Improved the component's feedback to indicate that the MapStyleId property cannot be changed after map initialization.
  • ROU-12069 / RPM-5988 - Fixed an issue that caused the Markers to throw an error when being destroyed when the Map was removed first.
    This occurred when the Map was removed and contained Marker blocks. The Map would remove all the Markers from an internal list to avoid memory leaks (when the marker is created via API).
    To fix the issue, the Map is now removing only the markers created by the API, leaving the remaining Markers to remove themselves from the internal list.