17.50

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

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

  • TMWSuite®
    You must be using TMWSuite V. 2017.17_01.0130 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
    Install or upgrade to the latest version of the Microsoft .NET Framework (full package not client) on your system.

    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 2008 R2 or later

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

Enhancements

3PL Billing

Using 3PL Billing (PTS-64140)

A third-party logistics (3PL) company acts as an intermediary between a shipper and carrier providing outsourced transportation services.

TMW.Suite’s 3PL Billing feature provides 3PL companies a process for billing for their services. The feature allows you to specify unique billing rules for your Bill To companies. The rules can be as simple as cost plus markup or you can design very complex billing rules.

The feature works with simple orders or with complex trips that have been consolidated or cross-docked.

3PL Billing is a licensed add on feature. Contact Trimble Sales for more information.

Brokerage

Streamlined user interface (NSUITE-104969)

Based on customer feedback, we have enhanced the default brokerage boards available with TMW Operations. Dispatchers and Customer Service representatives will now have a streamlined user interface that allows them to handle workloads including incoming bid requests more efficiently. These new boards replicate the look and feel of the Brokerage, Covering, and Tracking boards that are supplied to clients during the Implementation process.

Reason Late functionality (NSUITE-98747)

Currently, when you save an order with an early or late stop in certain TMW Operations windows, the system, by default, opens the Reason Late window to warn you.

Now, this Reason Late functionality has been added to the Tracking window in these locations:

  • Check Call/Status Update pane

    Note: This brokerage pane is built upon the Company Planner Check Call/Status cell.

  • Edit Trip pane

    Note: This brokerage pane is built upon the Company Planner CarrierLoadInformation cell.

You can configure the system to do either of the following:

  • Ignore the early/late stop

  • Require a reason be recorded for the early/late stop

By default, these cells are available on the Tracking board. However, any Company Planner board that has a CarrierLoadInformation cell or a Check Call/Status cell will support this Reason Late functionality.

Common dispatch features

Opening the Trip Folder from the Asset Assignment History window (NSUITE-200015)

In the Asset Assignment History window, you can view the trips to which a resource is assigned during a specific date range.

Now, you can open these trips in the Trip Folder by double-clicking on its row in the Asset Assignment History window.

DirectRoute

The TMW integration to DirectRoute allows you to send orders from TMW Operations to Appian DirectRoute for route planning optimization. DirectRoute consolidates the orders into one or more movements and the best route for the trip. This solution is an efficient use of time and resources.

Generating a DirectRoute truck file based on the tractor and trailer (INT-200165, INT-200147)

In the past, DirectRoute truck files were based on tractor information in the TMW database.

Now, you can set up the system to generate a DirectRoute truck file based on the tractor and trailer information. The truck file is saved to the location you set up for the DirectRoute pickup.

Setting equipment code requirements (INT-200321)

Now you can set equipment code requirements on orders. The system will require that the corresponding code is recorded in the profile of the equipment you assign. You can set up the system to record equipment codes in the following locations:

  • Order header

  • Stop detail

  • Freight detail

  • Tractor profile

  • Commodity profile

  • Company profile

Driver Management

Driver Management (NSUITE-200378)

The Driver Management feature gives managers a one-stop-shop for reviewing driver information.

Now, a Driver Management tab displays on the driver profile.

All TMW Operations users can see a recap of these driver items:

  • Basic driver classifications, such as Fleet, Division, Domicile, Company, Terminal, and Team Leader.

  • Data from the driver’s last ten trips

  • Information from the driver’s last ten paychecks

  • Current or upcoming driver expirations

  • Open driver accident information

You will also see dashboards with key performance indicators (KPIs) and driver scores from the TMW Data Warehouse if you have an active Reveal.Business (SaaS) subscription or Reveal.Business Reports and Dashboards 2017.3 or higher (on premise).

  1. You can create your own dashboards or work with our Professional Services group to configure them.

  2. If you are using a custom tab layout for the driver profile, you will need to recreate your layout to see the new Driver Management tab.

Freight Board Interface

Support for 123Loadboard.com freight board services (INT: 85202)

TMW’s Freight Board Interface provides the ability to post available loads and trucks to one or more freight board services from within TMW Operations.

Now, the Freight Board Interface supports the 123Loadboard.com freight board services.

Fuel Maintenance

Rejected Transactions Log (INT-200191)

If you are using the EFS/TCH integration, you can set up the system to show rejected transactions on cards from within TMW.Suite. This information allows you to troubleshoot and assist drivers who have had their cards rejected at fueling pumps.

Card Transfers within TMW.Suite (INT-200193)

If you were using the EFS/TCH integration in previous version, when a card was damaged or broken, you could not assign the driver or unit to a replacement card easily.

Now, the Transfer Card feature allows transfer all the data and balances from the previous card to the new one. The original card is updated to be inactive and unassigned.

System security

Changing to case sensitive passwords (NSUITE-200031)

In previous versions, passwords were not case sensitive by default. To use case sensitive passwords, you had to have [Misc]CaseSensitivePasswords=ON in your TTS50 file.

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 CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

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

  1. This change affects only passwords. It does not affect usernames.

  2. If you log in without entering the password in all uppercase characters, the system displays a message stating, "Failed to connect using the entered credentials."

Link to topic: Logging on

Planning Worksheet

Editing trip comments in the Planning Worksheet (NSUITE-72677)

Now, you can enter free-form comments for individual trip segments in two new columns on the Planning Worksheet: lgh_comment and lgh_trc_comment. Both columns exist in the Available Trips grid and the Inbound Trips grid.

These columns are added as required columns to the system default Outbound (OUTSCR) and Inbound (INBSCR) planning boards.

However, after you upgrade to 17.50, these columns must be manually added to your custom board views before users can use the Planning Worksheet. After you upgrade TMW Operations, contact Trimble Support for assistance with adding these columns.

Link to topic: Recording trip comments

Modeling multiple trucks for a trip (NSUITE-200372)

You can use the Sort Power Closest to Trip command to calculate the distance between the origin of the trip selected in the Planning Worksheet’s Available Trips grid and the destination of each of the tractors listed in the Inbound grid.

This feature has been enhanced. Now, in addition to distance, this feature will also calculate for each tractor:

  • Revenue per mile

  • Driver utilization

This feature removes resources that do not meet the specified load requirements.

Profiles

Adding a Pay To profile from the carrier profile (NSUITE-96049)

