Geopointe June 2016 Release

Last Updated June 19, 2016 11:30am (us pacific)
(release notes will be regularly updated as the actual release approaches)

Geopointe's June 2016 release is scheduled to be generally available on AppExchange Thursday, June 30 , 2016. This page contains the most important details regarding the release and will be updated as the release progresses.

Release Schedule

The Geopointe release process begins with an upgrade of all Sandbox systems. Shortly thereafter, we update the AppExchange listing making the new release available. This allows admins the opportunity to upgrade their systems during their own work hours. A release webinar occurs at that time to provide a preview of the release and to allow for questions. Finally, all remaining Geopointe production systems are automatically upgraded on a weekend. The table below provides the schedule for this release.
Name Description Date
Sandbox All Geopointe installs in Sandboxes will be automatically updated 6/25/2016
Manual Update The release will be available on AppExchange to allow you to manually update your production system 6/30/2016
Automatic Update All Geopointe installs in production systems will receive the update automatically 7/9/2016

Release Webinar

A recorded version of the release webinar demonstrating the new features is now available.  Click here to watch the recording and access the webinar slide deck.

Feature Summary and User Impact

Feature Automatically visible to all users Not automatically visible, requires admin setup Contact Us to enable this feature
Geopointe in the Browser
One-Click Search X    
Easy Data Set Refresh X    
Unified Folders X    
Recent Items X    
Private KML Layers X    
KML for Everyone X    
Saved Demographic Layers X    
Data Set Field Configuration X    
Cross Object Filter Logic X    
Route Stop Notes X    
Shape Labels X    
Merge Shape X    
Markers + Labels X    
Custom Marker Icons   X  
ID values Rendered like Lookup fields X    
{!User.Field} Merge Fields in Filters X    
Add to Campaign Supports Junction Objects X    
On-Demand Drive Distance in Nearby Searches X    
Geopointe for Salesforce1
Map UI Changes X    
Multiple Data Set Layers X    
Action Icons X    
Route Stop Fields   X  
Route Stop Actions in the List X    
Route Stop Notes X    
Geopointe Platform
"Nearby List" Lightning Component   X  
Map User's Current Location to Create Record Action   X  
Assignment Plans at Scale   X  

Geopointe in the Browser Feature Details

One-Click Search

We are laser focused on user productivity. We spent a lot of time working with users to understand their workflow with Geopointe. It became clear that, for simple and power users alike, the process of getting data onto the map was a bit "clicky". We took that to heart and worked to simplify the way a user puts their data onto the map. This simplification occurred in several ways...

  • We unified the folders to provide access to all of your Saved Layers in one place
  • We removed the dropdown to access Saved Layers and put them front and center for easy access and navigation. 
  • We removed the Search button so that Saved Layers can be added with a single-click by clicking on the layer name
  • We eliminated the "Clear Map on Search" and, in its place, provide the user with granular control on a Data Set by Data Set level. You can now add a 2nd instance of a Data Set with a click or refresh the Data Set using the refresh icon
  • Saved Layers can be added to the map in parallel

To edit an item, use the menu icon.

Clicking on multiple Saved Layers at the same time will load them all in parallel. No longer is the page locked up waiting for a layer to load.

^ Return to Feature Summary ^

Easy Data Set Refresh

When you have a single instance of a Data Set on the map, you have the ability to add a 2nd instance of that data set with a new search or replacing (refreshing) the existing data set on the map.

When you have one instance of a Data Set plotted on the map, you will see the refresh icon next to the Data Set name in the Saved Layers list. 

  • Clicking on the Refresh icon will replace the Data Set currently on the map with the results of your next search.
  • Clicking on the Data Set Name will add a 2nd instance of the Data Set onto the map.
This approach gives the user ultimate flexibility in how they'd like to work with their data.

Once you have added data to the map, you can manage the Layers in the Layer Manager.

^ Return to Feature Summary ^

Unified Folders

All mappable items are now unified into a single set of folders. Prior to this release Data Sets, Shapes and KML Layers were all accessed from different places on the page. Now, all of these items can be found in a single place, being distinguished by the icon designating the type of mappable item it is.

