Switch the Mobile App to the Native API Integration
Introduced in 8.7
Starting with version 2.0, Alloy Navigator Mobile App no longer needs the Mobile App Service (formerly, "the Mobile Portal") as a backend. Instead, it uses the native API integration, which significantly improves the application performance.
As soon as your technicians update their Mobile App to version 2.0, the app will prompt them to update the application URL, warning that the existing address is being deprecated. Starting with version 8.7, we are retiring the Mobile App Service and replacing it with the API module. However, technicians will still be able to use the "deprecated" URL until you are ready to install the API module.
When you are ready to switch the Mobile App to the native API integration, take these steps.
Install the latest version of the API module and configure it for Access Token authentication.
INFO: For instructions, see Installing and Configuring the API Module
If you already have the API module of a previous version, upgrade it to the latest version.
IMPORTANT: The API must be configured for Access Token authentication.
In your Web Configuration tool, view the API URL. The URL is displayed in the main pane on the right-hand side, among other configuration information.
This is the new URL that Mobile App users should use to sign in to Alloy Navigator now.
Give the new URL to all technicians and ask them to update the application URL in their Mobile App.
When all technicians update the application URL, you can uninstall the Mobile App Service from your IIS server. You will not need it anymore.