In previous versions, when you set up a Pay To for a carrier, you needed to set up the Pay To profile first, and then link the carrier.

Now, you can open the Pay To profile directly from the carrier profile. This allows you to create a new Pay To profile or edit an existing one.

Recording and tracking accident investigations (NSUITE-105683, NSUITE-201245)

You can record accident investigations in the Accidents tab. It is available in these resource profiles:

  • Driver

  • Tractor

  • Trailer

  • Carrier

    Note: If Carrier Management is enabled, the tab is available as a sub-tab in the Carrier Management tab.

On the tab, accidents appear in a grid. You use the Accidents window to add or edit individual accident information, including:

  • Date, time, and location of the accident

  • Weather conditions

  • Whether the accident was preventable

  • Police information

  • Order and dispatch information

  • Investigation status

If any accident investigation has a status of Open, the tab color changes to red.

Resolved issues

3G-TM integration

  • NSUITE-104547
    System shows an error on the commodity when creating the order from Rate Quote window

  • NSUITE-105091
    When creating/updating orders during the transfer process, place the TMW orderheader.ord_number in a reference field.

  • NSUITE-105095
    During the load consolidation process, a multi stop load that is based on mileage cost does not rate.

  • NSUITE-105096
    Currently the user has to maintain the legheader_accessorial table to generate line item rates for TMW Operations integrated with 3G. The desire is to enter a line item invoice/pay detail and have it generate the appropriate billing and pay costs based on 3G contracts.

  • NSUITE-105649
    The charge type description is being left blank. On researching this item, the field that is being used to fill this field is blank when a markup is being applied.

    This change will use the charge type description when no description is supplied by 3G.

  • NSUITE-105709
    If a marked up cost rate contains accessorials, and a matching billing rate is applied that has no accessorials, the accessorials should not show up as invoice details.

    This problem exists in every version.

  • NSUITE-200165
    "ViewLoad" Link in TMW Operations needs to have a lower-case "v" - Within operations, the user may screen design a control 3GLoadLink that, when clicked, should direct them to that load in 3G-TM. However, for the link to load correctly, the v needs to be lowercase in "viewLoad".

  • NSUITE-200669
    HU is set 1 in 3G, even when there are no Pallet(s) records on the freight record

3PL Billing

  • NSUITE-96936
    Need the ability to edit the TM Billing Rating Rules and TM Billing Allocations from the tariff application through TMWSuiteAddins.

  • NSUITE-97391
    We need to lock down invoices for TM Billed invoices similar to what we did for 3g rated invoices.

  • NSUITE-97724
    TM Billing: Rating Rule Maintenance - Per the business specification, users are only allowed to create one rating rule per tariff. The TM Billing Rating Rule Maintenance screen is currently enforcing this requirement, but not handling it gracefully.

  • NSUITE-98757
    3PL

    Issue 1: Allocation Maintenance does not show any indication on the grid/screen that there are required fields

    Issue 2: Messages are incorrect when saving with User Defined Formula.

    Issue 3: Tab does not work correctly after selecting User Defined Formula.

    Issue 4: Messages are incorrect when saving with Stored Procedure.

    Issue 5: Tab does not work after selecting Stored Procedure.

    *Issue 6: Cannot type in Formula field (Not fixed - Per Dev, users must use Formula Editor).

  • NSUITE-99219
    Cost details for Benchmark tariffs display as expected in the Cost Details Tester Window but are duplicated in the 3PL Billing Benchmark window (link from Profit and Loss in Trip Folder).

  • NSUITE-99833
    Since Reconcile billing no longer uses the order invoice status of 3PLHLD, the traditional billing queues will be responsible for generating the linehaul invoices that are based on estimated costs.

  • NSUITE-99934
    When trying to complete an order in the Trip Folder that has a rate mode of 3PL Billing, we should throw an error that will not let the order be saved if the movement contains no paydetails.

  • NSUITE-101055
    GEH Error occurs when Computing Charges Trip Folder Create two new orders Consolidate new orders Save Add Carrier (to both orders) Save Profit and Loss Select 3PL Compute Charges Pay is calculated, but GEH Error occurs and no Charges are added.

  • NSUITE-101193
    3PL Billing Cost Detail Tester no longer calculates with 3PL Billing Charges 'button'

  • NSUITE-101521
    Unable to install TMW No-Touch Processor after installing 3PL Billing Service

  • NSUITE-101925
    3PL Billing Autogen Windows Service - item #199 The Cost Detail Generation worker will "spin" on processing-delayed items when they no longer need to be processed upon the expiration of their processing delay. See Steps to Reproduce for more details.

  • NSUITE-101929
    ivd_type and ivd_sequence are not being populated when invoice details are created in Profit and Loss or the 3PL AutoGen service

  • NSUITE-102038
    Issue #195 Create new INI setting for 3PL rounding. Implement for pay amounts, invoice detail amounts, and rates data for data reporting.

  • NSUITE-102052
    Performance Improvement of 3PL Autogen Views. "Need to address CostDetailGenerationWorker continuing to pickup and reprocess the same order unnecessarily Concerns over Worker/View trying to create cost details over and over again needlessly WHERE [RatingCostHeader_Order].[ID] IS NULL AND [RatingCostHeader_Leg].[ID] IS NULL" #196.

  • NSUITE-102087
    Reconcile process run by TMWTPLBillPostSettlementsView needs to create B invoices, even if A is on a dedicated invoice.

  • NSUITE-102192
    3PL / 3G Modify create pay from cost code logic to include orders in available, planned, and started status for processing (TMWCreatePayFromCostsView). If cost details source is '3' (coming from 3G), mark pyd_updsrc = '3' as well.

  • NSUITE-102199
    3PL / 3G Modify 3PL Compute Charges button logic in Ops P&L to work with 3G: call regular compute pay, if found tariff is marked external /3G, hand processing over to 3G to create cost and pay details. When successful, refresh P&L UI to show pay detail.

  • NSUITE-102257
    When processing 3PL Billing for orders that have been consolidated and cross-docked, individual orders cannot be computed until all legs for all consolidated orders on the cross-docked moves have been completed and paid or completed with a CPU Carrier. We are going to change this so that an individual order can be paid as long as every leg it is on has been completed and paid or completed with a CPU Carrier.

  • NSUITE-102289
    3PL Billing Given a 3PL Billing or Allocate Only trip, when a user makes a change in Operations to the trip, and any order on that trip is already associated to an invoice or a closed settlement, do the following. Upon save in Trip Folder, log a message to TMWSystemWideLogging of Critical Importance that indicates there has been changes in Operations and 3PL. Recompute cannot occur because there are invoicing-related or settlements-related records for the trip.

  • NSUITE-102319
    Completing a 3PL Billing order with a CPU carrier if cost details have not been computed the system error message is incorrect. CPU carriers are not eligible for pay.

  • NSUITE-102346
    Delete records from TPLBillPostSettlementsActive table after processing is done/attempted to be done TPLBillPostSettlementsActive table has records of orders/legs which are currently being processed by 3PL Worker and/or Trip Folder UI.

  • NSUITE-102378
    Allocation is based on Bill Mileage when Cost and Pay are based on Trip Mileage.

  • NSUITE-102430
    Orders are remaining in the Cost Detail view for Pass Thru, Pass Thru Qty, Pass Thru with Markup, or any order that is 3PL and does not have a Rating Rule Setup.

  • NSUITE-102471
    Change freight record on a 3PL trip, did not trigger timestamp difference check in the Windows Service for cost detail compute. Change on orderheader did. Need to make sure any change like that in Trip Folder will trigger the trip to recompute. (Work done for active tables should also verify this behavior).

  • NSUITE-102475
    For both the 3PLAutoGen Cost Detail Worker and On Demand Cost Detail Queue - When recomputing, need to reallocate cost details across all associated moves, but invoice details that are associated to an invoice header cannot be touched in any other status but HLA.

  • NSUITE-102476
    Changes to on-demand queues:

    1. Compute 3PL orders with HLA invoice status

    2. Remove SQL dependency of windows service SQL views from their retrieve

    3. Remove timestamp 'cost details up to date' check from cost detail queue - allow computing of orders where cost details are current.

  • NSUITE-102485
    When creating invoice with rating rule, it is pulling a billing tariff for gallons when the settlement is by weight and the allocation is by miles.

  • NSUITE-102565
    Allocate Only/3PL Eligible not computing the same in 3PL Cost Tester and Trip Folder/Profit and Loss Computes in 3PL Tester, but NOT in Profit and Loss.

  • NSUITE-102781
    3PL Compute When computing 3PL cost/pay/invoice details for two orders cross docked and consolidated on the outbound leg, the system is not persisting cost details for the outbound leg of the cross dock.

  • NSUITE-102824
    In the case of ALLOC rate mode, need cost detail worker to continue to create/update invoice details, even after the leg(s) have been closed when rate mode is ALLOC. The on-demand cost detail generation queue, 3PL Autogen Cost Detail Worker, and the Trip Folder Allocate Only compute button need to be able to perform this computation of invoice details.

  • NSUITE-103157
    Allocate Only orders cannot be processed in Invoice 3PL Orders Post-Settlements Queue even though they display on list.

  • NSUITE-103233
    Given a 3PL passthrough billing order that only has manual invoice details (no rates will generate invoice details), the post-settlements worker is unable to create the invoice for the order when no charges come from the passthrough setup.

  • NSUITE-103234
    3PL Billing - Benchmark Window - Improve the UI/UX of the Benchmark Window that is launched via the Screen Designer button in Trip Folder.

  • NSUITE-103520
    GEH Error occurs selecting 3PL Compute Charges when setup for Pass Thru Qty Trip Folder New

  • NSUITE-104734
    3PL Billing For Buy/Sell Scenarios: When using ALLOC rate mode, the tariff description (Charge Description field on the Maintenance screen) does not override the charge description on the invoice detail. It keeps the description of the charge type.

  • NSUITE-104765
    OrdRateMode in Trip Folder not displaying the correct information for consolidated orders, shows UNKNOWN when the order has a 3PL Bill To assigned.

  • NSUITE-104938
    In regards to 3PL Billing. For Pass-Thru: The way that the pass-thru logic works requires that we look at the cost details and then join to a few tables to get back to the paydetail description.

  • NSUITE-200721
    When pay is generated by the 3PL billing process, the trips that contain 3PL pay details do not show in the Settlements Trips Audit Queue window.

  • NSUITE-200752
    TM Billing process is failing to create invoices due to trips being in an active record lock status.