Adding a new Map Item is easy. Simply click the green + icon and choose the type from the panel that pops up. The UI will walk you through the rest of the process after selecting an layer type.

How will all of the Saved Layers be brought together?
We know that many customers already have folders setup for their Data Sets and Shapes and had Sharing Rules setup for their KML Layers. With the new release, we will be migrating everything into one folder hierarchy. The following explains how the migration will take place in the new release.

Data Set Folders
Your Data Set Folders will be unchanged. The only difference is that they will now be able to contain any type of map item. 

Shape Folders

Your Shape Folders will move to be within this structure. We will not be consolidating Shape and Data Set folders for you. Your Shape Folders will merely be available in the main folder list and will maintain their sharing settings. Your Geopointe Admin, or someone with read/write access to folders, can easily move Saved Layers between folders to clean things up. For example, suppose you had a Data Set folder called "Marketing" and a separate Shape folder also called "Marketing". On day 1 of this release, the screenshot above would show 2 separate "Marketing" folders, one containing Data Sets and another containing Shapes. It would be up to your Geopointe Admin(s) to rename the folders and/or move layers into a consolidated folder. 

KML Layers 
KML Layers previously supported Sharing Rules at the file level. With the new release KML Layer security will be driven by the folder that contains them. When the new release is installed in your system, your existing KML Layers will be put into a "Unfoldered Saved Layers" section in the Saved Layer list. At this point, your end users will have the same level of access to the KML Layers as they did prior to this release. 

Geopointe Admins will see a link above the Saved Layers list giving them a tool to move KML Layers into folders. This tool will analyze the current sharing settings on your existing KML Layers and offer to create you a folder for each unique set of sharing permissions. This tool is especially helpful if you have many KML files with many variations of sharing rules configured. If you do not have a large set of KML Layers or all if all KML Layers have the same sharing rules, it may be just as easy for your Geopointe Admin to manually move them into the folder structure rather than use the migration page. 

Once all KML Layers are moved into folders, the messages to Admins will go away.

^ Return to Feature Summary ^

Recent Items

The Saved Layers panel now displays your 5 most recent Saved Layers used listed in the order of most recent usage. You can switch between viewing all Saved Layers or just your Recent ones.

^ Return to Feature Summary ^

Private KML Layers

Geopointe now supports uploading KML files for access by your users. No longer are you required to host publicly accessible files, but we do still support that model. KML Layers can now be stored in a secure, non-public location. When creating a KML Layer, the user is given the option to upload a file or use a public URL instead. Prior to this release, only the public URL was supported. 

File uploads only support KML & KMZ file types. These files are uploaded to Geopointe servers for hosting because Google still requires visibility to the files when rendering them onto the map. In order to secure this information, we have done a several things.

  • A unique key is generated inside your Salesforce system for every file that gets uploaded. This key is used, along with some other information, to encrypt the file on our servers. "Encryption at Rest" is the term to use with your security team if they are asking you questions about this. This ensures that the data is unreadable by anyone on the Geopointe team. The file can only be unencrypted using the key in your Salesforce system in conjunction with the Geopointe software.
  • Google's servers still do need access to the file at the time of rendering the KML layer for a user. To accommodate this, we built an API for Google's servers to have special access to the unencrypted version of the file when the Geopointe software requests it. This access is for a very short period of time while it needs to be rendered onto the user's map (no more than a few seconds of access). Google does not have access to the files without Geopointe involved. Accessing an unencrypted version of the file requires the combination of Geopointe making the request, your Salesforce system to provide the keys and Google Maps all working in concert with one another.
NOTE: Due to how the security of these files is implemented, KML Layer records transferred from your Production system to a Sandbox via a Sandbox Refresh process will not be able to load on the map in the Sandbox. In order for them to work in the Sandbox, the files will need to be uploaded again from within that Sandbox system.

^ Return to Feature Summary ^

KML for Everyone

Geopointe now allows any user to upload and save KML/KMZ files, not just Admins.  The ability to do so has moved from the Geopointe Setup page to the Map page.  Each KML Layer is stored in a folder and is accessible just like any other Map Item. The folder's security settings dictate how that KML file can be accessed by Geopointe users.  When creating a KML Layer, a user has the option of uploading a file or supplying a URL.

