20220210 - TMS Release

Summary:
FedEx Integration - New rules for max length of Address Lines (Hong Kong)

Ticket:
https://bigdigit.atlassian.net/browse/TMS-762

Detail:
The actual printed FedEx Labels only allow 2 StreeetLines and they are truncated: 

• For SmartPost Shipments, StreetLines[0] and StreetLines[1] are limited to 30 characters.

• For all other FedEx services, StreetLines[0] and StreetLines[1] are limited to 35 characters. 

The TMS concatenates line2, line3 and line4 in the TMS Request into one line separated by commas. If any of these are null or empty it will exclude these from the concatenation. 

If the total length of the concatenated address line is greater than 30 characters for the SmartPost service OR greater than 35 characters for other FedEx services, the TMS will throw an exception: 

“Address exceeds max length“

Summary:
FedEx Integration - Currency Mappings (CurrentBody)

Ticket:
https://bigdigit.atlassian.net/browse/TMS-768

Detail:
Ability to add custom mappings for specific currencies between the ISO standard (TMS Request) and FedEx currency codes (FedEx request). This is to support FedEx’s custom implementation of currencies. As there are a number of mappings, we store these in a table in the database instead of doing this directly in the code. We could use this table in the future for other Carrier Providers who also require a different currency code than the ISO3 standard.

Summary:
FedEx Integration - Signature Option (Canyon)

Ticket:
https://bigdigit.atlassian.net/browse/TMS-770

Detail:
Added support for the following FedEx Signature Options:

• ADULT - FedEx will obtain a signature from someone at the delivery address who is at least the age of majority in the destination country.

• DIRECT – any person at the recipient’s address may sign for delivery. If no one is at the address, FedEx will reattempt delivery.

• INDIRECT - FedEx obtains a signature in one of three ways: (a) From someone at the delivery address (b) From a neighbour, building manager or other person at a neighbouring address (c) The recipient can authorize release of the package without anyone present.
  
  

Summary:
FedEx Integration - Handle FedEx timeouts

Ticket:
https://bigdigit.atlassian.net/browse/TMS-753

Detail:
We intermittently do NOT receive a response back from FedEx when attempting to call a Close Request. This is an issue with the endpoint at FedEx. We now show a more descriptive error message when this happens so the user can attempt to try again.

Summary:
Hermes Integration - Support for SMS notifications (Grind Coffee Roasters)

Ticket:
https://bigdigit.atlassian.net/browse/TMS-759

Detail:
The “notificationType” in the TMS Request supports the following values:

For Hermes:

If TMS Request → “notificationType” == 2 OR 3

AND

TMS Request → “deliveryContact.phone“ is NOT NULL OR EMPTY

We will then request SMS notifications to be sent by Hermes.