Brokerage

  • NSUITE-96880
    Merge External Equipment and Company Carriers into combined view rather than the current stored procedure. Users need to see Company Carrier info, External Equipment, and Board Carrier resources all within one planning/covering screen.

  • NSUITE-97845
    Problem: Customer is getting an error in the tracking board after an upgrade to 16.10.118 from their previous 14.21.56 where when they right click on a trip in their Tracking board and select "Pay Advance" they get the following error: Exception Info: Exception has been thrown by the target of an invocation.

  • NSUITE-100415
    Opening the ACS window for a trip with a carrier assigned, selecting the Print check-box, and clicking the Save icon is no longer prompting the user with the Carrier Confirmation Report window from which they can print the confirmation sheet. This changed after an upgrade of TMW Operations.

  • NSUITE-102200
    In Covering/Tracking Board, utilize UpdateStops option to create Check call, the last CC City on the grid, displays the CITY only, not the city, state as displays when creating a check call through check call option.

  • NSUITE-102769
    When a load is split between a company asset on the first leg and a carrier on the second leg the trailer associated with the trip is not populating the trailer field in the ACS screen. Unable to save the assignment to carrier in the ACS screen until the until the trailer field is populated.

  • NSUITE-104316
    The Executing Terminal is not assigning when assigning a carrier on the ACS window. This autopoulates in TMWSuite and TMW Operations, but does not populate when using the Company Planner ACS window. Customer does not want to manually fill.

  • NSUITE-104438
    Tracking Board > Update Status window - If you open window and do nothing in it, when you close window, it asks you to save.

  • NSUITE-104443
    Customer has added a tab on the Tracking Board. With that tab present, you can not default the layout to the Stops tab in the Edit Trips section of the Tracking Board. In order to initiate the Stops tab, you must click on it.

  • NSUITE-105409
    User is receiving message "You have some uncommitted changes. Would you like to save these changes?" when trying to click from one trip to another trip in the Broker_Cover_Tracking board and Cover_Tracking board of the Company Planner.

  • NSUITE-106666
    When you create a driver accident in PB File maintenance it doesn’t populate the driverAccident.dra_source field in the db (value indicates type of resource, either DRV or CAR for Suite). When we then open accidents in Ops, we can’t find that record because of the missing data.

  • NSUITE-200527
    Dragging an available order from a parent to a child within the Branch Tree in the Company Planner Brokerage board is not assigning the Executing Branch to the trip.

  • NSUITE-200562
    ACS window does not compute carrier pay, throws an error.

  • NSUITE-200594
    When attempting to retrieve results in the External Equipment tab using DAT Interactive, the application throws an error stating "startIndex cannot be larger than length of string."

  • NSUITE-201390
    GEH error is thrown when sending a Load Assignment for the second leg of a split trip.

  • NSUITE-201943
    Email address is not written to confirmation_history table from ACS window (SSRS).

