TMT Fleet Maintenance V.2025.1.3 Release Notes

This document contains information on the latest version, including:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

PDF version

With the release of V.2024.2, the release note organization has changed. Issues are presented in this order:

  • Enhancement or Resolution

  • Feature set or module

  • Menu path

  • Issue number

To go directly to the section you’re interested in, use the page contents links on the right side of the page.

General information

All information in this section applies to all 2025 releases except where noted.

Warnings

PLEASE READ BEFORE UPGRADING

A security update has been made to TMT Web, and we highly recommend that all customer-hosted On-Premise customers upgrade to 2025.1.3, or the latest patch version for your TMT Web product. If your version is not listed, to ensure you are protected from this vulnerability you must upgrade to a supported version as soon as possible and apply the patch. If you have any questions please contact Trimble Transportation Support.

  • TMT Web Version 2019.4 (2019.4.8.132)

  • TMT Web Version 2022.2 (2022.2.2.525)

  • TMT Web Version 2022.3 (2022.3.6.555)

  • TMT Web Version 2023.1 (2023.1.2.557)

  • TMT Web Version 2023.2 (2023.2.3.821)

  • TMT Web Version 2023.3 (2023.3.3.695)

  • TMT Web Version 2024.1 (2024.1.3.704)

  • TMT Web Version 2024.2 (2024.2.3.1001)

TMT SOAP APIs

A security update has been made to the TMT SOAP APIs, and we highly recommend upgrading to TMT 2024.1 or later.

If you are a TMT and TruckMate client, the aforementioned APIs impact this integration, so please take note of the following:

  • If you plan to upgrade TMT to 2023.3.3 or higher you may upgrade both TMT and TruckMate at the same time, or upgrade TruckMate first, followed by TMT.

  • Please contact TMT support for version compatibility questions.

If you are using TTP on premise, and you chose not to upgrade to V.2022.2 or higher, you can still use the current TTP URL, https://tmt-ttp.trimble-transportation.com

IWS

Interactive Workstation (IWS) will no longer be supported in V.2022.3 or later. For more information, see Changes to TTP.

Client Server

You will not be able to use TMT Client Server (Delphi) if you upgrade to 2020.1 or later. DO NOT upgrade unless you are ready to go to TMT Web Only.

Please note that our 2025.1 release does not include an update to our Client Server (Delphi) product. As announced in October 2019, our 2019.4 release was our final version with enhancements to the Client Server version of the system. Per our October 2019 notice, this release (2025.1) and all future TMT releases will only include updates to the Web version of our software.

The TMT Client Server (Delphi) version of the system cannot be used with the new Web version of TMT (V.2025.1). By taking this upgrade (2025.1) to Web, customers will need to move exclusively to the Web version of TMT only. Do not upgrade your production system until your team is able to make a complete move to TMT Web only.

Prior to beginning this installation, please review the following details. We highly recommend reviewing system hardware requirements as they are different for this new, more advanced release. In addition, we recommend installing the system on a test server and using the resources noted below to prepare your staff to work with our new user interface.

For more information from your Customer Support Team: Click Here

Please contact your Customer Support Representative before you upgrade to 2025.1.

AMSLIC Database: READ BEFORE UPGRADING

TMT Fleet Maintenance/Service Center V.2022.2 and above uses a new, merged database. Before upgrading, you will need to run the "Installer_Migration_Script" to merge your TMWAMS main database with your AMSLIC framework database. Please note that if you are coming from an older Client Server version, you will need to be on at least version 2020.1 before running the merge script. Once the database has been merged, you can proceed with the upgrade as normal.

  • Version 2025.1: Only includes TMT for Web. It does not include TMT for Client Server.

  • Client Server upgrades are no longer included or supported beginning with Version 2020.1. A Client.exe file is no longer included.

  • Hardware Requirements: Make sure you have the correct hardware required to support TMT for Web V.2025.1 before you upgrade. To download the TMT Fleet Maintenance and Client Server Hardware Specifications document, click here.

  • Create a migration plan: Create an SOP, create a training plan, and install V.2025.1 in a test environment.

  • Train your staff: Use the "Free Choice Training Menu" by accessing the TMT Migration eLearning course to become familiar with TMT for Web (requires a login for the Trimble Client Center). We are calling it a "free choice menu" since the topics may be viewed in any order you choose. This is an interactive eLearning course that allows you to progress at your own pace as opposed to a non-interactive video. We hope you find the interactive content useful and engaging!

Telerik Vulnerability

Customers who are on versions of TMT Web prior to 2022.1 may be exposed to a vulnerability documented by one of our third-party software vendors (Telerik). Guidance varies depending on the installed TMT Web version (see below). For information directly from Telerik, please use this link:

