SystemsLink 2020

These release notes contain:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

A PDF version of these release notes is available.

2020.4.1.81

Resolved issue

TTESUITE-10487

In the Hours of Service service, the RuleResetDate database field was not updated after the XML was completed and submitted.

2020.4.1.80

Resolved issue

TTESUITE-201235

For split trips where the first leg contained settlement data, the system was unable to update departure times on the second leg.

2020.4

Enhancements

The following new features, improvements, and optimizations are included in this release:

RESTful PayToService (API-424)

A new PayToService has been added to SystemsLink RESTful to provide CRUD operations.

Internal session implemented in SystemsLink External (API-1275)

An internal session has been implemented for SystemsLink External. It improves the performance of the CarrierCsaApi services.

Resolved issues

  • API-1139
    Each invoice detail saved for a given order (identified by the order header number) using the SaveInvoiceDetail method was given the same sequence number, 9991, instead of a unique sequence number.

  • API-1248
    Unable to access data provided by HubTran via the SystemsLink HubTran interface.

  • API-1312
    Fixed a bug where the SystemsLink TruETA product would not execute when the TruETA product license was purchased but the full SystemsLink product license was not purchased.

2020.3.1.182

Resolved issue

  • TTESUITE-201789
    The generic imaging API did not use the current TMW Operations document handling data.

2020.3

Resolved issues

  • API-589
    A reference number on an order was not retrieved when running GetMoveByLeg for an outbound portion of the cross-docked order. The GetMoveByLeg did not supply the reference numbers, because the save dispatch request deleted them.

  • API-1155
    The logic in the constructor of NetworkLogic may cause the AppManager to fail and disable all middle-tier services.

  • API-1211
    SystemsLink security access was enhanced to give FleetConneX access to additional methods within SystemsLink and SystemsLinkFuel.

  • API-1212
    When the WorkCycle workflow recalculated miles for a set of stops on a trip/move, the mileage was not calculated from the first stop to the next stop.

  • API-1225
    When WorkCycle lost a connection or certain workflows failed, the WorkCycle service would stop processing. An internal restart now exists to handle these conditions.

  • API-1233
    In some cases, the installation process did not set URLs correctly in the web.config file for SystemsLink.TMW.

  • PB-200678
    When querying with the MC number for RMIS, the DOT number was not added to the carrier profile. This issue was resolved within the TMWSuite application.

2020.2

Enhancements

This release includes the following new features, improvements, and optimizations:

RESTful CityService endpoint (API-415)

A new endpoint, City, has been added to the SystemsLink RESTful. It supports the following operations:

  • GET

  • POST

    • Search

  • PUT

  • PATCH

    • NullableFieldsById

  • DELETE

Retrieval of Engage.Bid contract fulfillment data (API-874)

Now, Engage.Bid users can retrieve contract fulfillment counts and analysis via SystemsLink.

State Miles report data supplied by ALK Web (API-952)

Previously, to view mileage breakdown data on the State Miles report, you had to buy and install ALK DLLs.

Now, web-based ALK services allow you to view the data. No additional purchase is required.

Allow override of historical user in Freight Order API (API-953)

When a user creates a freight order, their user ID is stored in the HistoryDetail table. By default, this value does not change.

To override this functionality, you can add the user-override node to the FreightOrderService header. Each time a user modifies the freight order, their user ID replaces the previously stored value. This allows you to track all users who work with a freight order.

Pay To functions added to CarrierCSAService API (API-999)

A new PayTo method has been added to the CarrierCSAService API. It supports these functions:

  • Retrieve

  • Retrieve paged

  • Save

Canadian carrier support added (API-1018)

Canadian carrier support has been added to the TMW Operations RMIS interface. Now, you can look up carriers using the CVOR number.

Driver retrieval by encrypted Social Security number (API-1091)

TMW Operations now supports database encryption of a driver’s Social Security number (SSN). The SystemsLink driver search has been revised to allow retrieval of a driver by their SSN when it is encrypted within the database.