Common dispatch features

  • NSUITE-100169
    The customer has identified inconsistencies in the Asset Assignment window when working with an order that has a BMT/DMT followed by a HPL. When an MT stop is selected and the asset assignment window is opened, the MT trailer will display in the Trailer 1 field.

  • NSUITE-101416
    When you have more than one trailer in the trailer 1 column on a leg and update an order, the Trailer Drop Maintenance window keeps popping up. This should only happen when you have multiple trailers in the different "trailer buckets", trailer 1, trailer 2, trailer 3, etc.

  • NSUITE-101979
    Removed misleading dialog box when using profit and loss.

  • NSUITE-102175
    Within the Appointment Scheduler, if there is no contact on a company (shipper or consignee) and one is added via the "Manage Contact" access on the stop location section. User must close the Appointment Scheduler and reopen to have the new contact available. The drop-down is not accessible until that step has occurred. This issue does not occur in the Bill To section—​only the stop section.

  • NSUITE-103112
    Bill to set as Rate Order by Move issue. In .Net Operations, if an order is pre-rated or the linehaul charge is edited in the Profit and Loss tab, the Linehaul line is saved to the database as an invoice detail row. If there are multiple orders on the move, this causes problems for Bill To’s set as Rate by Move.

  • NSUITE-103371
    The INI setting "InvoiceStatusEditLocks" causes an issue on certain trips (consolidated and cross docked) where the user is not able to complete the stops for a trip that has not been completed and invoiced. We need to find a way to make this possible.

  • NSUITE-103859
    When putting storage events on park and hook split trips using DLT/HLT events, the storage event is created but there is no order/move number associated with the storage event or listed on the process storage billing screens.

    The Begin Empty and End Empty Split types also do not associate an order/move number listed on the process storage billing screens.

    When using IDLT/IHLT with split trips does not popup the Trailer Storage Management dialog box. The IDLT/IHLT events were not programed as part of the Trailer Storage process.

  • NSUITE-104090
    stp_ord_mileage_mtid is not getting set when calculating mileage. It appears that the stop bill to miles is overwriting the mtid. Additionally, if you open an existing order that does have a stp_ord_mileage_mtid and make a change to the order, the stp_ord_mileage_mtid gets set to null.

  • NSUITE-104792
    If a manual pay detail exists and pay is then auto computed via the Profit and Loss panel, the Pay To column for the existing pay detail is updated from a valid value to blank (NULL).

  • NSUITE-104946
    Message displays: Unable to remove order xxxx for the following reasons: You may not remove the source order from the consolidation. System does not allow user to remove secondary order from consolidation.

  • NSUITE-104981
    Issue with trailer type rating. Have created order and set (orderheader.trl_type1) to a value. Have created rate with the trailer type. With that scenario, the rate properly pulls in Ops. If I then place a trailer on order that has a different trailer. If I then place a trailer on order that has a different trailer type (legheader.trl_type1) on it, the rate fails to pull because it is using the trl_type from legheader rather than the one on orderheader.trl_type.

  • NSUITE-105028
    The Asset Assignment window is not properly defaulting the trailer for the dead head leg when the primary leg begins with a HPL stop. When the tractor is assigned, the prior trailer is assigned to the primary leg instead of the dead head leg. The trailer field for the dead head leg is left as UNKNOWN.

  • NSUITE-105396
    Check Calls - The ETA is not calculating - The issue is that only certain Rand IntelliRoute supports this functionality. Need to add a message that if no miles are returned, then it cannot calculate the ETA.

  • NSUITE-105421
    Receiving "Error Loading Layout" errors when opening the Appointment Scheduler window and when switching various grid layouts. The grid layouts are setup correctly and are associated to the appropriate SQL view.

  • NSUITE-105489
    Invoicing - Quantity - When the order is opened within Invoicing, the quantity is showing as zero. If you open it within TMW Operations, the quantity is there. If you re-compute in Invoicing, the quantity re-displays. In looking into the issue, the orderheader.ord_ratingquantity is not set, which is how Invoicing is populating this field.

  • NSUITE-105605
    Check Call - Unable to add a check call to an empty move. The user gets a message 'No assets for checkcall - No assets have been assigned to trip: xxx. You must have a driver, tractor, trailer or carrier to create a checkcall'.

  • NSUITE-105650
    End users are receiving Out of Memory exception errors that result in an application crash when working in the Consolidated Load Builder window.

  • NSUITE-105870
    Cannot actualize EBT stop after DLT for storage until the storage is released

  • NSUITE-200006
    The Asset Assignment window is not auto populating the driver ID and tractor ID based on the driver/tractor pairing when the tractor ID or driver ID is populated.

  • NSUITE-200089
    Prior Commodity Rules And Trailer Wash - Client is using prior commodity rules to prevent commodity class from being loaded into a trailer without a trailer wash occurring first. When a dispatch empty move is used to wash the trailer, it is not clearing the prior commodity preventing the trailer from being assigned to the load.

  • NSUITE-200156
    Error when deleting the PaperworkMisc table

  • NSUITE-200157
    Carrier Profile - car_carrierwatch_montiored option is not available - Customer should be able to select the carrier watch monitoring type within Carrier Profile. Currently the car_carrierwatch_montiored option is not available within the Carrier Profile in Oprerations> Carrier Profile.

  • NSUITE-200246
    Users are not able to consolidate an available cross dock movement to a split trip when the other portion of the cross dock is completed and the trailer assigned differs.

  • NSUITE-200256
    Issue with BlockEditLevelAfterStl TTS50.ini setting - When BlockeditLevelAfterStl is set to LEG and you have a split trip, the non-settled portion of the split becomes non-editable because of an error message referring to the first leg of the trip.

  • NSUITE-200290
    When copying a trip in TMW Operations, the Booked By and Booked Date fields are not updated to the user who copied the trip and the current time stamp of when the trip was copied.

  • NSUITE-200302
    The Invoice Charges data grid on the Profit and Loss window does not properly default custom saved grid layouts when the Trip Folder is opened. User must manually load custom grid layouts via the right click menu.

  • NSUITE-200321
    Asset Assignment window does not recognize record locking

  • NSUITE-200324
    Issue with Checkcalls tab in .Net Operations > Trip Folder > Checkcalls not having a no-lock on query when you retrieve them.

  • NSUITE-200496
    Load Builder Broken Filter - Seeing random but regular issues with the load builder not moving orders down to the trips sections when users plan their orders (car inventory). Load Building is the life blood of Auto Haulers and this is causing confusion with actual inventory levels and users; it mistakenly tries to plan orders more than one time.

  • NSUITE-200593
    Do not update UNKNOWN asset with location details during check call processing

  • NSUITE-200709
    When a trip is split and the first leg ends with a HMT/EMT and the second leg begins with a BMT/DMT, the trailer being assigned to the HMT/EMT is cascading down to the BMT/DMT incorrectly.

  • NSUITE-200790
    The INI setting "InvoiceStatusEditLocks" causes an issue on certain trips (consolidated and cross docked) where the user is not able to complete the stops for a trip that has not been completed and invoiced.

  • NSUITE-200801
    Assets (driver/tractor/trailer) are being auto assigned when consolidating two available orders that contain cross docked stops.

  • NSUITE-200826
    The customer is experiencing very poor performance when working with large consolidated cross-docked orders in the application. This will often result in an Out of Memory exception error and the application will crash.

  • NSUITE-200836
    System does not allow user to enter data in reference number field when they have ADD privilege.

  • NSUITE-200874
    Embedded Website is not holding in any of the profile windows

  • NSUITE-200878
    Cross Docking Features causing corruption in TMW Operations - Problem: Users are unable to cross dock the orders on movement 3016 from TMW Operations because when they do, it corrupts the movement and provides a 'Move 3016 is not found' error message.

  • NSUITE-200913
    The tractor is remaining assigned to trip despite it being set to 'UNKNOWN' via the Asset Assignment window during the planning process. This occurs when planning a trip via the Planning Worksheet, or Trip Folder> Asset Assignment window.

  • NSUITE-200955
    Dispatch Empty Move missing Driver - When creating a Dispatch Empty Move, the Leg is missing the Driver even though it is showing on the Assignment Form.

  • NSUITE-200983
    Trips to be consolidated are being duplicated in the order pane of the Consolidated Load Builder when dragging a trip from the order pane to the trips grid and then back to the order pane again.

  • NSUITE-201008
    TMW Evolution folder - The functionality is to provide a list of recently used search values in scrolls.

  • NSUITE-201044
    Out of memory reported using consolidation manager with cross docked movement

  • NSUITE-201079
    Error occurs when attempting to actualize remaining part of order

  • NSUITE-201093
    Deadhead BMT/DMT Start Times are not defaulting to a time prior to the HPL Trailer within the asset assignment window

  • NSUITE-201122
    The Invoice Charges data grid on the Profit and Loss window does not properly default custom saved grid layouts when the Trip Folder is opened.

  • NSUITE-201150
    A message stating that the selected stop has been updated elsewhere pops up when attempting to create a new stop schedule via the Appointment Scheduler. The user clicks "OK" to refresh the screen and the message pops continuously.

  • NSUITE-201168
    Pay is not recomputing after orders are split when in a Started status. Pay does not recompute when brought into Settlements.

  • NSUITE-201171
    A "Cannot Insert Duplicate Key" error is preventing the save of an order when the [Order]RateSettlementsOnSave INI setting is enabled and route pay is computed.

  • NSUITE-201739
    Non System Admin users who have access to Asset Profiles (Driver, Tractor, Trailer, Carrier) should be able to add/remove/or update any expiration regardless of the expiration code.

  • NSUITE-201825
    Drivers with a lot of history are opening slowly in the Driver Profile. This can be seen with one driver specifically. This is possibly caused by Driver Management. QA was able to recreate using client’s db.

  • NSUITE-201832
    The System is allowing them to plan and start a trip without having a trailer on it. I was able to replicate this on their db using their ini.

  • NSUITE-201846
    With IgnoreTrlStart=Y, trailer validation is skipped, leading to inaccurate trips.

  • NSUITE-201856
    Driver Picture Alignment is off in Driver Management Profile.

  • NSUITE-201864
    After upgrade, Beta Customer is seeing the allow autobill checked in the Company Profile even though it is not checked in production.

  • NSUITE-201872
    Accident Point Lengths Display Issue in Ops.

  • NSUITE-201890
    Route Generator is not honoring the "Fixed" Quantity when creating new orders.

  • NSUITE-201898
    Driver Accidents - Not showing up in Accident Tabs in Ops.

  • NSUITE-201900
    Driver Msgs and Tractor Msgs are not displaying all messages from Profile.

  • NSUITE-201946
    The paperwork required field does not display when using the 'On Hold' queue.