https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-allows-javascriptserializer-deserialization

  • 2022.1 through 2025.1
    Uses an upgraded Telerik version that has patched the vulnerability (no changes needed).

  • 2019.4
    A service pack is available which includes patched Telerik DLLs. This can be located under the 2019.4 version downloads.

  • 2019.2
    Remediation possible with web.config changes in this version and higher (2019.2-2021.2.X).

  • Prior to 2019.2:

    • Remediation is not possible with web.config changes. You must upgrade.

    • For Delphi/Web hybrid customers, see 2019.4 section above. For all others, we would suggest you upgrade to the latest version of TMT Web.

Telerik Vulnerability Remediation

Please refer to this link for detailed steps on patching this vulnerability:

https://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security

This involves web.config changes, and it can be done without taking an upgrade. However, we strongly encourage you to upgrade to a later version of TMT Web for the greatest level of mitigation.

Changes to hardware requirements

TMT Web V.2022.1 and later have new SQL Server requirements. You must be using SQL Server 2016 or later to use TMT Web V.2022.1 through V.2025.1.

For SQL Server 2016, the minimum compatibility mode is 130. TMT Web will also support modes 140 and 150.

There are two files from Microsoft that are required for this version:

  • SQL Server 2016 CLR Types

  • SQL Server 2016 Shared Management Objects

Review the latest Hardware Requirements documentation prior to upgrading.

You must download and run both files via the following links before upgrading to TMT Web V.2022.1 or higher:

You must not delete the 2008R2 CLR/SMO SQL Server components from any TMT Web environment when installing or upgrading. The installer is still using these components at this time.

Windows Server and SQL Server upgrades are included in TMT Web software as a service (TMT Web SaaS). For information about upgrading to TMT Web SaaS, contact Dawn Siegel at [email protected]. If you have technical questions, contact TMT Support:

Changes to TTP

  • Trimble will upgrade TTP to V.2025.1 on Sunday, 2/9/2025. Users should clear their cache when logging back in following the update, please refer to the Security Administrator guide for instructions. The production URL will stay the same: https://tmt-ttp.trimble-transportation.com/.

  • If you are a customer that self-hosts the TMT Web Application, and you choose not to upgrade to V.2022.1 or higher, you can still use the same TTP URL as mentioned above.

  • Interactive Workstation (IWS) will no longer be supported in V.2022.3 and later due to the sunsetting of Internet Explorer and Silverlight.

    • If you upgrade to V.2022.3 or later, note that any IWS out of browser shortcuts that have been installed need to be deleted and will not be supported.

    • You can still call our support team for assistance on IWS with V2022.2 or lower, but IWS will no longer be included with TMT V.2022.3 or later. You will still have access to IWS in V.2022.2 if you maintain an existing instance of Silverlight and use Microsoft Edge in IE Compatibility Mode.

If you use Single Sign On (SSO) for TTP and you are on TMT Version 2025.1, please add https://tmt-ttp-25-1.trimble-transportation.com/login in your Azure Portal as a 'Redirect URL'. For more information relating to SSO for TTP, refer to the Security Administrator Guide.

V.2025.1.3 Enhancements

Asset Inspection App

Masters > Employees > Misc

  • TMT-326131

    Implemented a new access permission for an employee: Allow User to view Asset Inspection App Unit History and Work Pending. The setting is on the MISC tab of the Employees Master page.

    When the field is set to:

    • NO

      The employee cannot see the unit history, list of next service due, or open tickets for a unit in the Asset Inspection App.

    • YES (default)

      The employee can see the unit history, list of next service due, or open tickets for a unit in the Asset Inspection App.

    Employees can create inspections whether the access permission is set to YES or NO. That is, the new permission does not affect creating inspections.

Licenses

Setup > Module Licenses

  • TMT-326958

    The Trimble Login ID module license has been added to the Core Section as a new module. This license enables the Trimble ID module and the Trimble Identity SSO Options section in Settings Manager (Configuration > Settings Manager on the General > Core > Login Info tab).

Trimble Technician Portal (TTP)

  • TMT-321998

    You must know your Windows domain controller IP address before completing the setup. To let Active Directory users log in, complete these steps:

    1. Use File Explorer to open the Server API web.config file in a text editor, such as Notepad or Notepad++.

    2. Update the web.config file.

      Add a new connection string for the LDAP server.

      Example:
      <add name="ADConnectionString" connectionString="LDAP://10.60.10.21/OU=People,DC=tmwsystems,DC=com" />

      Replace the LDAP IP address shown here (DC=tmwsystems,DC=com) with the IP address of your Windows domain controller.

    3. Add the membership provider for Active Directory under system.web using the connection string added in Step 2.

      Example:
      <membership defaultProvider="ADMembershipProvider">
      <providers>
      <clear/>
      <add name="ADMembershipProvider"
      type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ADConnectionString"
      attributeMapUsername="sAMAccountName"></add>
      </providers>
      </membership>

      The connection string name you enter here must match the one you entered in Step 2 exactly (such as connectionStringName="ADConnectionString"). Any error in the name will break the setup.

    For more information, see TMT AMS Windows Authentication User Guide.

Users

