Geopointe June 2015 Release
Last Updated June 2, 2015
Geopointe's June 2015 release is scheduled to be generally available on AppExchange Tuesday, June 16, 2015. This page contains the most important details regarding the release and will be updated as the release progresses.
Release ScheduleThe Geopointe release process occurs over the course of two weeks. It begins with an upgrade of all Sandbox systems. Roughly one week later, 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 Geopointe production systems are automatically upgraded on the following weekend if they have not already been. The table below provides the schedule for this release.
|Sandbox||All Geopointe installs in Sandboxes will be automatically updated||6/6/2015|
|Manual Update||The release will be available on AppExchange to allow you to manually update your production system.||6/16/2015|
|Automatic Update||All Geopointe installs in production systems will receive the update automatically||6/20/2015|
Watch a recording of our release webinar for more detail and a demonstration of some of the new features in detail.
|Feature||Automatically visible to all users||Not automatically visible, requires some setup||Contact Arrowpointe to enable this feature|
|Removal of Geocode Offset||X|
|Static Map Deprecation||X|
|Geopointe in the Browser|
|Interactive In App Help||X|
|Assignment Plans at Scale||X|
|Improved Analytics Uploading||X|
|Geopointe for Salesforce1|
|Check In & Checkout Direct from Mapped Result||X|
Beginning with the June release, Geopointe will use Google as its geocode provider. All future geocode requests will result in Google geocode data. Google is the best in the geocoding business in terms of depth and accuracy and has incredible global coverage. Google geocoding should result in much more precise map pin placement, especially for our customers outside the US and Canada. We are very excited about the move and know our customers will be too.
For customers that utilize the additional data stored on the Geocode record that Geopointe manages, please note that a few things will be changing due to using Google.
- Geocode Quality values now come from Google. Customers were used to seeing values such as ADDRESS, POINT, CITY, ZIP when we had MapQuest geocoding. Google has a similar notion, but different values. Values from Google (in order of accuracy) are: ROOFTOP, RANGE_INTERPOLATED, GEOMETRIC_CENTER and APPROXIMATE. In situations where Google cannot figure out an address' location, a geocode record will not be created.
- Latitude and Longitude fields are no longer offset. There is more information on that in the next section of the release notes.
- No information will be provided for Geocode Quality Code.
- No information will be provided for Side of Street
- No information will be provided for Link ID
- County (clean) will continue to be populated, but the full value is different from that at MapQuest. MapQuest would have a county for Chicago simply say "Cook" where as the Google response will say "Cook County".
Now that we are utilizing Google geocoding, this offset is no longer necessary in our licensing and the latitude/longitude fields on the Geocode record will now hold the proper latitude/longitude values.
Static Maps are the non-interactive maps that we allowed you to embed in your Page Layouts. They were merely a PNG image of a record's location. Geopointe utilized these in embedded Visualforce pages that could be added to Page Layouts. We also provided a Visualforce Component developers could use to customize their own Static Maps.
The June release of Geopointe is deprecating the Static Map component. This is primarily a byproduct of moving to Google geocoding and the licensing around Static Maps. This is also due to Salesforce now providing basic mapping functions on standard address fields and custom maps in Visualforce.
All of the "embedded map" pages packaged in Geopointe will have their map replaced with an image indicating they are deprecated. Admins should remove these embedded pages from their Page Layouts. Fundamental Geopointe functionality is not impacted by this. We will continue to provide static map images in our Route PDFs, Check In chatter feed posts and select upcoming Geopointe features.
We are aware that some customers are using the Static Map component in their own development. We are in the process of identifying those customers and whitelisting their current use of the static maps, but will prohibit new use of the static maps. If you are one of those customers, we will be reaching out to you. If you'd like to help us out, you could log a case with us and let us know how and where you are using the component. We would still recommend our customers replace our Static Map and use the basic apex:map component now available in Visualforce for those pages.
^ Return to Feature Summary ^
We are extremely happy to announce that Geopointe will support four (4) new languages in our June release. The languages Geopointe now supports are:
- English (this is the default language for the application)
- Portuguese (Brazil)
Our Map page (both for the desktop and in Salesforce1) will be fully translated. Any user with a language listed above as their Salesforce language setting will have Geopointe loaded in that language. For users with any other language settings, English will be used as it had been prior to the June release. Our plan, over the next couple releases, is to support every language that Salesforce supports.
Please note that the Geopointe setup pages and our Help Site are not being translated at this time. The focus is on the map page itself.
The new Help feature is available behind the question mark icon in the top right of the map. Every user also has a set of Getting Started tasks to accomplish.
^ Return to Feature Summary ^
We released our Assignment Plans feature with our March release and have seen many customers take advantage of what it has to offer. Feedback has been very positive. At that time, we had to impose limitations as to the number of sub-shapes that could be included in an assignment area (100) and how many records could be included in each shape (10,000).
The June release has improved this. An individual assignment area can now include up to 500 sub-shapes. We also eliminated the limit as to how many records can be included in an assignment area. We will continue to work to improve limits, but the 500 sub-shape limit available with this release has supported all of the use cases that we have encountered thus far.
We rewrote the process to upload Analytics data sets to take full advantage of SpatialKey's new API version. This has results in faster uploads and the elimination of several errors that would occur due to anomalies in the source data.
We made it possible to check in/out right from the mapped results in Salesforce1 rather than requiring a user to navigate to the record in Salesforce to then use a publisher action. Organization can simply create a new Record Action in Geopointe setup that points to our Check In page and passes in a URL parameter sf1=true.
We hope you enjoy what we have delivered in this release.