2019.4

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

Warnings

User level record security

Starting with TMW Operations version 2019.1, there is a functional change that will affect customers using custom views on Company Planner, Brokerage, or Covering boards that rely on User Level Record Security. Affected customers may need to contact Support for assistance before upgrading. See the User level record security resolved issue for details.

Minimum technical requirements for 17.50 or higher warning

To upgrade from a build lower than 17.50 to 17.50 or higher, you must follow these steps.

  1. Notify your Support team that you will upgrade. (As noted in Step 4, they will need to work with you to complete the installation process.)

  2. Verify that your environment adheres to these minimum technical requirements:

    • Microsoft .NET Framework version 4.6.2 must be installed.

    • Client operating systems must be at Windows 7 SP1 or higher.

    • Server operating systems must be at Windows Server 2012 or higher.

    • In addition, verify that your system adheres to the additional requirements listed in the General requirements section for the build you are upgrading to.

  3. Run the TMW Operations installation program.

  4. Before any users attempt to use TMW Operations, call your Support representative to have them update your Planning Worksheet boards.

Trimble Transportation has added columns to the system default Planning Worksheet views to enhance the inline editing feature. These columns also must be added to all custom views. Support will perform this step for you at no cost.

Case sensitive passwords warning

Starting with V.17.50, the system treats all passwords as case sensitive. This includes existing passwords.

This change affects how you log in with an existing password:

  • If your password was created with [Misc]CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

  • If your password was created with [Misc]CaseSensitivePasswords=ON in your TTS50, you can enter that password as you originally recorded it (case sensitive).

Requirements

Before you begin installing TMW Operations version 2019.4, check that these requirements are met:

  • TMWSuite®
    You must be using TMWSuite 2019.4.0.0007 or later.

  • TMW Back Office
    If you are using TMW Back Office, your version of TMW Operations must be the same as your version of TMW Back Office.

  • Microsoft® .NET Framework
    .NET Framework 4.6.2 or later (full package not client)

    The framework must be installed on the TMW Operations server, client, and administrator systems before you install TMW Operations. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Internet Information Services (IIS) for Microsoft Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft SQL Server®

    • Microsoft SQL Server 2012 or later

      Note:* SQL Server 2014 and SQL Server 2016 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • You must be logged into the system where you want to install TMW Operations, and have administrator rights for that system.
    Like most applications, TMW Operations can be installed locally on a user’s system. It is also possible to install TMW Operations on a network drive. To do so, you must be logged into the system where the drive is physically located, and have administrator rights for that system.

  • SQL Server System Administrator rights are necessary.
    The installation of TMW Operations includes the manual application of a SQL script to the TMWSuite database. You must have a SQL Server administrator login and password to apply it.

  • TruETA
    You must have these Trimble Web Products and modules installed:

Enhancements

Commodities

Company Product Maintenance window added (NSUITE-207155, NSUITE-208168)
Use the Company Product Maintenance window to link commodities and their sub classes with pickup and delivery locations. In this window, you can also:

  • Assign a supplier

  • Apply a volume-to-weight conversion

  • Verify that calendar-based start and end dates for picking up and delivering commodities are valid.

If a pickup or delivery company has no product relationships, you can copy all product relations from an existing company to it.

EDI

Specifying the number of EDI 214 records to process (PB-200708)
Previously, when an EDI Scheduler job started, the batch included all 214 records in the database. For very high volume clients, batches could be too large to complete before the job timed out. This caused changes to records to revert, which produced failed records. Failed records were put back in the queue for the next batch.

Now you can set the number of records to be included in a batch. This eliminates an ever-increasing backlog and allows records to be processed in a timely manner.

Use Hours Out and Hours Back with Date range to retrieve orders on EDI tab (NSUITE-207976)
In previous versions, the Planning Worksheet’s EDI tab, like all the tabs, retrieved trips using a date range. A user could manually enter the dates. If the user did not enter the date range, the system would use the entries in the Hours Out and Hours Back fields to determine it. The stored procedure used to retrieve data for the EDI tab did not use a date range. It used the hours out and hours back values. It treated the lookup as if the Hours Out and Hours Back fields had the default values of 0 (zero) which equals 1.000.000 hours or 277 days.

Now, the system accommodates using a date range. It translates the range to the number of hours back and the number of hours out.

eManifest

New Service Code added for ACI (TSI-285)
The Freight Information grid now includes InTransit as an option in the Service Code field.

Fuel Maintenance

