2022.1

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.

A PDF version of these release notes is available.

Warnings

Social Security number encryption warning

Starting in version 2020.2, Social Security numbers you enter in the Driver profile are encrypted in the database by default.
However, you can set up the system so that the Social Security numbers you enter in the Driver profile are not encrypted in the database.
To do so, set the DataEncryption General Info Table setting’s String1 field to N.

The Data Conversion Administration Utility lets you encrypt/decrypt a group of Social Security numbers in your database. Contact your Professional Services representative to obtain the DataConversionAdministrationUtilityInstall.msi.

Access and usage of The Data Conversion Administration Utility should only be provided to a system administrator. That utility provides access to all highly sensitive data and should only be used in the explicit instance of needing to encrypt or decrypt the driver profile.

Cancel order/trip feature warning

Starting in version 2020.1, the user interface for the cancel order/trip functionality has changed. Several enhancements were made to make the process easier and more intuitive. Also, the same Cancel Trip/Order window is now used in both Order Entry and in the Trip Folder.
For more information, see Canceling an order in version 2020.1 and later.

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 2022.1, check that these requirements are met:

  • TMWSuite®
    You must be using TMWSuite V. 2022.1.

  • 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, SQL Server 2016, SQL Server 2017, and SQL Server 2019 are certified for use with this application. 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 Preplanning
    You must have these Trimble Web Products and modules installed:

Enhancements

EDI

Auto creating companies based on Alternate ID supplied in 204s (TTESUITE-201835)

When you accept load tenders, they may list companies that are not in your TMWSuite database. The system compares the companies on the tender with the database. It looks for matches by company name, Alternate ID, and address. If it does not find a match, it copies the information to the Select Company for Bill To or the Select Company for Stop Location window. From there, you can review the information and create a new company using the data from the tender.

