Shared Interactive Maps
Use Mapsly to create a custom map shared by a link, that will contain a subset of your CRM data controlled by URL parameters, multi-level filters, adjusted permissions and custom tiles. Use cases:
A shared interactive map allows anonymous users (visitors) to view, edit and interact with a subset of data from your CRM via an simplified Mapsly interface.
The subset of data is defined by one or multiple dynamic layers created using Mapsly formula builder.
If multiple dynamic views are shared within a map, they will be available as layers and the user will be able to select them in any combination.
In a dynamic layer used for shared maps you may also use variables that will be later passed in the map’s URL. Example of a layer’s formula with an URL variable:
Lead Type = Vendor AND Customer Id = %customer_id
Here, customer_id can be passed in the map’s URL:
Typical use cases for URL variables include:
A missing URL parameter will cause the condition to be false.
Similar to adjusting fields to be shown for a particular object, you may define fields to be shown to anonymous users who will be accessing the map by its link.
The level of access that anonymous users will have to your CRM data when using a shared map is defined by the User profile that you’re required to select for the map.
Similar to formulas in a shared map’s layer, record sharing rules’ formulas in Profiles used in shared maps also can use URL variables – to elevate access for a subset of CRM data.
Your shared map may have one of multiple filters. A filter may required or optional. The user will be required to select values for all the required filters before any objects will be shown.
A filter is either a list of pre-defined values or an integer number within the defined limits. For a list of values you may indicate whether multiple selection is allowed.
An anonymous user’s selection will be passed as a filter parameter to the data layers’ formulas as right operands.
For a list of values as the right operand, a data layer formula may use contains all or contains any operator to indicate whether all of the selected values must be present in the formula’s left operator or any of them.
If a user leaves an optional filter empty, conditions referencing the filter value in the data layer formula will be evaluate to true.
Values for a filter is defined by a dynamic layer that must also be shared within the map. Objects from a dynamic layer used as a filter are not considered data and will not be shown on the shared map.
A filter may be may be marked as dependent on another filter (parent-child relationship). This will require a user to select the value from the parent filter, and then from the dependent one. A dependent filter will remain visually disabled until a value for the parent filter is selected; and will update its dataset whenever the value of the parent filter changes.
You may select of the custom-styled map tiles.