Setting pay details initial status to Pending (TSI-422)
Now you can set up the system to have the initial status of imported pay details set to Pending instead of On Hold.

Performance improvements

Performance improvements have been applied to these features:

  • NSUITE-204563 – Legs grid in Asset Assignment History

  • NSUITE-207742 – Retrieving information in Asset Assignment History

  • NSUITE-207743 – Route Code instant best match field

  • NSUITE-207760 – Trip Folder’s reference number validation

  • NSUITE-207761 – MoveManager.ValidateOrderTMW

  • NSUITE-207768 – Editing stop dates

  • NSUITE-207785 – Trip Folder’s Trip and EDI tabs

  • NSUITE-207845 – Scroll Reference Numbers

  • NSUITE-207965 – QuickDesigner

  • NSUITE-207966 – Trip Folder’s Profit and Loss tab

  • NSUITE-207967 – Trip Folder’s Schedule Dates Change Log tab

  • NSUITE-208095 – FreightDetail.fgt_parentcmd_fgt_number

  • NSUITE-208175 – Trip Folder’s Activity Audit tab

  • NSUITE-208177 – Trip Folder’s Manhattan tab

  • NSUITE-208179 – Trip Folder’s TM Messages (TotalMail messages) tab

  • NSUITE-208213 – Trip Folder’s Check Calls tab

  • NSUITE-208227 – Trip Folder’s Trip Audit tab

  • NSUITE-208228 – Trip Folder’s Intermodal/Container Selection Control tab

  • NSUITE-208229 – Trip Folder’s Documents tab

Prior Commodity Cleaning

Requiring cleaning logs on trailers carrying incompatible commodities (NSUITE-207934)
When you assign a trailer on a trip, the system compares the commodity on its last trip with the commodity on the newly assigned order. If the commodities are not compatible, the Trailer Cleaning Needed window opens when you try to save the assignment. To save the assignment, you must verify that the trailer was cleaned as required or assign a different trailer.

This only applies to single commodities.

Processing trailer cleaning for multiple freight (NSUITE-208036)
You can now process trailer cleaning validation for more than one type of freight contained in different compartments on a trailer.

New setting controls validation and menu option visibility (NSUITE-208198)
A new General Info Table setting, TrailerCleaningValidation, replaces the [Misc]EnableNewPriorCommodityRules setting in your TTS50. If you have this setting in your TTS50, the system will ignore it.

  • String1 controls whether the Prior Commodity Cleaning command appears in the Tools > Tools Maintenance menu.

  • String2 contains three options for trailer cleaning validation.

    • IGNORE
      The system never attempts to perform a cleaning validation when you save a trip in Trip Folder.

    • WARN
      If the system determines that it can perform the validation, the Prior Commodity Cleaning window opens when you save the trip.

    • ALWAYS
      The system will always open the Prior Commodity Cleaning window when saving a trip in the Trip Folder.

Reference Number Scroll

Setting a default search option for the Reference Number Scroll (NSUITE-207845)
The search for the Addins Scroll Reference Numbers field had the default reference number set to LIKE, which is the least efficient search method. You can set up the system to allow users to select more efficient search methods, such as EXACT or STARTSWITH.

SystemsLink

SystemsLink expiration services now display the Completed column (API-634)
SystemsLink consumers can now complete expirations for TMW resources using the Completed column.

Resolved Issues

Asset beaming

  • NSUITE-205624
    Previously, the only String1 options that the system recognized for the AssetBeamLev General Info Table setting were for tractors (TRC). The system now recognizes when String1 is set for drivers (DRV1 and DRV2) and trailers (TRL1 and TRL2) as well.

Custom layouts

  • NSUITE-207571
    Fixed an issue that occurred when applying a custom grid layout to the Tank Maintenance window; drop-down lists were not functioning as expected.

  • NSUITE-207572
    Fixed an issue that occurred when applying a custom grid layout to the Axle Limit and GVW Limit data grids on the Jurisdiction Road Restrictions window; drop-down lists were not functioning as expected.

Confirmation messages

  • NSUITE-207879
    In the Jurisdiction Road Restrictions window, if a user deleted a record in either the Axle Limits or Gross Vehicle Weight Limits grid and then added a duplicate record, a GEH error occurred. Now a confirmation message appears when a user deletes a record.

  • NSUITE-207880
    If a user deleted a record and then added a duplicate record in the Fleet Licensing window, a GEH error occurred. Now a confirmation message appears when a user deletes a record.