Company Planner

  • NSUITE-95898
    When using the OpenTripFolder command as a subscription in the Company Planner and passing the lgh_number as the argument the Trip Folder is always opening with ord number as the default lookup type. This results in the Trip Folder opening an incorrect order instead of the order based on the leg number being passed as the argument. The customer requires the leg number to be passed because they have empty trips that do not have an order number.

    This is reported in TMW Operations build 15.40.174 but can be replicated in 16.10.118.

    Note: This may be related to PTS 88774. The DefaultTripFolderLookup TTS50 setting is not always honored. The Trip Folder seems to default to ord number unless it is launched from the Planning Worksheet.

Credit checking

  • INT-99466
    Unable to handle credit transactions with EFS until they put a fix on their side to correctly link the credited transaction to the original transaction. Will inform us when they get this in.

EDI

  • INT-97838
    In Operations, we are receiving an overflow error when the ord_totalweight in greater than 99,999,999. This error is causing issues with all files imported after the 'bad' file. When this happens, we cannot view the pending orders in the EDI planning work.

  • INT-101276
    eManifest is not allowing for a second trailer that is designated as a chassis to be included on the outbound 309/358 messages for ACI with a 0 amount entered for both shipment weight and count. The validation should allow for the data to be validated without warning based on the trailer type and include the equipment record in the output file.

  • INT-101481
    Validation for freight details in eManifest does not warn when commodity value is set to 'UNKNOWN'. Original Dispatch version of ACE does include specific validation for UNKNOWN commodity. Allowing the value to be sent is causing messages to be rejected.

  • INT-104228
    Issue with running multiple instances of Data Exchange, version 16.25.232. When more than one instance is running duplicate orders are being created with the same SID number.

  • INT-104540
    Inbound 204 updates for multi-stop orders are removing stops and not updating or recreating the stops when there is a change to the event type.

    An example of this would be an original 204 that includes the following stops:

    HPL Location A
    LUL Location B
    LUL Location C

    Update is received and the only change is the event type at location A( HPL → LLD). The resulting trip after the update shows only two drops:

    LUL Location B
    LUL Location C

  • INT-105057
    Issue with DX processing stops on a 204 update after TotalMail inserts a BBT event and changes the first billable stop event from a LLD to HPL.

  • INT-200078
    Issue with DX processing stops on a 204 update after Total mail inserts a BBT event and changes the first billable stop event from a LLD to HPL.

  • INT-200080
    LTSL EDI Service is slow to load - The LTSL EDI Service is taking 3 or more minutes to start up and receives an error message on the startup. The service ends up starting, but is not working correctly.

  • INT-200101
    The PostProcessTMWMileage setting is sometimes causing moves to be locked

  • INT-200214
    Issue with running multiple instances of Data Exchange, version 16.25.232. When more than one instance is running, duplicate orders are being created with the same SID number.

  • INT-200223
    When RollintoLH is set up for the EDI 210s the 210 rate is a calculation of numbers that are populated with a decimal out to four characters (.xxxx). The decimal is outputting in the file, causing issues with mapping. I believe the issue is when TMW rounds decimals, similar to PTS 88962.

  • INT-200224
    Issue with DX processing stops on a 204 update after Total mail inserts a BBT event and changes the first billable stop event from a LLD to HPL.

  • INT-200228
    The EDI grid in the planning worksheet is requiring that the end user associate a View Name to each of the custom grid layouts that exist. This cannot be done as the EDI grid is not populated based on SQL views.

  • INT-200273
    When a 204 comes in, is never accepted, then a cancellation 204 comes in and is accepted, the order is not being cancelled.

  • INT-200331
    Receiving a null object reference error when validating eManifest data retrieved from Archive

  • NSUITE-95513
    When using the Schedule/Reschedule window to make appointment changes and the order is assigned to a carrier who is configured to generate outbound 204s, an outbound 204 is not triggered when changing appointment times and saving.

    Reported in customers 15.10.165 version of TMW Operations but this has been replicated in 16.10.118 version of Operations as well.

  • NSUITE-200027
    LTL EDI214 Issues - LTL Dispatch - Two changes are required to deal with EDI issues