Resolved issues

  • API-587
    When notes were added, they were always given a sequence of 1. This happened even when there were multiple notes, or when the sequence was set to a different value in the XML.

  • API-681
    If reference number information was updated within DispatchHorizon, the existing sequence was not maintained. Instead, numbers were resequenced such that the last edited number was the last number in the sequence.

  • API-770
    WorkCycle updated large groups of CarrierCSA records with data (safety, insurance, etc.) from a different, incorrect company.

  • API-1003
    Performance improvements to FreightOrder updates.

  • API-1022
    Trimble Dispatch Advisor did not honor "should not have/be" or "must not have/be" in load requirements for assets that were tracked in TMW Operations.

  • API-1024
    The DBMod that created the FreightOrder ReferenceNumbers 'FO External ID', 'FOExt#' option generated a warning the first time it was run. It generated a duplicate key error the second time it was run.

  • API-1043
    After an upgrade, WorkCycle did not run the TruETA workflow on schedule.

  • API-1065
    An extra add was occurring in the historydetail table for FreightOrder.

  • API-1066
    When there were multiple FreightOrder legs in an order, the Planning Worksheet SQL view displayed unexpected extra rows for each leg.

  • API-1086
    Normally, WorkCycle should process at least one workflow several times a minute. Certain conditions occurred that caused the WorkCycle service to stop picking up workflows to execute.

  • API-1087
    The CarrierCSA window was pulling carrier data from the database before a CSA lookup.

  • API-1093
    Diagnostic switch added to CarrierWatch to gather data related to potential performance concerns.

  • API-1107
    An error occurred when calling the Get method in the CheckCallService.

2020.1

Enhancements

The following new features, improvements, and optimizations are included in this release:

RESTful CarrierService endpoint (API-410)

A new endpoint, CarrierService, has been added to the SystemsLink RESTful. It supports the following operations:

  • GET

  • POST

    • Search

  • PUT

  • PATCH

    • NullableFieldsById

  • DELETE

An older version of this endpoint, the Carrier endpoint, is still available.

RESTful CheckCallService endpoint (API-414)

A new endpoint, CheckCallService, has been added to the SystemsLink RESTful. It supports the following operations:

  • GET

  • POST

    • Search

  • PUT

  • PATCH

    • NullableFieldsById

  • DELETE

An older version of this endpoint, the CheckCall endpoint, is still available.

RESTful CompanyService endpoint (API-416)

A new endpoint, CompanyService, has been added to the SystemsLink RESTful. It supports the following operations:

  • GET

  • POST

    • Search

  • PUT

  • PATCH

    • NullableFieldsById

  • DELETE

An older version of this endpoint, the Company endpoint, is still available.

Service for re-sequencing order stops (API-640)

A new OrderStopSequenceService has been added to SystemsLink Middle Tier. This service has a single method, SaveNewSequenceAsync, which you can use to re-sequence an order’s stops.

You use a boolean parameter, calculateMileage, to indicate whether mileage is recalculated after re-sequencing the stops. If true, which is the default value, mileage will be recalculated.

This service changes only an order’s stop sequence. It does not affect move or trip segment stop sequences.

Changing the order stop sequence can significantly impact payment calculations.

Load requirement service (API-929)

You can create load criteria for companies and commodities using the new LoadRequirementDefault service.

Load criteria restrict the resources you can assign to an order based on conditions that must be met for the commodity, a company on the order, or the order itself. They can be requirements or preferences.

For instance, certain commodities may require a trailer with safety equipment.

Using the service, these criteria can be set for companies, commodities, or a company/commodity pair.

A SystemsLink RESTful version of this service is also available through the LoadRequirementDefault endpoint.

Resolved issues

  • API-815
    Completing a stop with APIWCFServices UpdateStop method will no longer leave the related leg in a started, or STD, status. The stop and leg will now be set to completed, or CMP, as expected.

  • API-912
    FreightService.svc in ExternalAPIWCFServices will now load when accessed from a browser.

  • API-928
    When working with movements in SystemsLink Middle Tier, unrelated UI events could cause performance issues and unintended results. These events are now ignored by Middle Tier.

  • API-942
    When performing a criteria search using filters, the FilterFieldName and SortFieldName properties are no longer case-sensitive. This change affects both SystemsLink Middle Tier and SystemsLink RESTful.

  • API-992
    Users licensed only for My Carrier Packets no longer require additional SystemsLink licenses to modify carrier contacts through the CarrierCsaAPI.