Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Detail:
Our integration with Transsmart / nShift now supports setting the “service“ property in the Transsmart request. This can be done by setting the value to be used (DOCS / NON-DOCS / ENVELOPE) on a Carrier / Client basis for Transsmart from the “Entity Setup → Carrier Setup → Maintain Carriers” menu.

...

Summary:
Admin Panel - Partner Drop Downs ordered by Partner Name

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyTMS-851

Detail:
The following Partner drop downs in the Admin Panel are now ordered by Partner Name making it easier to select a specific partner:

  • Activities → Carrier Labels

  • Security → Users

...

Summary:
Gracefully handle FedEx exceptions

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyTMS-772

Detail:
The TMS now handles standard and non-standard FedEx exceptions.
Occasionally FedEx goes down and returns - ”Internal system error. Please try again later.”
When this happens FedEx returns a completely different XML response.
The TMS can now handle this.

...

Summary:
Migration to .NET 6

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyTMS-757

...