SystemsLink 2019

These release notes contain:

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

A PDF version of these release notes is available.

2019.4

Enhancements

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

Search for contacts in SystemsLink RESTful (API-417)

A search endpoint is now available for contacts in SystemsLink RESTful.

Enhancements to EventCodeService (API-726, API-812)

The following methods have been added to the EventCodeService:

  • GetAllEndDeadheadEvents

  • GetAllStartDeadheadEvents

  • GetAllDeliveryEvents

  • GetAllPickupEvents

In addition, the following properties are now included in the EventCode object:

  • IsRetired

  • IsBeginDeadheadEvent

  • IsEndDeadheadEvent

  • MileTypeFromEvent

  • MileTypeToEvent

  • IsDriverPay

  • FreightEventType

  • LikeEvent

Allow re-rating of Pay Details (API-726)

Fixed an issue with the CalculatePay method in APIWCFServices where it unintentionally removed pay details that met these conditions:

  • The pay detail was not marked as manual

  • The pay detail had HLD status

  • The pay detail had a tariff number

Only pay details automatically created by the rating engine were meant to be deleted by the CalculatePay method.

Now, the CalculatePay method will not remove these pay details. Instead, the rating engine will manage which pay details should be updated, added, or removed

Performance changes to ShiftPlanningService (API-793)

The following methods in the Middle Tier ShiftPlanningService have been changed to increase performance:

  • SaveShift

  • ShiftLogin

  • ShiftLogout

Encryption support for configuration files (API-807)

SystemsLink now supports the encryption of sensitive sections in its web.config files.

To simplify management of these encrypted settings, encryption and decryption tools are now included with SystemsLink.

Get cities using name, state, and zip code in Middle Tier (API-833)

Previously, the CityService in MiddleTier supported retrieving a particular city by its database ID or a string containing the city’s name, state, and county.

Now, CityService also supports retrieving a city by supplying its name, state, and zip code as parameters. This is useful in cases where the city’s zip code is known but the county isn’t readily available.

New properties for the Middle Tier NoteService (API-871)

The following properties have been added to the Middle Tier NoteService:

  • SentBy

  • ForwardedFrom

  • LastUpdatedBy

  • LastUpdatedDate

  • AutoNote

  • OrderNumber

  • CompanyId

Resolved issues

The following bug fixes are included in this release:

  • API-617
    Fixed an issue with inserting stops through DispatchHorizon where the sequence of the inserted stop and existing subsequent stops was not resequenced.

  • API-796
    Fixed an issue with the Middle Tier CompanyService GetClosestCompany method where it could return incorrect locations. This occurred if the database used seconds as a unit of measurement for the latitude and longitude of cities.

    GetClosestCompany now checks the General Info Table setting CityLatLongUnits to determine the latitude and longitude units used for cities in your database.

2019.3.2.56

Enhancements

Get Cities using name, state, and zip code in Middle Tier (API-833)

Previously, the CityService in MiddleTier supported retrieving a particular city by its database ID or a string containing the city’s name, state, and county.

Now, CityService also supports retrieving a city by supplying its name, state, and zip code as parameters. This is useful in cases where the city’s zip code is known but the county is not available.

2019.3

Enhancements

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

CRUD and Search for GeofenceService (API-144, API-145, API-146)

Create, read, update, delete and search methods were added to the Middle Tier GeofenceService.

Update time zone and mileage lookup type for Company (API-475)

TimeZone and MileSearchLevel for a Company are now exposed through the Middle Tier CompanyService and can be updated.

Resolved issues

The following bug fixes are included in this release:

  • API-534
    Fixed an issue where negative longitude values received from MacroPoint were not reformatted for storage in our database. This caused locations to be displayed incorrectly when presented on a map.

  • API-562
    Fixed an issue in the DispatchHorizon where all the stops in a copied order would sometimes have the same arrival/departure time.

  • API-602, API-603
    Fixed issues with saving pay details through the Middle Tier PayService:

    • Quantities recorded by a driver were being rounded to the nearest integer. Quantities will now be saved as a decimal.

    • Work periods recorded by a driver were being overwritten to a default date. Work periods will now be stored as recorded by the driver.

2019.2.3.55

Enhancements

New properties for the Middle Tier NoteService (API-871)

The following properties have been added to the Middle Tier NoteService:

  • SentBy

  • ForwardedFrom

  • LastUpdatedBy

  • LastUpdatedDate

  • AutoNote

  • OrderNumber

  • CompanyId

2019.2.3.52

Resolved issues

API-796

Fixed an issue with the Middle Tier CompanyService GetClosestCompany method where it returned incorrect locations. This occurred if the database used seconds as a unit of measurement for the latitude and longitude of cities.

GetClosestCompany now checks the General Info Table setting CityLatLongUnits to determine the latitude and longitude units used for cities in your database.

2019.2.3.43

Enhancements

Get like events from EventCodeService (API-726)

Custom event codes retrieved using the EventCodeService in Middle Tier will now include the LikeEvent property. This property specifies the system event code used as a base for a custom event.

2019.2.3.4

Resolved issues

API-626

Fixed an issue where routes exported from the DirectRoute Export tool could not be re-uploaded on the same day they were initially uploaded.

