Mapsly Automation Platform

When a user clicks a custom button, their current location is available for use in actions. Using this feature, you can, for example, implement custom check-in/check-out processes.

A button can be added to the map right-click menu. When such a button is pressed, the right-clicked map location is also available for use in actions that follow.

Using Mapsly’s form builder, you can create various forms and use them to gather data from users before executing actions. Inside a form, you may add nested actions that will be executed when a button is clicked or a picklist’s current value changes.

Apart from any of the actions listed above, form event handlers can show/hide other form fields or change their content and currently selected items, so you can implement dynamic forms that change their appearance and content in real time in response to user actions.

In particular, Mapsly’s check-in/check-out feature is built entirely with the Automation Platform.

In Mapsly, you can easily calculate both direct and driving distance, as well as driving time between any locations, and use them in your automation or saved to records.

For example, for every new lead Mapsly can automatically calculate a quote for delivery to the lead from the best warehouse based on the driving distance for every warehouse in the area and their cost-per-mile.

A button can be placed into context menus for an object, like Account, so when the button is clicked, the fields of this object are available for use in the forms and actions that follow.

You may also place a button into the Table view for an object and make it available when multiple records are selected at once. When such a button is pressed, selected records, or all records in the table, become available for use in actions and forms.

When executing actions for multiple records at once, like when:

• A Create contact list button is clicked in the Table view.
• You need to send an email report listing records found with a Match records action.

Use the template engine to construct a single text value out of the record set data.

When necessary, in your templates, you may also:

• Execute other actions and use their results like data fetched from an external API
• Call geo-functions
• Use cycles and conditional logic
• Format date and time or other types of values in the desired format
• Save data to the execution context and re-use it down the execution flow
• Access the user’s current location and right-clicked map address

Actions within a single execution session are working in the same Execution context – a global space of variables – so they can pass one another various data, declare and re-use variables, which can be used to implement more sophisticated scenarios that cannot be addressed by just point-and-click tools.

You can create a territory with custom geometry and data field values using the Automation Platform. For example, it can be a circular territory around each of your accounts, with the radius from the account record representing its service area. You may also use automation to programmatically update the territory’s data fields, geometry, name, and color, as well as remove the territory.

Just like any territories created manually, programmatically created territories can also be automatically assigned to records of any object and can be automatically colorized based on their metric values.