Uploading a file will encrypt the file and upload it to Geopointe servers for later use. The URL option works just as it did before and requires the URL to be accessible by Google's servers. 

^ Return to Feature Summary ^

Saved Demographic Layers

The Demographics feature within Geopointe has moved and is improved. Rather than being a panel within the Layer Manager, users can now add a Demographics Layer to the map and save that Demographics Layer configuration for future use. They save into a folder just like everything else.
After choosing to create a Demographics Layer, you can now edit the configuration in the side panel and save it into a folder. You can, optionally, save the Layer configuration for future use.

Demographics Layers are placed into Folders just like your other Saved Layers.

^ Return to Feature Summary ^

Data Set Field Configuration

Data Set field configuration is now displayed in a list that allows you to...

  • Drag/Drop the fields to set their sequence
  • Show/Hide a field from the Info Window on a Map Marker
  • Show/Hide a field from the Data Table

Because of the flexibility in the new design, we have removed the old feature that had you specify how many fields to display in the Data Table.

^ Return to Feature Summary ^

Cross Object Filter Logic

Cross Object filters now allow you to add filter logic within them. This allows for extreme granularity filtering on cross-object relationships. For example, the image below is a filter against Accounts. It says to only include Accounts that have Opportunities associated with them, but only if those Opportunities are Open, in a specific Forecast Category and have a Close Date in the past or in the next 60 days. 

^ Return to Feature Summary ^

Route Stop Notes

Users can now add notes to their Route Stops. A simple, yet powerful feature. A Route Stop can be edited using the pencil icon and a Note can be entered. After the Route is saved, this note will appear on the Map page, Route PDF and also on the Route List in Salesforce1

^ Return to Feature Summary ^

Shape Labels

You can now add labels to your Shape layers. When editing any shape, the option to display labels is present. When selected, Geopointe will place a label in the center of each shape on the map. we will place the shape in the geographic center of that boundaries. If you decide to merge your shapes, we will label the merged shape using the shape layer name.

^ Return to Feature Summary ^

Merge Shapes (remove inner boundaries)

When working with Geopointe Shape Library shape layers, users can choose to "merge" the component shapes together. This process removes the inner borders from the shape. This can simplify your map experience considerably, especially when working with shape layers with lots of little component shapes (e.g. postal codes).

Unmerged Shape Layer

Merged Shape Layer

^ Return to Feature Summary ^

Markers & Labels

Geopointe now supports using Labels as your map markers or having a label alongside your map marker. Several usage options exist...

Static Marker + Label
Static Markers now support the ability to bring a Label along with it. A static marker is when all map markers look the same for a data set. Adding a label allows you to differentiate the records on the map without opening each one. 

In the above example, the Account Name is being used as a label along with a yellow/green marker. The result on the map is below. At a glance, I can see the Account Names being mapped.

Label Only
You do not have to use an icon for the marker. It's now possible to have a Label Only type of marker.

See the same information as above, but only using a Label, no pin. The labels are clickable to open up the record's info window.

Color By + Label
Geopointe's Color By still works great with Labels. Use pin color to differentiate by a grouping field and then use a label to help you identify pins off a different attribute. 

In this example, the Account Name is being used as a label along with a Color By marker rules using the Rating field. The result on the map is below. At a glance, I can see the Account Names being mapped and identify their rating using the legend.


^ Return to Feature Summary ^

Custom Marker Icons

Geopointe now allows you to upload custom image files to act as map marker icons. A folder (in the Salesforce Documents tab) called "Geopointe Markers" is included in your Geopointe install. Adding image files to this folder, and checking the Externally Available Image field on the document record, will allow that image to be chosen when setting up your map marker configurations. When configuring your markers in a Data Set, we will display your custom icons ahead of the set we provide for you.

These icons will then be used as map pins on the map.

Please note that Geopointe will auto-size your image files to the standard map marker size. It is recommended you use square images that are a little bit larger than the map marker icons. This will allow for proper scaling across various screen sizes.

^ Return to Feature Summary ^