2019.2.3.37

Resolved issues

API-602, API-603

Fixed issues with saving pay details through the Middle Tier PayService:

  • Quantities recorded by the driver were being rounded to the nearest integer. Quantities will now be saved as a decimal.

  • Work periods recorded by a driver were being overwritten to a default date. Work periods will now be stored as recorded by the driver.

2019.2.0.20

Enhancements

Order volume exposed through SystemsLink DispatchHorizonService (API-473)

The total volume for an order is now exposed as a read-only property, TotalVolume, when requesting an Order object from the DispatchHorizonService.

2019.2.0.18

Resolved issues

API-529

Fixed an issue where saving Orders through DispatchHorizonService without OrderInfo caused an exception.

2019.2

Enhancements

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

Add a DelayIncident service (API-168, API-287)

Add a new DelayIncident service which includes methods to retrieve DelayIncident details by leg and order-header numbers, update and save a delay incident, and delete delay incident by delayIncidentRowId.

Dedicated TMW.Suite Operations Invoice and Pay Locks (API-387/API-396)

SystemsLink in addition to the normal TMW.Suite invoice and pay locks SystemLink now also honors the invoice and billing locks that match the TMW.Suite Dedicated Operations.

Create a "Get Closest City" method (API-432)

A GetClosestCity method was created for the CityService of SystemsLink which takes a latitude and longitude to locate the nearest city. This method will be called by FleetConneX in the next FleetConneX release.

Send commodity profile data outbound (API-482)

Exposed the following fields in the Commodity object of the CommodityService in SystemsLink:

  • SpecificGravity

  • DotName

  • HazNum

  • AdrPackagingGroup

  • HazardousClass

Expose ord_extraInfo fields from OrderHeader table (API-394)

Added OrderInfo object to hold a list of extra information in the Order object of DispatchHorizonService and OrderService in SystemsLink.

New setting added in the web.config of the Internal SystemsLink (API-174)

New setting added in the web.config of the Internal SystemsLink:

  • UseClientLatLong:valid values: True, False; default value: False.

  • True: (new logic) save the passed in latitude and longitude values when saving check-calls.

  • False: (old logic) resolve the latitude and longitude values from the city table when saving check-calls.

Resolved issues

The following bug fixes are included in this release:

  • API-172
    Fixed Carrier411 to support 8 Character MCnumbers.

  • API-174
    New setting added in the web.config of the Internal SystemsLink:

    • UseClientLatLong:valid values: True, False; default value: False.

    • True: (new logic) save the passed in latitude and longitude values when saving check-calls.

    • False: (old logic) resolve the latitude and longitude values from the city table when saving check-calls.

  • API-327
    For SaveDispatchStop, the date is cascaded only if the stop’s arrival time, or departure time, or location of the stop has been changed.

  • API-332
    Finding the Closest Company based on Latitude and Longitude may be slow.

  • API-334
    Resolved an issue with CopyOrder that was causing errors. If a driver completed a circle of service on a copied order and attempted to copy another order, an error is no longer received due to time conflicts on the newly copied order.

  • API-431
    A GetClosestCity method was created for the CityService of SystemsLink which takes a latitude and longitude to locate the nearest city. This method will be called by FleetConneX in the next Fleet ConneX release.

  • API-474
    Resolved an error received when querying a specific carrier.

2019.1.1

Enhancements

Send commodity profile data outbound (API-482)

Exposed the following fields in the Commodity object of the CommodityService in SystemsLink:

  • SpecificGravity

  • DotName

  • HazNum

  • AdrPackagingGroup

  • HazardousClass

Expose ord_extraInfo fields from OrderHeader table (API-469)

Added OrderInfo object to hold a list of extra information in the Order object of DispatchHorizonService and OrderService in SystemsLink.

2019.1.0.31

Enhancements

Order volume exposed through SystemsLink DispatchHorizonService (API-473)

The total volume for an order is now exposed as a read-only property, TotalVolume, when requesting an Order object from the DispatchHorizonService.

2019.1.0.29

Resolved issues

API-529

Fixed an issue where saving Orders through DispatchHorizonService without OrderInfo caused an exception.

2019.1.0.27

Enhancements

Send commodity profile data outbound (API-482)

Exposed the following fields in the Commodity object of the CommodityService in SystemsLink:

  • SpecificGravity

  • DotName

  • HazNum

  • AdrPackagingGroup

  • HazardousClass

Expose ord_extraInfo fields from OrderHeader table (API-469)

Added OrderInfo object to hold a list of extra information in the Order object of DispatchHorizonService and OrderService in SystemsLink.

2019.1

The AssetLog service replaces the deprecated Asset service for both SystemsLink and SystemsLink external APIs. Any new applications should use the AssetLog service.

For FleetConneX, the ImageCapture service facilitates image storage and retrieval.

We have updated our company name and logo to the Trimble brand.

Enhancements

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

SystemsLink

WE-222698, WE-223250

Add new ImageCapture service.

SystemsLink and SystemsLink external

WE-223142

Add new AssetLog service and deprecate Asset service.

Resolved issues

The following bug fixes are included in this release:

SystemsLink

API-147

SystemsLink fix for multithreading stability.