Geopointe December 2015 Release
Last Updated December 7, 2015 10:00am
Geopointe's December 2015 release is scheduled to be generally available on AppExchange Tuesday, December 8 , 2015. This page contains the most important details regarding the release and will be updated as the release progresses.
Release ScheduleThe 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.
|Sandbox||All Geopointe installs in Sandboxes will be automatically updated||12/5/2015|
|Manual Update||The release will be available on AppExchange to allow you to manually update your production system||12/8/2015|
|Automatic Update||All Geopointe installs in production systems will receive the update automatically||12/12/2015|
|Feature||Automatically visible to all users||Not automatically visible, requires some setup||Contact Arrowpointe to enable this feature|
|Geopointe in the Browser|
|2x Query Limit||X|
|3x - 4x Query Performance Improvement||X|
|100 Route Stop Limit
(up from 25)
|New Drawing Controls||X|
|My Direct Reports Filter||X|
|KML Export Includes Shapes||X|
|Heatmap by any Numeric Field||X|
|Geopointe for Salesforce1|
|100 Route Stop Limit
(up from 25)
|Shape Migration Management||X|
The Geopointe query processor has been improved to allow the size of Geopointe's query results to more than double. Prior to this release, a single Geopointe query was limited to 20,000 records returned. The limit has been increased to allow almost 50,000 records per query result. Of course, you can also always layer on multiple queries to see even more data.^ Return to Feature Summary ^
We have significantly improved the Geopointe query result processing to operate more efficiently. As a result, we are seeing 3-4x improvements in performance time per query.^ Return to Feature Summary ^
Marker Clustering has been added to the visual representation of Data Sets. A cluster specific info window is also being delivered to summarize the contents of the cluster. The ability to toggle clustering on/off is available in the Layer Manager on each Data Set. The numbers within a cluster represent the record count in the cluster.
After the upgrade, each user is defaulted with a Auto Cluster Query Size setting of 2,000 records. This means that, for any query less than 2,000 records, the user will still be defaulted to the pins. They could manually change it to clusters in the Layer Manager.
Each user is able to manage their own Auto Cluster Query Size. Some users might like to have clusters default more often, even for smaller queries. The good news is that users can update this preference for themselves in their personal settings, which are available by clicking the gear icon atop the map.
Routing is being given a big boost. We have broken through the Google imposed limit of 25 stops per route request and will now support Routes of up to 100 stops, including optimization!
This new limit is supported in the desktop ("Aloha" & "Lightning") version...
as well as Salesforce1...
The Drawing Controls on the map have been enhanced and made more accessible. When drawing, you now have the option of drawing polygons (same as before) and also circles and squares. Also, the controls to add shapes have been added to the right side of the map along with access to the Geopointe Shape Library we provide.
We have brought the same type of folder organization that are used in Data Sets to Shapes. This means that a Shape is put into a folder and its permissions are driven by how that folder is configured. Folders are created by Geopointe Admins and can be setup to give a specific users access. Administration of that folder can also be delegated to others, so it's not always on the shoulders of the admin to manage folder contents.
Prior to this release, access to shapes was administered on each shape individually. With the new release, access is solely driven by folder. We have several customers that have sophisticated sharing already setup. As part of the release, we are delivering a migration script and a UI to help move you from the old model to the new. Upon getting the new release, a script will run that will automatically mark all un-shared shapes as Personal to the shape's owner. Those shapes will be put into the shape owner's My Personal Shapes folder. For any other remaining shapes, we are providing a Shape Migration screen to help you manage the transition.
All standard (except Accounts) and custom objects will have options similar to the image below...
Because of Account Teams in Salesforce, Accounts provide a few more options (assuming you have Account Teams enabled).
^ Return to Feature Summary ^
When you export a result to a KML file, the shapes you have on your map will also export along with the data.
exports as the KML below viewable in Google Earth and other map apps...
Sometimes a map pin gets put into an undesired location. Perhaps you mapped a location for a very large property and you want the map pin in a different place than Google geocoding put it. Well, you can now correct that location in seconds. Or maybe Google is just wrong and you know exactly where something should go.
A "Correct Location" action is now available as a link inside the info window for a record on the map.
When clicked, all other data will hide and that pin is now draggable.
Drag the pin to where you want it and click the Save Location button in the control panel. This will document the new location for that record and bring back the other map data.
This feature requires you to setup custom latitude and longitude fields onto your data object and then refer to those fields on your Map Object in Geopointe Setup. Geopointe has long had a feature that lets you refer to custom lat/lon fields in order to override the location of a record from its geocoded location. This Geocode Correction feature was added to Geopointe to simplify the process for populating those fields right from the map.
Please note that a user will only be allowed to correct the geocode of a record if they have read-write access to the record and read-write access to those fields in Field Level Security.
Heatmaps are a very popular feature. They allow you to see the concentration of records in a doppler radar fashion. Prior to this release, heatmaps only showed concentrations by record count. With this new release, you can now choose any numeric field from your data set to have the heatmap rendered by that metric.
For example, instead of seeing accounts by record count...
Maybe you want to see them by a different value you keep in your data. Now you can. When choosing the Heat Map option for the layer in the Layer Manager, you will see options to choose other numeric fields from your Data Set.
Please note that doing this may show gaps in places where you have records. Heatmapping is done on a scale. If your data has no value (null) or a very low value relative to the highest values in your data (e.g. many accounts, but only a few with large revenue numbers), the records with low/no value may not appear in the heat map or be very faint. You can see this below where only a portion of the data has a value in the Assets field. When heat mapping, you have the option to redisplay the markers/clusters atop the heatmap so you can see if those gaps are occurring.
^ Return to Feature Summary ^
We are very excited to be moving Shape management to Folders. This is a much more robust solution for organization and security than managing this on a record by record basis. However, whenever you move from one solution to another, you need to help bring people to the new way of doing things. For this, we are delivering things to help.
First, upon installing the new release, a script will run where we'll look at all sharing info on your shapes and, for any that are only shared with the owner of the shape (usually the shape's creator), we'll mark it as a Personal shape and it'll be in that user's My Personal Shapes folder the next time they visit Geopointe. That's pretty straightforward and covers ~90% of the shapes we see out there.
We know that some of our customers have setup specific sharing on shapes that can get complicated and customers would despise having to manually recreate that. For this scenario, we will not touch those shapes in the migration script. They will display below the folders. The sharing you have in place now will work as-is, so users will only see the shapes they have access to now.
In this section, Geopointe Admins will see a link to navigate to the Shape Migration page (available at /apex/geopointe__shapeFolderMigration for you admins out there). This page will, first, make sure the initial migration script successfully ran and then present you with an easy way to create folders and move shapes into those folders while maintaining their sharing settings.
The page will look at the unique groups of sharing rules and allow you to create a folder for each grouping and automatically move the corresponding shapes into the folder you create. This will take into account the groups/roles/users being shared to and whether the sharing is read-only or read-write. We have found that most customers that share shapes are repeating the same sharing rules across every shape. Or, at worst, have 3 or 4 permutations of sharing going on. For these customers, their shapes will be grouped together nicely and the folder creation process should be a breeze.
To create a folder, simpley give it a name and click the Create Folder button. Do this for each grouping.The new folders will get those sharing settings and all the shapes corresponding shapes will be put into that folder. After it's finished, you can see the results on the Map Page and do any cleanup you'd like in the map page.
We hope you enjoy what we have delivered in this release.