Dispatch Console: Google Maps Error

Hi, @Ugo Cannavo 

Do you know if all versions of Alliance are concerned ?
I use the console dispatch in demo environment15.4 SU2 and I don’t have the issue.
Hope it helps.

Regards

anthony

on our side we have changed the following code “var googleMapsVersion”  from 3.46 to 3.47 in initialization.js of the Map foder to avoid this error. Waiitng for the official fix

Hi @Ugo Cannavo, 

@Phil Seifert created a post regarding this a few months back, this might have the information you need.

Alliance Google Maps not functioning (17-Feb 2022) | IFS Community

What is status for resolution? We have extrem tight SLA. 

In November 2022, Google is planning to release a new version of the Google Maps JavaScript API. This change will automatically remove the latest Google API version that supports maps in Alliance.

This change means that Google Maps in the Astea Browser will stop working in the Dispatch Console module and also in modules that use the “find address” functionality, such as Customers and Employees.

To accommodate the Google changes, R&D has developed a new maps solution.

The solution was released in the latest maintenance release for these versions:

▪ V14 (HF27)

▪ V15.1 (HF12)

▪ V15.3 (HF5)

▪ V15.4 (SU2)

As part of the solution, the old WEB API control has been replaced by the new one that does not use IE.

All customers that use Alliance maps must install the latest maintenance releases for their versions.

November is over two months away. I have HF12, and it will take 3-4 weeks to test before I would even consider installing in production. Plus the know bug with the Dispatch Console included in the release.

Important message for all On-Premise Alliance Customers:

To cover this Google change IFS R&D developed a new Maps solution that was released in the latest maintenance releases for the following versions: V14 (HF27) , V15.1 (HF12), V15.3 (HF5)and V15.4 (SU2). As part of this solution the old WEB API control was replaced by the new one that does not use Internet Explorer. All customers using maps have to install the latest maintenance releases for their versions.

Work around is below for customers who experience issue but this will no longer work in November

1. On the web/applicaton servers open the file \website\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\initialization.js
2. remove the read only from the file
3. change the GoogleMapVersion to 3.47