Now, the IntraCompanyMatching` setting lets you have the system compare the Alternate ID field in the 204 with the company ID in the company’s profile. If a match is found, that company is used when creating the stop. If no match is found, the system creates a new company profile using the Alternate ID from the 204 as the company’s ID in the profile. You can turn on the IntraCompanyMatching setting in the Interface Settings application. If you do not turn it on, the system works as before.

Interface Settings

New EDI settings added (TTESUITE-70324)

New General Info Table settings are now available in the Interface Settings application.

  • The LTLEDI204StatusCode appears on the DX Configuration window’s DX Service tab.

  • The Customer EDI Codes window’s 214 GI Settings tab includes three settings related to 214s.

    • EDI214Limits

    • EDI214SendFirstX6Immediately

    • NewEditAuto214sOnHoldWindow

Mileage

Default Traffic and Weather options on TrimbleMap (TTESUITE-201165)

You can set up TMW Operations to use Trimble MAPS. With Trimble MAPS you can view and track trip and resource data on a detailed map. You can overlay the base map with additional layers of data. For example, you could show current weather information and/or traffic conditions. By default, all the layer overlays are turned off.
Now, you can set up your system to have the Traffic layer and/or the Weather layer on by default. You use these settings in the [TmwMapping] section of your TTS50:

  • ALKTraffic

  • ALKRada

Row Level Security

Extending Row Level Security to field options (TTESUITE-200685)

Row Level Security (RLS) lets you secure records. For example, security can be applied to records belonging to specific companies, divisions, or terminals. It limits access so that only users assigned to them retrieve their records. You do this by:

  • Identifying the tables and fields that would have security applied to them.

  • Specifying the field values associated with a user’s login.

This worked well when users retrieved records. However, when users created records such as orders or profiles, they could select any value in fields that have user-defined options. Their selections in these fields were not limited to what was defined for them when retrieving records. This meant that they could enter incorrect information accidentally. Once the record was saved, they could not access it to fix it.

Now, you can set up RLS to also use label security. Label security limits the options users can select in certain user-definable fields that have security applied to them.

Once you assign individual label options to a specified label key, only the groups or users assigned to the same label key value can see them in the user-defined field.

Notes:

  1. Row Level Security is a licensed add-on. In addition to the license, the RowSecurity General Info Table setting must have a String1 value of Y.

  2. In this release, the LTL Operations Module does not support extending RLS to filter field options in windows that are specific to LTL functionality. It does support it in profile and scroll windows that it shares with the TMW.Suite applications.

Stops grids

Address validation added to the Stops grid (TTESUITE-201542)

Your company may not create company profiles for all of the locations where you do pickups and deliveries. The system lets you enter a street address for a stop location. Now, you can set up the system to validate street addresses entered for stops that have a Company ID field value of UNKNOWN. The validation is not performed for stops that have a valid company ID.

To use this feature, you must:

  • Use PC*Miler as your mileage system.

  • Have [PCMilerMap]EnableStopLevelAddressValidation=Y in your TTS50.

When the setting is in place, you can validate stop-level addresses in the Trip Folder’s Stops grid and on the Order Maintenance All Stops tab.

In both places, you use Field Chooser to add these fields:

  • Address Validation

    This field is available when you have [PCMilerMap]EnableStopLevelAddressValidation=Y in your TTS50. It does two things:

    1. It acts as a button to let you trigger the validation process for the stop.

    2. It shows color indicators that tell you whether the stop’s address has been processed and if it is valid.

      • Green means the address has been validated and is valid.

      • Red means the address has been validated and is not valid. Red also shows when you have canceled the validation.

      • Yellow means the address has not been validated yet.

      • Gray means the address cannot be validated. Addresses cannot be validated if the stop has a valid company ID, or if you did not make entries in the Address1, City, State, and Zipcode fields.

  • GFC Latitude (stp_gfc_lat)

    This field shows the stop’s latitude returned by the validation process. It is a decimal data type and has a precision of 4.

  • GFC Longitude (stp_gfc_long)

    This field shows the stop’s longitude returned by the validation process. It is a decimal data type and has a precision of 4.

Save the grid layout after adding the fields.

Note: The GFC Latitude (stp_gfc_lat) and GFC Longitude (stp_gfc_long) fields are available in Field Chooser after you apply the TmwOperationsDBMods.sql file to your database. The file is supplied with the TMW Operations 2022.1 installation files you download from ClientCenter.

You record the stop address for stops that have UNKNOWN in the Company ID field. You must make entries in the Address1, City, State, and Zipcode fields. When you tab out of the Zipcode field, the validation starts.

  • If the process finds a match, the indicator in the Address Validation field shows as green.

  • If an exact match is not found, a pop-up window opens. It shows possible matches. When you select one of them, the stop’s address and ZIP Code are updated to your selection. The Address Validation field indicator shows as green.

  • If the process does not find an exact match or an address that is a possible match, the Address Validation field shows as red.

  • If the stop cannot be validated, the Address Validation field shows as gray.

Note: When using this feature, orders must have a valid company ID in the Order By and Bill To fields.

Trip Folder

Improved retrieval error messaging (TTESUITE-156781)

Before, when you retrieved a record in the Trip Folder and the retrieval failed for any reason, you saw a generic error message. Now, error messages are more specific. For example, the message may state:
"Unable to Load Trip" Could not find a stored procedure.

TruETA

Latitude/Longitude web.config update (TTESUITE-201694)

TruETA was sending the latitude and longitude object name as “Coords” with a tag of “Coordinates” to the TruETA service. The tag should match the object name. This caused the lat/long values to be ignored for a location. The TruETACorrectNALongitude key has been added to the SystemsLink web.config file. It ensures the lat/long values are recognized for North America.

Resolved issues

Brokerage

  • TTESUITE-201685
    The Brokerage board’s Notes tab displayed notes as read only. To access the board, go to Operations > Company Planner > Brokerage.

Company Planner

  • TTESUITE-202385
    The Brokerage board did not load or display any content in the window. This included the default board layout.

  • TTESUITE-202831
    The Company Planner grid was no longer refreshing data automatically. This happened even though the grid Refresh Time interval was on. You set the interval in the window Company Planner Setup > Grid Options > Refresh Time.

Company Scrolls

  • TTESUITE-200871
    Clicking the Show Map button caused a PC Miler error. You saw a message stating, "PCMiler Service not installed properly, the function will not continue". You got the error for any company listed in the scroll window.

EDI

  • TTESUITE-201606
    If the AutoCancel204s Interface setting is on, the system cancels an order when it gets a Cancellation204 for it. The cancellation happens automatically. Before, orders would not be cancelled if their status was Started or Dispatched. Now, in addition to started or dispatched orders, the system will not cancel orders that have been consolidated or cross-docked.
    This change takes place when you upgrade to the 2022.1 version of TMW Data Exchange and update the 204 script.
    Note: You apply the AutoCancel204s` setting for each of your trading partners separately.

  • TTESUITE-201795
    When you accept an EDI Cancelation for an order that is consolidated with another order or orders, the system:

    • Removes it from the consolidation

    • Cancels it

    The process does not corrupt the orders that remain on the consolidation.

