Summary:
FedEx Integration - Set Max Length New rules for max length of Address Lines based on Service used
Ticket:
https://bigdigit.atlassian.net/browse/TMS-762
...
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
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:
Hermes Integration - Support for SMS notifications
Ticket:
https://bigdigit.atlassian.net/browse/TMS-759
Detail:
The “notificationType” in the TMS Request supports the following values:
Value | Description |
|---|---|
0 | None |
1 | |
2 | Text |
3 | EmailAndText |
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.
...