...
- Microsoft announced on May 24, 2024, that they are deprecating Bing Maps. Customers using Bing Maps for Enterprise Basic or Free license will no longer be able to use Bing Maps for Enterprise services beyond June 30, 2025. To continue using Mapping in MobileTech, you will need to obtain a Google Maps API key at https://cloud.google.com/maps-platform/pricing/. (You will need an API key that includes Maps and Routes. You do not need Places.) See Enter the Google Maps API Key.
- As App Stores increase their security requirements, HTTPS (with Trusted SSL Certificates) will soon become required across all device types. Therefore, we recommend you transition your MobileTech environment to use SSL with a trusted certificate.
- Do not install MobileTech server components on your SQL Server machine.
- Install MobileTech Administration on the MobileTech web server.
- Verify the eTimeTrack Web Service current release version matches the installed version of Signature. For installation instructions for each component, see the Installation & Administration Guide.
- If your technicians need WiFi, and your company typically turns it off overnight and on weekends, you might want to reconsider this practice to ensure they have the necessary access.
| Excerpt | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CompatibilityTo find a complete list of system requirements across all the Signature modules, refer to the System Requirements documentation. This table lists the tested and supported compatible versions for MobileTech
Incompatibility
Obtain a Google Maps API KeyTo use the Mapping feature on any device, you will need to obtain a Google Maps API key at https://cloud.google.com/maps-platform/pricing/. You will need the Maps JavaScript API (Maps > Dynamic Maps) and Geocoding (Places tab). Geocoding is required for setting coordinates. See Enter the Google Maps API Key.
|
...
Bug Fixes
10.0.63 - November 2024
| Case # | Fixed Issue |
|---|---|
| MT-1944, MT-1945 | Service call and location attachments are now sending metadata. |
| MT-1964 | Users will no longer receive the “No data found to generate report” error message when attempting to run the Timesheet Report. This occurred when the technician was in a different time zone than the server. |
10.0.60 - October 2024
| Case # | Fixed Issue |
|---|---|
| MT-1181 | Android users will now see the Entry Type field as expected when entering time entries. |
| MT-1198 | When adding an administrator in MobileTech Admin, we are now checking to see if the email address already exists. |
| MT-1206 | You can now add an icon on an inspection template. |
| MT-1340 | The Legacy JSA and Summary reports are now created as expected when there are more than three appointments. |
| MT-1379 | Job reports are now saved as expected to the correct job appointment attachment location. |
| MT-1410 | We've improved the fetch request performance to be more efficient for users who have many tasks on several pieces of equipment and are attempting to add equipment to the Appointment Completion form. |
| MT-1544 | We've fixed an issue where some users report receiving the error message "Check Report Signatures Error: Missing Summary Report" when completing an appointment. |
| MT-1651 | Notes at the job level are no longer duplicated in the notes list. |
| MT-1685 | The sync logic was updated so that null values are not created in the Branch field of the Technician Team Branch table. When a lookup refresh is performed, data that has null references are removed. |
| MT-1757 | Technicians can now update their password from their device. |
| MT-1769 | Users will no longer receive an error message when creating a task response. |
| MT-1776 | The Field Invoicing preview is now working as expected. |
...