Database

  • NSUITE-202204
    In Order Maintenance, there was a problem with the Additional Order Header Information window’s Show As Shipper and Show As Consignee fields. Entries in the fields were not applied to the database when the order was saved.

EDI

  • PB-200753
    On outbound 204 EDI orders, the flat file output included reference numbers attached to order headers having a reftablekey value of 0 (zero). Now the system only includes reference numbers for stops on the leg where the ord_hdrnumber is greater than 0 (zero).

  • TSI-330
    Object Reference error produced when processing 204s with empty fourth line.

eManifest

  • TSI-213
    Freight and company information is not displayed in eManifest for cross docked moves.

Fleet licensing

  • NSUITE-207823
    When the Show Expired checkbox remained clear, a GEH error occurred when saving a new row that duplicated a hidden expired row.

  • NSUITE-207574
    Fixed an issue that occurred when loading custom layouts. When a custom grid layout was applied, any drop-down field contained within the layout lost drop-down functionality.

Freight Board

  • TSI-217
    Freight Board Interface supports receiving the available date and time from the Dispatch system. However, the Create Posting tab allowed only the available date to be entered. Now you can enter the time when you enter the date.

Freight By Compartment window

  • NSUITE-208087
    When loading freight compartments using the Freight By Compartment window, the Compartment From fields are not being populated with LEAD and/or PUP values based on the compartment’s position in the train.

Fuel Maintenance

  • TSI-214/TSI-215
    If you had [FuelServ]ProcessEFSRejectedTransactions=Y in your INI file, the interactive EFS integration performed the pulling and processing of transaction records. The table used to store transactions must be seeded, that is, has at least one record. If there were no records, the system used a default start date, such as 1/1/2000, to pull rejected transactions. This could cause too much data to be returned, resulting in time outs.

  • TSI-371
    Fuel purchase pay details for an owner/operator were being pulled for a company driver.

HubTran Trimble Integration

  • TSI-416
    If a request comes to release a paydetail that is already closed, the system is setting the paydetail status back to Released. The system now returns an error with an http 400 code, which identifies a bad request.

  • TSI-420
    Exception messages appear as generic, "Internal Server Error" messages. Exception messages should display so that the appropriate required action is identified.

Mileage

  • NSUITE-208204
    Fixed an issue with a setting option that was supposed to limit mileage inquiries to company-to-company lookups but was also including city-to-city information when no valid address was given. This led to incorrect mileage reporting.

Reference Numbers

  • NSUITE-207172
    The system was enforcing reference number requirements before a user made any change to an order-based stop.

System Updates

  • PB-200685
    Tractors with expirations were not appearing in drop-down lists.

Time conflicts

  • NSUITE-207646
    Split trip time conflicts occurred when stops Hook Empty Trailer (HMT) and Drop Empty Trailer (DMT) events scheduled before a Live Load (LLD) switched to billable events (IHMT and IDMT). This issue has been resolved for these and the hook loaded trailer events (HLT and IHLT).

Trailer Profile

  • NSUITE-207728
    The system now retains changes you make on the Trailer Profile window’s Compartments tab, no matter how you move between fields before saving.

Trimble Cloud Imaging

  • TSI-38
    For TMW Operations to work with Trimble Cloud Imaging, the API had to authenticate the connection and provide a Trimble token. Information needed for this is the user’s Single Sign-On (SSO) User Name and Password, a Consumer Key, and a Consumer Secret.

    TMW Operations was storing the Consumer Secret associated with Trimble Cloud Imaging in the database. This allowed tokens to be generated and the system to display documents. However, it presents a security issue.

    Now, the Consumer Secret is no longer needed.

    When you apply the 2019.4 upgrade SQL to your database, the Consumer Secret is removed. You must specify different end points for the integration.

Trip Folder

  • NSUITE-207382
    Fixed an issue that occurred when changing a stop location in the Trip Folder. The system was changing the Earliest Date and Latest Date fields to match the arrival and departure times for the stop instead of preserving the appointment times.

  • NSUITE-207782
    In the Trip Folder, the system was not retaining an updated stop sequence if you:

    • Used the drag-and-drop method to move stops.

      and

    • Changed the event type for one of the stops.

  • NSUITE-208224
    If the [Misc]CompanyProductsRule setting is activated in your TTS50, the system now limits trip validation to the current move you are saving.

TruETA Agent

  • NSUITE-208203
    Fixed a timestamp error that occurred on the UpdateTripStatus call. The system now applies UTC time rather than the local time for the tractor’s location.