Security > Work With Users > Create Users

  • TMT-326845

    Adjusted the TMT Web user creation logic for Trimble ID (TID) enabled users. The program follows this hierarchy when creating and sending a TID invitation email:

    • If the Username field is a valid email address, the program sends the invitation to this address.

    • If the Username field is not a valid email address, the program checks the E-mail Address field. If this field contains a valid email address, the program sends the invitation to this address.

    • If the program cannot find a valid email address in either field, the program issues this error message: "TID invite could not be issued. No valid email address was provided." The program also highlights the Username and the E-mail Address fields in red to indicate the errant fields.

V.2025.1.3 Resolutions

Database

  • TMT-327051

    Fixed a problem where the database task Process TMWAMS Audit Purge was not completing successfully. This issue happened when the Serial Tire Reading Inspection ID (INSPRPTID field) was not properly cleared while records were removed. Now any records that are removed during this process will have their INSPRPTID field set to NULL.

Inventory

Inventory > Physical Inventory

  • TMT-326194

    Fixed the issue of sticky notes not allowing you to adjust the actual value to zero. Disabled the sticky notes from physical inventory with the system message "Sticky Note is restricted in the Physical Inventory page".

Landing page

  • TMT-327147

    How you set the Use PM Due Calculation Job Application Option affects how the PM Due widget behaves on the Landing page:

    • If the option is set to YES:

      • The PM Due widget updates in real time when a new PM is scheduled for a unit, regardless of the scheduled job time.

      • Clicking the refresh icon updates the widget immediately.

      • Refreshing the browser window does not affect the widget’s contents.

    • If the option is set to NO:

      • The widget only updates when the scheduled calculation job runs.

      • Clicking the refresh icon does not update the widget.

Core Parts

Orders > Purchase Order

  • TMT-327186

    Corrected an error where the order number should be generated for the Standard PO in the Used Core Bank Manage Forms pop-up window. The program correctly generates the number when the Enable Core Tracking option is set to YES (at either the Application or Shop level) and Default PO Type for Core Credits is set to Standard.

Repair Orders

Orders > Repair Orders

  • TMT-326942

    The program was rounding vendor-supplied part quantities when you added a decimal amount to a non-vendor parts master part.

    When adding a new vendor supplied part, if you choose not to add the part to the Vendor Part Master, when you add a decimal quantity, it will round to the nearest whole quantity. The quantity UOM is set to a value that allows for 2 decimal places.

Shops

Masters > Shops> Orders tab

  • TMT-326775

    This update has changed how the Tax On Fees? setting works. In the past, this setting was a simple YES/NO option that applied to all fees on a repair order. Now, you can set the tax status for each fee individually. This let the program calculate taxes more precisely, in accordance with state requirements. The Tax On Fee Configuration window lets you enable or disable taxes on each fee.

    Note: The Cancel button has been removed from the Tax On Fee Configuration window. If you have not made any changes, select OK to close the window.

Trimble Technician Portal (TTP)

TTP > Repair Orders

  • TMT-326360

    Corrected an issue where closing a repair order in TTP generated invalid OEM Potential Warranty claims. This issue occurred when RO sections made in TMT left the warranty value blank.

Units

Masters > Units > Meters/Fluids

  • TMT-326902

    Fixed an issue where the program was improperly giving the error "Daily Max Exceeded".

Users

Security > Work With Users > Create Users

  • TMT-326820

    Added fixes and enhancements for Trimble ID (TID) User Creation:

    • Added a tool tip to inform you of the requirements for username/email precedence to send TID invitations: "A valid email is required in the 'User Name' or 'E-mail Address' field. If an email is provided in the 'User Name' field, it will be used to send the TID invite. Otherwise, the 'E-mail Address' field will be used." That is, the program uses this hierarchy when sending TID invitations:

      • If the program finds a valid email address in the User Name field, it sends the TID invitation to that address.

      • If the User Name does not contain a valid email address, the program reviews the E-mail Address field. If the program finds a valid email address, it sends the TID invitation there.

      • If neither the User Name nor the E-mail Address fields have a valid email address, the program will display the error message.

    • If you try to create a duplicate TID, the program displays this user creation error message: "Tool Tip to inform the requirements for username/email precedence."

    • The Status column heading has been renamed to TID Invite Status. The Send Invite button has been renamed to Send TID Invite.

    • The page identifies users who are not TID-enabled by showing N/A in the TID Invite Status column.

    • If you are logged in as a TMT user, but not a TID user with admin rights, then when you select Send TID Invite, the program gives you this error message, "Failed to send TID invite. Please login as a TID user to send invites."

Security > Work With Users > Review Users

  • TMT-326820

    See TMT-326820 under Security > Work With Users > Create Users.

  • TMT-326861

    Added and updated processes for TID user invitations.

    • You can invite a TMT user to become a TID user. Select the user’s row on the Review Users page, and then select the Send TID Invite button.

    • In the past, if a TID user was created before the invitation process their TID Invite Status would appear as NULL on the Review Users page. Now, it is listed as ACCEPTED.