Expirations

  • NSUITE-104414
    In the stored procedure carrier_search_sp, there are 2 blocks of code (see below) that count up the P1 and P2 expirations. The code is currently using the value in @stp_departure_dt - which is being set to GetDate() (aka right now) earlier in the stored proc logic.

  • NSUITE-104692
    If an expiration is added to a driver that puts the driver out of service (fired/retired), and that expiration is completed, closing that expiration (rehiring the driver), this message displays when adding a new expiration to the driver: "This resource has been retired or put out of service. Ensure that this is the resource you intended to retrieve."

  • NSUITE-200585
    Non System Admin users who have access to Asset Profiles (Driver, Tractor, Trailer, Carrier) should be able to add/remove/or update any expiration regardless of the expiration code.

  • NSUITE-201739
    Non System Admin users who have access to Asset Profiles (Driver, Tractor, Trailer, Carrier) should be able to add, remove, or update any expiration regardless of the expiration code.

  • NSUITE-201759
    Code NSUITE-201739 to sprint/ship - This CAT is to ensure the fix for NSUITE-201739 gets coded to sprint/ship.

Freight Board Interface

  • INT-200087
    Import code from PTS-105447 to fix 123Loadboard bugs.

  • NSUITE-106605
    Upgrading the customers DB from 2016.15_07.0311SP23 to 2017.17_01.0102 (current Ship Build) that will be delivery with the 17.50 release causes SQL errors.

Fuel Maintenance

  • NSUITE-200632
    Express Checks being cancelled from Profit and Loss tab in Trip folder

  • INT-105083
    Make sure the cdfuelbill_layout values for:

    cfb_transdateday (cfb_columnstart should be 74 and cfb_columnend should be 2)

    cfb_transdateMonth (cfb_columnstart should be 76 and cfb_columnend should be 2)

    cfb_transdateyear (cfb_columnstart should be 72 and cfb_columnend should be 2)

    for xfacetypes 38 and 39. Currently due to a legacy bug they are swtiched and during implementation these need to swapped.

  • NSUITE-105184
    If you click on a card that has yet to be assigned. Exception Info: Object reference not set to an instance of an object. We can click OK and still assign the card

  • INT-105248
    Unable to export transaction from Fuel Import screen into Excel.

  • INT-200042
    Reefer Fuel Rebates - Problem: A customer imports fuel transactions for both diesel and reefer purchases, however, owner operators are not charged for the reefer fuel; that cost is handled by the company. The problem is .Net Fuel Import is creating rebates for that reefer fuel, and passing those rebates back to the owner operator, even though the owner operator did not pay for that fuel.

  • INT-200048
    Currency issues with fuel import.

  • INT-200120
    Fuel import creating high fee Paydetails.

  • INT-200260
    When a customer is licensed for ".NET Fuel Import" but not "COMDATA Interactive Interface" blank/missing menu items will display in the Fuel Maintenance menu.

  • INT-200262
    New changes by EFS causing invalid logins while giving cash advance

  • INT-200276
    Card advances not pre-populating card numbers

  • INT-200279
    'Fix' the EFS advance to allow for reference number to be passed like comdata does.

  • INT-200287
    Need to update the process_Driver_Advance to change the following pieces: AND crd_status = 'ACTIVE' AND crd_vendor = 'TCHI' and they need in their 15.30 build

  • INT-200322
    Issue with trip updates where it is not setting the card to active correctly when using multiple vendors and multiple legs on a move.

  • INT-200479
    Since the upgrade to 17.50 it seems like there are a large number of missing fuel transactions.

  • NSUITE-103884
    When generating a fuel solution for a split trip the second leg of the trip is generating with the last stop only. No other stops on that leg are being included. The first leg is working properly.

  • NSUITE-201092
    GEH Error opening expert fuel View Trip Fuel Solution. Also creates 70 byte request records instead of 93 byte request records.

