TMT Fleet Maintenance V.2022.3.4 Release Notes

This document contains information on the latest version, including:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

PDF version

Warnings

PLEASE READ BEFORE UPGRADING

Starting with V.2022.2, the AMSLIC (license) database has been merged with the TMWAMS (TMT) database. The installer now works with the new merged database alone.

Existing customers must:

  • Run the provided installer migration script to copy all the data from their AMSLIC database to the TMT database.

  • Perform the upgrade using this merged TMT database. The AMSLIC database will become an invalid input in the SQL setup page of the installer.

After doing an upgrade, the web.config file should only have a TMT database, so that the application will launch without issues. The web.config file will still have two database connect entries, as they exist today, but both will refer to the same database.

New customers with a fresh database do not need to run the installer migration script. They can install the program using the TMT database alone.

If you are currently using an older Client-Server version, you must upgrade to at least V.2019.4 before running the merger script to upgrade to V.2022.2.

Important information, please read

  • SQL Server Cardinality

    Changes to SQL Server cardinality are affecting the performance of TMT Web. The issue happens when SQL Server compatibility mode is set to 120 or greater. This has been identified through Trimble benchmarking and customer feedback.

    At this time, Trimble recommends that you set the SQL Server option for Legacy Cardinality Estimation to ON. This will lessen the effects of the new SQL Server cardinality behavior, which still needs further assessment/improvements in TMT Web.

  • Trimble Technician Portal (TTP) single sign-on (SSO)

    • If you will be using TTP SSO, you must allow pop-up windows. You cannot block them. This applies to Apple and Android phones and tablets. If you block pop-up windows, SSO will not work correctly.

    Follow the directions for your tablet and browser to allow pop-up windows.

    • If you have issues with TTP after upgrading, you may need to clear your browser cache. Close the TTP application and follow the directions for your browser to clear the cache.

    • If you have bookmarked a TTP URL that has a version number, such as 21-3, you should delete that bookmark. Use and bookmark this URL instead: https://tmt-ttp.trimble-transportation.com/

  • TMT Client-Server (Delphi) 2019.4.1 or any earlier version cannot be used with TMT Fleet Maintenance 2020.1 or later. Do not upgrade unless you are ready to go to TMT Web only.

  • Customers using both Integration Options and Windows Authentication should set up their systems so that User drop-down lists use the WINUSER value, instead of the USERNAME value.

  • This version requires .Net Framework 4.8. See the hardware requirements for more information.

  • Customers who are on versions of TMT Web before 2021.3 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 xref: https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-allows-javascriptserializer-deserialization

    • 2021.3, 2021.3.2, 2021.3.3, 2022.1, and later

      These versions use an upgraded Telerik version that has patched the vulnerability. No changes are needed.

    • 2019.4

      Upgrade to V.2019.4.8 to get the security patches for the Telerik DLLs.

    • 2019.2

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

    • Before 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.

Before upgrading your production environment, Trimble recommends that you read the hardware requirements and install the latest version in a test environment. If you have questions, please contact your Trimble customer representative.

Changes to hardware requirements

You must be using SQL Server 2016 or later to use TMT Web V.2022.1 or later.

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

Two files from Microsoft are required for this version:

  • SQL Server 2016 CLR Types

  • SQL Server 2016 Shared Management Objects

You must download and run both files using these links before upgrading to TMT Web V.2022.1:

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 or other technical questions, contact Dawn Siegel at [email protected].

If you have technical questions, contact TMT Support:

Windows Server and SQL Server Support

  • Windows Server 2012, 2016, and 2019 support SQL Server 2016.

  • Windows Server 2022 does not support SQL Server 2016.

  • Windows Server 2012, 2016, 2019, and 2022 support SQL Server 2017.

  • Windows Server 2016, 2019, and 2022 support SQL Server 2019.

  • Windows 2012 does not support SQL Server 2019.

Interactive Workstation replaced by Trimble Technician Portal

Effective with V.2022.3, Trimble has replaced Interactive Workstation (IWS) with Trimble Technician Portal (TTP). Mechanics Workstation (MWS) has also been replaced by TTP. Here are some highlights:

  • You can now open TTP from TMT Web.

  • All IWS options (Application, Customer, Shop, User, and so on) have been replaced with TTP options.

  • References to IWS or MWS throughout TMW Web have been replaced with TTP.

There are some IWS features that will not be available in TTP V.2022.3, but they will be included in future releases. Please contact Support for additional information if you are using any of these features:

  • Allow charging more than qty 1 serial/position

  • Custom company logo

  • Forgot Password

  • Inspection Tickets and Quick RO

  • Pendings/PMs at RO Create

  • Spanish Language Support

  • Sticky Note support

  • Support for switching shops/restrictions

These IWS features will no longer be available (that is, they will not be included in TTP):

  • Gate in/Gate out

  • Yard Check

Enhancements

Orders menu

Repair Order

  • TMT-318620

    When TravelCenters of America (TA) starts a repair request and includes an Associated Unit value, that value will fill the Associated Unit field in the TMT vendor repair order (VRO) header. If TA also sends a tractor number, then the TMT VRO header shows that tractor number in the Associated Unit Number field.

    • The Associated Unit Number field on the Repair Request form will always match the Associated Unit Number field on the Repair Order header.

    • In the Repair Request form, the page shows a validation message on the screen with the changed Associated Unit Number value. This shows the before and after values for the Associated Unit field.

    • If TMT has the Associated Unit field turned on and required, the VRO header shows the field. TMT will complete the Associated Unit field with the Tractor Unit Number provided by TA. If the Tractor provided by TA is invalid in the TMT Unit Master, however, TMT will leave Associated Unit Number field blank.

    • If someone has already completed the Associated Unit Number field with a valid Unit Number, and TA sends an incoming value that is invalid, TMT will not overwrite or remove the existing Associated Unit Number value.

    • If the Associated Unit field is required, TMT will not allow the Repair Coordinator to save the VRO header if the Associated Unit field is blank or filled with an invalid value. The user must enter a valid Associated Unit Number to save their changes.

Resolutions

Orders menu

Repair Order Template

  • TMT-316000

    The VRO Template includes the approval process. The template autofills the Estimate field with the VRO total.

    • If the user’s approval limit is less than the total (as calculated using the Estimate field), the template sets the Approval Status to Needs Approval.

    • If the user’s approval limit is greater than the total, the template sets the Approval Status to Approved.

    • If the user adds multiple template sections to same VRO and the total value is within the user’s approval limit but greater than the Estimate value, then the program opens the Update Estimate Field pop-up window.