Classic TMS 5.38 Release Notes
We're delivering this automatic upgrade on August 27, 2026.
Get started
Improvements and issues fixed
| Component | Summary | Reference # |
|---|---|---|
|
Procedures |
Sub procedure readings now correctly populate and display in the Sub procedure readings worksheet, including readings triggered by Flows. |
TMSPROV-12974 |
|
Administration |
TMS Classic now automatically creates user accounts in Tms online admin and the customer database when a new user logs in via Single sign-on, correctly linking records and applying permissions based on the Sso group mapping defined in the database. |
TMSPROV-17475 |
|
Quick Convert |
The Asset import tool now creates new work orders with blank sub procedure readings when using an Example work order. Readings from the example record are no longer copied to new work orders, and the original example data remains unchanged. |
TMSPROV-21574 |
|
Schedules |
The Pm schedule query now returns all schedules filtered by Asset group, including those created in the Pm schedule master or Pm schedule (multiple assets) forms. Results also include In (inspection) schedules associated with the asset group. |
TMSPROV-23566 |
|
Schedules |
Work orders with numerous assets and more than 15 required Sub procedures now complete without crashing or timing out. TMS Classic successfully updates the status to Complete and generates an alert if required readings are missing. |
TMSPROV-27253 |
|
Schedules |
When a Variable pm schedule has a work order closed as Closed not performed (CNP), TMS Classic now correctly resets the schedule to allow for new work order generation. This applies to both manual and auto schedule generation. |
TMSPROV-29228 |
|
API/REST |
The Tms rest api no longer requires Meter type or Meter reading fields when creating or updating assets. Patch and Post operations now succeed without these values, allowing for updates to non-meter-related fields without validation errors. |
TMSPROV-29547 |
|
API/REST |
The Tms rest api now correctly evaluates user group permissions when creating Network address objects. Post operations succeed if the user group has Full permission for the Assets module in the target Segment. |
TMSPROV-29548 |
|
Permissions |
In Setup > Security > Users, TMS Classic now restricts visibility to users whose default User group has access to the same segments as the current user. This prevents viewing or modifying users with access to other segments. |
TMSPROV-30128 |
|
TMS Core |
In Purchasing > Requisitions > Manual req generation, the vertical scrollbar now remains visible after sorting the list by column headers, such as Material number. This ensures all items remain accessible in TMS Classic when a warehouse contains enough records to require scrolling. |
TMSPROV-31408 |
|
TMS Core |
During Manual requisition generation, TMS Classic now correctly divides the required quantity by the Order factor. This ensures the requisition line and Quantity on hand reflect the correct amounts after processing. |
TMSPROV-31409 |
|
Work Order |
TMS Classic no longer crashes when you enter a retired asset in the Asset number field of a work order. The application now displays a validation message and allows you to clear the field and save the record without closing unexpectedly. |
TMSPROV-31716 |
|
Quick Convert |
When using Quick convert to import Tasksubtask relationships, TMS Classic now correctly links all Sub-procedures to the parent Procedure, including checklist procedures. The application now displays a failure message if the association is not created, preventing false success reports. |
TMSPROV-31980 |
|
Data Sources |
TMS Classic now supports SQL queries using Union all in reports and data sources. To maintain security, Insert, Update, and Delete operations remain blocked. All queries execute via a read-only account, and requests for sensitive system information are restricted. |
TMSPROV-32265 |
|
Fresenius |
Work orders generated from a Pm schedule requiring a sign-off now correctly include all signature verification fields. When you submit a Log, TMS Classic mandates that a different user completes the second sign-off. |
TMSPROV-25692 |