General system setup

  • NSUITE-90195
    Gap item for TMW Operations with no workaround confirmed from Tier3.

    Customer would like to use .NET like they do TMWSuite, where they pass parameters through the custom menu to open applications. In .NET, we can pass parameters to web URLs, but not to applications.

  • NSUITE-101853
    Upon upgrade of Operation Row Level Security stops workingSee Misc1 for exampleRe-run of a portion of the Master Upgrade SQL to resolveSee Misc2Portion of error message:Window: w_rowsec_userassignment Control: dw_det Object: d_rowsec_userassig

  • NSUITE-103837
    When using the TTS50.INI Import function in System Administration, any settings that are duplicated in multiple sections of the INI file fail to import

  • NSUITE-104114
    City Profile: Create a new city (doesn’t have to be a valid city, but should start with letters that could be a valid city, e.g., BEA or FRE). Do not save. Click on the ALK button to validate the city. A window opens and a GEH error is displayed.

  • NSUITE-201181
    Liter (Vol) to Gallon (Vol) unit conversion won’t save.

Installation and upgrade

  • NSUITE-101853
    Upon upgrade of TMW Operations, Row Level Security stops working.

  • NSUITE-105624
    New DLLs from Synergize need to be tested and deployed with TMW Operations.

  • NSUITE-106605
    Upgrading the customers DB from 2016.15_07.0311SP23 to 2017.17_01.0102 (current Ship Build) that will be delivery with the 17.50 release causing SQL errors.

Layouts - Menus and toolbars

  • NSUITE-91735
    When assigning a keyboard shortcut to a menu selection in Ops, the assignment only works for active session although saved to layout with menus toggled on.

Layouts - Windows

  • NSUITE-200578
    Conditional Validity equations are not preventing the user from saving new orders in the Order Maintenance window. Conditional Validity does work properly in the Trip Folder.

Order Maintenance

  • NSUITE-97004
    When selecting the map icon in Order Entry, the routing engine malfunctions, causing errors.

  • INT-98263
    String or binary truncation issue occurs due to the following insert statement located within the fuel_transaction_queue stored procedure. This stored procedure is called from update_move/update_move_light when the CDI General Info Setting is set to Y. This was resulting in orders failing to save in the .NET Operations application.

  • NSUITE-98864
    The customer has purchased the licensing for Third Party Pay and would like the tab to be available in Order Maintenance in .NET Operations. They have Customer Services reps that do not have access to the Trip Folder who will need to enter the Third Party Pay information into the system.

  • NSUITE-201840
    Order Entry and the Window Earliest Time changing when I update the window earliest date.

Other interfaces

  • INT-200208
    Master Order Matching incorrectly overwrites min/max temperature if current temperatures are 0.

Planning Worksheet

  • NSUITE-97440
    In the Modify restrictions windows for Trips and Resources in the Planning Worksheet, the button label names are not changing based on the name set up in the Label edit window for Company, Terminal, Division, Domicile, Team Leader, Fleet, etc. Others are affected.

  • NSUITE-102177
    In the Core Dispatch application, the sort power buttons computes miles based on the origin city. In TMW Operations, the sort power button computes miles based on the pickup company/city (shipper) for the entire trip. This poses a problem when a load is split into multiple legs. If the first leg of an order is completed, the current functionality is still looking at the shipper city to compute mileage, even though the load has moved to another origin city leg.

  • NSUITE-103774
    Memory leak suspected in the Planning Worksheet.

  • NSUITE-104315
    P! (Priority 1) field does not show the correct image alert.

  • INT-200145
    Map does not work when going from TMW to Direct Route. However, if Direct Route is opened directly from the same EXE, the map displays correctly.

  • INT-200146
    When uninstalling Direct Route, it leaves multiple folders and files on the PC.

Scroll records

  • NSUITE-100610
    In the multi-asset scroll, there is not a way currently to filter by trailer 3-8 and there is no way to add this in via quick designer. Extended assets added trailers 3 - 8 to the system. All of those should be available for the multi-asset scroll.

  • NSUITE-104027
    Expiration scroll not using the customer’s Default View anymore.

TMW Rating

  • NSUITE-98490
    Ops Rating not working with Charge Unit Rule Basis

  • 101935
    Percent of revenue allocation (split trips) function now computes consistently between TMW Operations and TMW Back Office.

  • NSUITE-105343
    Tax rates do not apply to a miscellaneous invoice IF the tariff has adjusted in effect dates.

  • NSUITE-105704
    When a charge tariff is set up to pull based on the Other Type 2 (cmp_othertype2) value, the tariff will not apply when auto-computing the invoice.

  • NSUITE-200357
    If pay details exist on a trip and a user re-computes pay, the Created On and Created By columns are updated to the current date/time and current user for the already existing pay details.

  • NSUITE-200507
    Rating Engine causes slowness on Range Value Type Tariffs

  • NSUITE-200902
    A pay tariff that is configured with an Index Asset restriction on Trailer Number or Tractor Number will not apply when computed by the rating engine.

  • NSUITE-201125
    3PL Passthrough Billing - active tables not being populated for XFR pay

  • NSUITE-201134
    Billing rates that utilize a user-defined formula will not properly compute via the Profit and Loss tab in TMW Operations. The rate remains 0 or is set incorrectly which will compute a wrong charge amount.

  • NSUITE-201179
    The weight value on a freight weight invoice line haul charge is not being updated when the freight weight is changed via the application. This appears to only affect trips with multiple drop stops.

  • NSUITE-201183
    Rounding of .net formula rate causes precision loss

  • NSUITE-201851
    Secondary rate is not pulling when all of the restrictions are met.

  • NSUITE-201869
    Rating in Ops and Settlements do not match

  • NSUITE-201888
    The TMW Operations application is incorrectly setting the orderheader.ord_rate_mileagetable.