ID values Rendered like Lookup fields

When a Lookup or Master-Detail relationship field is selected in the Data Set Fields list, it's results will be displayed as a link displaying the name of the referenced record. Prior to this release, it displayed the ID value stored on the main object. For example, suppose you wanted to display the Owner of an Account in your Data Set. 

When displayed on the map and data table, the field will carry the label of the Owner field on Accounts and the value will be displayed as a link showing the Owner's Name. The link is clickable to view the corresponding record in Salesforce.

NOTE: If you would like to display the real ID value instead of a link, this is still available. Instead of choosing the Reference field on the main object, you will want to use the joined ID field from the related object. See the image below for how we are getting the ID from the Owner record.

^ Return to Feature Summary ^

{!User.Field} Merge Fields in Filters

You can now utilize any value from the Current User's record in your filters. Doing this can greatly simplify your Data Set setup allowing you to create one data set that is reusable by many users. For example, this would allow you to create a single Account Data Set filtering for Current User being the Manager of the Account Owner.

The link will open a list of User fields available. After selecting one, the merge value (e.g. "{!User.Id}") will be added to your filter criteria.

^ Return to Feature Summary ^

Add to Campaign Supports Junction Objects

Geopointe's Add to Campaign feature has been enhanced to allow for the recognition objects that are junction objects between the object you are mapping and leads or contacts. Add to Campaign has always been quite intelligent in that it allows you to use Add to Campaign no matter what object you are mapping. Let's say you map Accounts. When launching Add to Campaign, the system will look for...

  • Lookup fields on the Account Object that lookup to Lead or Contact (LOOKUP). For example, suppose you have a field on your Accounts called "Billing Contact" that identifies 1 contact as having that role. This Contact can be included in your Campaign via that relationship.
  • Lookup fields on Lead or Contact that lookup to Accounts (CHILD). For example, Salesforce has a built-in lookup relationship on Contacts that link an Account to them. This relationship can be used to add Contacts to a Campaign when mapping Accounts. 
  • Child Objects to Accounts that have a relationship to Lead or Contact (JUNCTION). This is the new one! For example, suppose you were mapping a custom object you have called "Meetings" and that object has an "Attendees" object related to it that links all the Contacts that attended the meeting. You could use this relationship when mapping your meetings to include all Contact attendees from that meeting into a Campaign.
The JUNCTION option is the new one with this release. When I map Accounts in an org that has a Junction object between Accounts and Contacts, below is what I see as my options to help build my lead/contact list.

^ Return to Feature Summary ^

On-Demand Drive Distance in Nearby Searches

Prior to this release, drive distance calculations were automatically performed and displayed for every Nearby search. Beginning with this release, this calculation will require an additional click rather than happening automatically.  This change is due to a shift in Google's licensing and the fact that many users did not use this information.

^ Return to Feature Summary ^

Geopointe for Salesforce1 Feature Details

Map UI Changes

The Salesforce1 map UI has been cleaned up a bit to modernize it and also better accommodate the new functionality being introduced in this release.

We have made additional UI improvements in the record detail panels and with Route Stops. Those are discussed in other sections of these release notes.

^ Return to Feature Summary ^


Multiple Data Set Layers

Salesforce1 now supports the ability to map multiple Data Sets at the same time. This would allow different objects (e.g. Leads and Opportunities), as well as variations of the same data (e.g. Customer Accounts and Partner Accounts), to appear together on the map. Each Data Set search will be added as a separate layer in the Layer Manager. Multiple instances of the same Data Set are not supported. If map the same Data Set a 2nd time, the Data Set will be replaced on the map.

Opening the Layer Manager will list the different mapped layers. 

Tapping on a Layer will expand it and display a list of records from that Data Set.

^ Return to Feature Summary ^

Action Icons

When viewing an individual item (record, route stop, place, current location, custom address) in Salesforce1, you have Actions that can be performed. Prior to this release, we displayed a button for each action. With the new release, these actions cleaned up visually and utilize a icon to help distinguish them. In certain cases, Geopointe has standard actions that always appear (e.g. View Record). Those standard actions always appear first. Any custom actions will appear after.