function LoadGoogleMainScript() {

    try {

        $('#destination').hide();

        var MapBaseURL = window.external.getMapBaseURL();

        var key = window.external.GetMapKey();

        if (MapBaseURL == null || MapBaseURL == undefined || MapBaseURL == "" ||

            key == null || key == undefined || key == "") {

            window.external.MapErrorHandler("1071", "");

            return;

        }

        var googleMapsVersion = "3.47";

        var libreries = "&sensor=false&libraries=geometry,places";

        var MapURL = MapBaseURL + "js?v=" + googleMapsVersion + "&key=" + key + libreries;

    4. clear cache (on all user clients)

     5. Open Dispatch Console map

Important message for all Alliance Customers that use “maps” in modules other than Dispatch Console. It is the same change that was done in February, whereas the Maps API version was changed to 3.46. Now it needs to be changed to 3.47.

Below are the changes for customers working on V14 and V15 that include changes in the DC and also in other modules:

Dispatch Console Maps
 
website\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\initialization.js
 
Change function LoadGoogleMainScript()
 
var googleMapsVersion = "3.47";
 
Address Finder Maps
 
\website\form_asp\google_address_finder.htm
 
Change function LoadGoogleMainScript (comment first line with // and paste other three lines below this line)
 
//script.src = m_googleApiUrl + "js?&key=" + m_apiKey + "&libraries=places&callback=initMap";
 
var googleMapsVersion = "3.47";
 
var libreries = "&libraries=places&callback=initMap";
 
script.src = m_googleApiUrl + "js?v=" + googleMapsVersion + "&key=" + m_apiKey + libreries

For customers that work on versions below V14 the following are instructions:

Address Finder Maps

\website\form_asp\google_address_finder.html:  

function loadGoogleMainScript() { 

            setFieldText();

            parseRequestArguments(window.location.search.substring(1));

            if (m_apiKey === "") return;

            var script = document.createElement('script');

            //script.src = m_googleApiUrl + "js?&key=" + m_apiKey + "&libraries=places&callback=initMap";
var googleMapsVersion = "3.47";
 
var libreries = "&libraries=places&callback=initMap";
 
script.src = m_googleApiUrl + "js?v=" + googleMapsVersion + "&key=" + m_apiKey + libreries

            document.body.appendChild(script);
        }

Dispatch Console Maps

\WebSite\Maps\GoogleMaps\MainMap\GoogleMap.htm

  function LoadGoogleMainScript() { 
                try {
                    $('#swapDiv').hide();
                    $('#textDiv2').hide();

                    var MapBaseURL = window.external.getMapBaseURL();
                    var key = window.external.GetMapSignKey();
                    if (MapBaseURL == null || MapBaseURL == undefined || MapBaseURL == "" ||
                        key == null || key == undefined || key == "") {
                        window.external.MapErrorHandler("1071", "");
                        return;
                    }

                    var googleMapsVersion = "3.47";

                    var libreries = "&libraries=geometry,places";
                    var MapURL = MapBaseURL + "js?v=" + googleMapsVersion + "&key=" + key + libreries;

                    //check if the Google URL is accessible
                    var IsUrlValid = window.external.CheckMapConnectivity(MapURL);
                    if (IsUrlValid != "true") {
                        window.external.MapErrorHandler("1086", IsUrlValid);
                        return;
                    }

                    updateUStats(RequestTypes.DynamicMapLoad, "OK");
                    BuildGoogleMainScript(MapURL, 'LoadGoogleScripts');
                }
                catch (err) {
                    window.external.MapErrorHandler("1086", ErrLoadGoogleMainScript);
                }
            }
 

Thanks for the update

Are the symptoms of this problem the same ones that we could expect to see in November if we do not or cannot install the latest patches? (Currently on v11.5 and weighing our options. Upgrading by November is not one of them.)

Hi Kathy,

Yes, same symptoms will occur in November if you cannot upgrade.  Currently maps API version number 3.47 is accepted by Google.  This specific instance was when they stopped accepting 3.46.  In November, they will no longer accept 3.47 so it should be the same issue.

Phil, just so I’m clear going back to my user team, Suggest SA will still offer recommendations, but the map will not be shown. Is that correct? The potential loss of Suggest SA functionality is a major issue for our dispatch team.

Hi Kathy,

I have this response from R&D:

v3.47 is the last version of Maps JavaScript API that still supports Internet Explorer. According to Google, it will be removed in November. As soon as this happens, customers that don’t have the latest releases with the new Maps solution won’t see any information on maps. This is the only thing that is affected. All other Google features will continue working.

Hi @Luis Aguero 

Do we have a solution for customers in 15.2 ? (I didn’t see this release in the list)

Regards

anthony 

Hi Anthony,,

Unfortunately, no. Version 15.2 had support stopped and was really only an interim temporary version on the way to v15.3.

I had another customer who was using v15.2 who we only restored that functionality for them after they upgraded to v15.4 SU2 (and since also upgraded to SU4) plus another one who is now upgrading from SU1 to SU4 and did not have maps in SU1 until this upgrade.

Hi @Phil Seifert 

Ok thanks for your explanation. 👍

To be sure, could you confirm that without the fix a customer couldn’t validate an address for a customer site in the transaction “Customer Center”  ?
The impact on the fix concerns not only the usage of maps in the console dispatch but also the feature of geocoding addresses (employee, warehouse, customsier site, etc..) ?

Thanks for your help.

Regards

anthony

Hi Anthony,

I tested this on a vanilla 15.2 environment and it seems address geocoding is still possible.

Example, customer center - address validation shows a result:

Change the address to a different one in another country for the search criteria - also returned the correct result.

Hi Phil @Phil Seifert 

Thanks you very much for your test. Very Useful 👌

anthony