Freight Board Interface

  • TTESUITE-201376
    The leg number is used in the posting ID when you submit orders for posting. When a trip is started, the system creates the queue record for LSM. When LSM runs, Freight Board Interface cancels the load posting. The cancellation is sent to the appropriate board(s). The Load Status Monitor (LSM) stopped pulling down trips because leg numbers were too many characters. Now, Freight Board Interface and LSM accommodate leg numbers of up to ten characters.

Group layout priority

  • TTESUITE-201356
    A user’s default grid layout was ignored when:

    • The user was assigned to multiple groups

      and

    • No default grid layout existed for the highest priority group shown in the Layout Priority list.

    The system used the global default layout for all groups. It ignored the default layout assigned to the highest priority group.

Scrolls

  • TTESUITE-200871
    In some scroll windows, you could not show a specific item in the retrieval grid on a map. When you clicked its row, a PC Miler error occurred. This affected these scrolls:

    • Company

    • Driver

    • Tractor

    • Trailer

Trip Folder

  • TTESUITE-159956
    Clicking Compute Pay on the Profit and Loss tab could cause an error. You saw a message saying that pay details could not be created. This happened if the order had two stops at the same location and the first stop’s event type was non-payable. The system treated the miles calculated for the trip as non-payable.

  • TTESUITE-160266
    In the Trip Folder, you can go to Edit > Send Load Confirmation to send a load confirmation for an order. This action caused a GEH error.

  • TTESUITE-201228
    When you made multiple copies of an order using the Copy Order/Trip window, the Copy Notes checkbox would change from cleared to selected. This caused notes you did not want copied to be on the new orders. If you had [Order]CopyNotes=No in your TTS50, the system ignored it.

Trip Planner

  • TTESUITE-202388
    By default, the Trip Planner window has five sections:

    • The top of the window shows the Restriction fields.

    • The Trips/Resource pane appears below the Restriction fields.

    • The Timeline pane appears below the Trips/Resources pane.

    • The bottom of the window shows the Shift pane on the left. It shows the Assignment Plan pane on the right.

    You could get an "Out of Memory" error if you:

    1. Used the scroll bars to move to the bottom or the right in the Assignment Plan pane.

    2. Resized the Shift or Assignment Plan panes.

  • TTESUITE-202801
    You can use the Route Maintenance window to create route templates. When you generate a route from a template, it creates a trip. The system was not handling trip assignments correctly after you used the route generator. When you dragged a trip to a driver’s shift for the day:

    • Deadhead stops were not added at the beginning of the driver’s shift.

    • Pickup and drop stop arrival and departure dates were not calculated based on the trip’s duration.

    This caused the Trip Planner to show additional trips for drivers that did not belong on a specific day’s board. It also caused the Timeline (Gantt bar) to show incorrect trip durations.