SendSuite Live version 7.14.01 Release Notes (November 2, 2016)

SUPPORT ITEMS

This section includes items that have been raised via Support and escalated to Development for resolution within this release.

Freight Shipments. Fixed Issue with Quote Based Shipping

Resolved an issue whereby shipping a pre-rated freight item would apply the rating options twice.

OTHER CHANGES

This section contains information about minor changes and corrections. It can include issues raised in previous releases that have been corrected.

Shipment Server. Task History Now Uses Server Time Zone

Task History times and dates are now derived from the server. Previously, they were converted to the logged in user’s time zone.

FedEx Web Services. Corrected Customs Insurance Charges Currency Handling

An issue has been corrected with FedEx Web Services, whereby the default currency code was always passed within the CustomsClearanceDetail section of the carrier request. To change this value, map the following Ship node:

• PierbridgeShipRequest/Packages/Package/International/CustomsClearanceDetail

You must map this value if you need to process an international request that has items defined in a different currency to the default.

Shipment Server. Improved Locking when Fetching Package Numbers

To ensure no duplicates are returned, we have improved the locking associated with database calls that fetch the next available package or shipment number.

TNT Express. Fixed Consignment Note Output Rule

Corrected the output rule for the TNT Express consignment note. The document now generates correctly.

Shipment Server. Profile Permissions Now Take Priority Over Any “All User” Permissions

Note: This is a Possible Breaking Change.

A significant change has been made to how permissions are selected when performing all transactions.

Since the concept of “profiles” was introduced in version 6.6, the product selected permissions as follows:

1. If a user-specific permission exists, select it.
2. If a profile permission row exists in the database row order before any All User permission, select it.
3. Otherwise, any All User permission is selected.

The product now works as follows:

1. If a user-specific permission exists, select it.
2. If a profile permission exists, select it.
3. Otherwise, any All User permission is selected.

Due to the change in step 2, profile permissions previously ignored due to their position in the database will now take effect. To ensure a seamless customer upgrade, it is very important to review the scope and impact of this change before applying the update. Any issues can be resolved by setting more specific permissions.

FedEx IPD. Removed Validation for IOR Codes Manually Provided in Ship Requests Now

The validation relating to FedEx IPD shipments has changed. An IORCode can be provided in each ship request. In all previous versions, the product validated this code and its validity for the destination country. However, this caused issues when multiple IOR codes were required for the same country. As such, all validation relating to the IOR code has been removed when one is provided in the ship request. If no code is provided, the product will attempt to find one for the destination country, and will still fail if it finds duplicates for the same country.

Configuration Onboarding API. Enhanced Toolkit including Resolution of Type Ambiguity

This work includes Possible Breaking Changes, if using the toolkit:

1. The Configuration Onboarding API has been updated to support the Visual Basic development environment. To support this, some XML request elements have been renamed to avoid clashes with underlying types. Each rename is a possible breaking change. The affected elements are:
   • Request/contact has been renamed Request/ContactDetails.
   • Request/Carrier has been removed. The existing Request/CarrierID is used instead.
   • Request/paymentType has been renamed Request/PaymentDetails.
   • Request/invoiceInfo has been renamed Request/InvoiceDetails.
   • Contact/Address has been removed. The existing address details elements are used instead (Contact/Street, Contact/Locale etc.).
2. The carrier Onboarding calls will now always return a 200 (OK) to allow any carrier messages to be returned, previously any failed attempt would return a 304 (NotModified)"

The revised toolkit is available by contacting SendSuite Live Support. Also, refer to the Possible Breaking Changes section of these release notes.

POSSIBLE BREAKING CHANGES

This section lists all changes that have the potential to break legacy functionality. Please review the contents of this section before updating any project to understand the changes that are being made and any actions that you need to take prior to applying the patches.

Change: How permissions are selected has changed. Previously ignored profile permissions may be selected.

Action: Before upgrading, review the scope and potential impact of the change and resolve any issues by setting more specific permissions.

Change: Elements in the Configuration Onboarding API have been removed, renamed or amended.

Action: If you use this toolkit, check if any of the changes affect you and revise your code where necessary.