TMW-Synergize

  • NSUITE-96207
    Part 1: In Trip Folder, when you open Trip Folder with the Synergize tab as part of the default layout, the system looks for all related Synergize paperwork, even though no order is even requested. This significantly impacts performance for loading the Trip Folder, because it unnecessarily looks for scanned images that do not exist. Continuing with the same issue.

    Part 2: In Trip Folder, when a user opens an order with the Synergize tab as part of the default layout, the system looks for all related Synergize paperwork, even though user has not requested any Synergize paperwork. This significantly impacts performance for loading the trip information, because it unnecessarily looks for scanned images when it may not interest the user

  • NSUITE-104716
    Synergize control is losing the visibility of the docs. Mostly happening in the control on the Carrier profile. It loses the value of the carrier id after the initial load. If the user retrieves another carrier, it will stay and it does not reload the control.

  • NSUITE-105321
    Synergize control is losing the visibility of the docs. Happening on the Trip Folder. (PTS 104716 fixed an issue on the Carrier Profile.) Load an order. Stay on the Trip Info tab. Wait until the 'Loading' is done on the Synergize control. Click on the Synergize tab. The docs will be there. Then they disappear. Synergize control is losing the visibility of the docs.

TotalMail

  • NSUITE-105549
    Add (nolock) to tblMessages

  • NSUITE-105571
    TM Messages 1- Click on the TM Messages tab in the Trip Folder 2- Double click on a Loaded Call line 3- Click in the Error Text section 4- Click on Alt+Tab 5- GEH Error "Can’t access SelectionLength unless the Editor is in edit mode."

Trip Folder

  • NSUITE-94280
    \.Net Operations is not correctly updating the trailer status when a DRL event is completed but the PUL event has not yet been actualized. The system shows the AVL trailer status when it should be SPU. This does work correctly in the Core Dispatch application.

    The incorrect trailer status causes users to assign a trailer when it is not avaliable for assignment.

  • NSUITE-97840
    In the Trip Folder, the Load Requirements tab is ignoring column security restrictions set up at the custom grid layout level. When the custom grid layout is loaded a second time manually, the column restrictions then apply correctly.

  • NSUITE-98048
    Receiving an error loading layout message when attempting to load custom grid layouts from a SDL file.

  • NSUITE-99682
    In the Trip Folder, the OrderReferenceNumberControl displays the incorrect reference number type qualifier to the left of the reference number when switching between orders. This occurs when the two orders have different reference type qualifiers set at the order header level. The reference type qualifier will update to the correct value once the user clicks the red View button.

  • NSUITE-99952
    The issue is that the Proc [image_invoicedata002_splong] takes only the first 10 paperwork sequences and the customer is using more than 10 paperwork types. This causes the proc to return nothing when the doc type returns anything over a 10 bdt_sequence from the billdoctype table.

  • NSUITE-102864
    When a user creates a fuel solution and adds or inserts a stop, the city field is a freeform text. This field should be a city instant best match field bound to the city table.

  • NSUITE-102953
    Disable the upper fields in the trip folder if there is no leg present on the move. Allow the tabs to be viewed but nothing to be created until the leg exists.

  • NSUITE-103866
    This issue revolves around the supporting docs grid layout. When you add the Attached_BC and Attach_MISC fields to the grid and save the layout, it breaks the field format of Req. For Application and Req. For Freight Event. It changes the field from a drop-down menu with options for Both, Invoicing & Settlements to a text field. The only way you can define Req. For Application and Req. For Freight Event is by manually typing the Abbr. associated with the value desired. For example, if I wanted to say that a Doc type is required for invoicing, I would have to put the letter I in the text box in the grid.

  • NSUITE-104208
    When opening orders in the Trip Folder, not all data elements refresh. If you have an existing order open and then open another order, the reference type doesn’t change even though the reference type on second order is different. If you open a different order by driver, the order number doesn’t refresh to the new order at the top of the Trip Folder tab.

  • NSUITE-104873
    On consolidated orders, the revenue type values of the primary order are still showing when you click the > key to view the second order of the consolidation. If you save the order, the system updates the second order’s revenue type values to match the values of the first order. This behavior is exhibited when the ContractMgmt (Bill To Relations) GI setting is enabled and the default Trip Folder screen design has been modified.

  • NSUITE-105019
    When clicking on CurrentLegsList control in the Trip Folder, the user is sometimes getting a GEH error.

  • NSUITE-105468
    When the StlAssetInDispatch General Info setting is enabled, copying a trip with pay details and choosing the option to copy pay results in the pay being duplicated on the copied order.

  • NSUITE-105583
    When attempting to add a return empty split on a trip that has been split with a park and hook, the system does not allow the save due to an Event Code Validation error on the DLT stop. The error states:

    "Trailer Drop stop #: STOP NUMBER at COMPANY NAME must drop AT LEAST one Trailer."

  • NSUITE-200303
    Unable to open an empty move in the Trip Folder

  • NSUITE-200304
    After a different trip is opened in the Trip Folder via the Current Leg List control by double-clicking on an item in the list, the user cannot open another trip after the order is refreshed unless the trip is re-retrieved manually.

  • NSUITE-200511
    Index was out of range exception error is thrown when deleting stops to remove an empty leg from a trip. The trip can be saved after clicking through the error.

  • NSUITE-200822
    Opening Asset Assignment window in Trip Folder with Split Trip order and DHCheckbox TTS50 setting, set to 1, you receive errors.

  • NSUITE-200853
    GEH when using multiple trailers - When working with multiple trailers, a primary key violation is thrown during trip save.

  • NSUITE-201185
    GEH Error in Trip Folder / Asset Assignment - GEH Error in Operations Trip Folder after clicking OK in the Asset Assignment window and choosing a tariff to apply from the duplicate rates window.

  • NSUITE-201871
    Planning Worksheet drag/drop is incorrectly assigning trailer when last stop is non-billable.

  • NSUITE-201880
    Planning Worksheet in-line edit changes lost if going directly to asset assignment.

  • NSUITE-201854
    Customized tabs embedded in Trip Folder not editable once ivh_invoicestatus='XFR'.

  • NSUITE-201896
    Error loading layout issue when Global Default on Tractor/Carrier grid in the Planning Worksheet.

  • NSUITE-201977
    Hyperlinks are disabled in Trip Folder.

Trip Planner

  • NSUITE-105495
    When two users are working in the Trip Planner at the same time, and they are using the same Shift Scrolls view, if one user removes a planned trip from a driver’s shift and saves their changes the other user will receive the following error when they plan a trip to a different driver and then save their changes: 'Someone changed the move while you were editing. The save did not complete'. However, the Save Warning error references a movement number that neither user was modifying.

  • NSUITE-200239
    After upgrading to Operations 17.25.3, refreshing the Trip Planner is taking longer than expected and appears to be unresponsive.

WorkCycle

  • INT-200205
    Need an Activity created for OOS process that comes from Carrier411