If you have more than 5 Actions, the 5th spot will be replaced with a Show More option allowing you to access the rest of the Actions. Please note that you can sequence your Actions in Geopointe Setup.

^ Return to Feature Summary ^

Route Stop Fields

When items are added to a Route Stop, you can have Data Set fields brought along for the ride. This feature needs to be enabled by a Geopointe Administrator on the Geopointe Setup page.  Edit the Org Settings and set the "Number of Route Fields to Display" field to the number of Data Set fields you would like included on your Route Stops.  

Geopointe Setup

When viewing that Route in Salesforce1, those field values will be available to you when expanding a Route Stop in the list or viewing is on the map.

On the Map

Route List


^ Return to Feature Summary ^

Route Stop Actions In Route List

Route Stop actions were previously only available when viewing the route stop details on the map. With this new release of Geopointe, we have included the Route Stop actions within the Route List as well.

^ Return to Feature Summary ^

Route Stop Notes

Users can now add notes to their Route Stops and these also appear in Salesforce1.

^ Return to Feature Summary ^

Geopointe Platform Feature Details

"Nearest Records" Lightning Component

A new Lightning Component comes packaged with Geopointe in this release. The component can be placed on any Lightning Page and provides a list of the nearby records, based upon a Geopointe Data Set. Because of the relationship to Geopointe Data Sets, the use cases are endless. For example, use the new Lightning Component to provide...

  • Nearest Referenceable Customers
  • Nearest Service Center
  • Nearest Fellow Attendees to an Event
  • More!

The Component is intended to be a quick answer for an end user. 

It can be placed onto a Lightning Page multiple times (each with a unique configuration) and supports both the narrow and wide columns.

Configuring the component is simple. In the App Builder, simply use the "Geopointe: Nearby List" component and set the properties (the Data Set ID value to use is obtained when editing the Data Set on the Map page). Notice how App Builder supports multiple instances of the component. In the example below, I've setup a Nearest Customers and a Nearest Partners component. I chose a wide search area (500 miles) because my goal is to show the nearest 3 records no matter how far they are. The Component can be placed in the wide or narrow columns of a Lightning Page. 

^ Return to Feature Summary ^

Map User's Current Location into a Create Record Action

When configuring a Create Record action (one that lets you create records from the Map), you can now map the user's current location into fields on record being created. This feature can enable features you'd like to implement such as...

  • A Custom Check-In process
  • Documenting the location of your record while on site
  • Documenting the location of your users for audit purposes. This would be a great piece of information in Field Service scenarios where you are documenting activities performed while onsite. This information can confirm the fact that the user was there.
  • Capturing the user's location when dispositioning a record in a door-to-door scenario
  • More!

^ Return to Feature Summary ^

Assignment Plans at Scale

Geopointe's Assignment Plan functionality allows you to automatically determine and update your Salesforce system with information about how a record fits into custom areas you've defined.  There are so many reasons businesses need to segment their data into areas: service territories, sales territories, marketing areas, time zones, etc.  Sometimes a user needs to map and search your data against these areas, but other times, you'd rather it be automatically done for you.  Imagine Service Incidents coming into your Salesforce system and having Geopointe automatically designate each one to a Service Area automatically, without anyone looking at a map. That's Assignment Plans.

This release scales up the power and performance of Assignment Plans by:

  • Supports territories with 4000 shapes (e.g. an Area comprised of 4000 zip codes), an 800% increase!
    Brazil Zips
  • Over 7x increase in performance (time to process an Assignment Plan)
  • Assignment Plan scheduler runs all plans each time it fires
    Previously, when the Assignment Plan Master Schedule class would execute, it only ran a single assignment plan.  Now, when it executes, all active plans will be processed (in series).
  • On-demand assignment capability
    This advanced feature allow you to assign records to territories in near real time.  Your custom Apex code can use Geopointe's API Apex class to assign records on demand.  Additionally, you can also specify a callback function for our code to call when the assignments have finished processing.  This feature can supercharge your automated processes for powerful, fast results!

^ Return to Feature Summary ^

We hope you enjoy what we have delivered in this release! Remember, we are always looking for new ideas.