SendSuite Live version 7.16.00 Release Notes (February 16, 2017)

SendSuite Live Release Notes for version 7.16.00 (February 16, 2017).
Products affected: SendSuite® Live


This section describes the major new features or enhancements that are included in this release.

USPS Rate Changes Verified

The product has been tested against USPS rate changes. No product changes were required.

Purolator Rate Changes Verified

The product has been tested against Purolator 9.1.2 rate changes. No product changes were required.

ERR. Pitney Bowes USPS Vendor Code Added to Shipping Services File (SSF)

USPS has assigned a vendor code 7560 to SendSuite Live. The Shipping Services File has been updated.

PB Shipping API – USPS. Setting for Minimal Address Validation

There is a new Shipment Server configuration setting, PB Shipping API Minimal Address Validation. The default is False. When set to True, street address checks are less stringent. Specifically, it will:

  • Perform a basic format check (building number and street name).
  • Correct misspellings for recognized street names and abbreviations.
  • Allow unrecognized street names to be submitted provided that city, state and zip code are correct.



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

USPS. PDX Filename Download Listings Now Case Insensitive

The USPS filenames returned by PDX can be mixed case. To ensure all files are listed, the listing is now case insensitive.

GetRecentRecipients Stored Procedure. Standardized ReceiverEmail Size at 100 Characters

The length of the string for ReceiverEmail within the GetRecentRecipients stored procedure is now 100 characters in both temporary tables. Previously, one table had it set to 50.



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

Cartonization. Updated Endpoints

URLs used by cartonization have been updated in this release. These settings are not exposed in Shipment Server Configuration.

Customer Charges. Restored Legacy Behavior

The handling of Customer charges in both the database and transaction response has been corrected to restore legacy behavior. In earlier versions, passing a TotalCharge in a request would override the CustomerTotalCharge stored in the database and returned as part of Customer elements. This behavior has been restored.

Task History Table. Manage Size Automatically

The Task History table is now automatically maintained by the Task Agent service during its clean up sequence, and only 30 days of history will be stored. The 30-day setting is not configurable. As this table could be very large, note that all rows are truncated during the update. Post upgrade there will be no rows in this table. This is a possible breaking change, if you use the contents of this table for some other function, or if you want to hold history beyond 30 days. Post upgrade there will be no rows in this table, and going forward, it will only hold 30 days of history. If you need the contents of the Task History table, take steps to preserve the data both prior to update, and post update, beyond the 30-day clean-up. See the Possible Breaking Changes section of these release notes for a summary of all such changes in this release.

Shipment Server. Custom Document Viewer. Added Search by Output Identifier (OutputID)

You can now search by output identifier (OutputID). The search fields are now: OutputID, CarrierName, and Output Type Description. As part of this, due to issues with mismatched results and performance, TimeLog has been removed.

UPS Consolidated. Paperless. Resolved Label Issue

An issue has been corrected with the database storage of labels for paperless UPS transactions. The backup document is now associated with the first package label, and all other labels are correctly allocated to each package.

Consolidated Shipping. Extended ‘Generic’ Capability

Previously, a generic capability was available using the UPS Supply Chain (Generic Consolidation) option within the trailer administration controls. This option’s functionality has been preserved, but it has been renamed UPS Supply Chain, and a new Generic Consolidation option has been added. This new option is purely generic, and can produce the following document types:

  • Consolidated Commercial Invoice
  • Consolidated Bill of Lading

Both of these outputs should be set up for All Carriers, and defined as Active Reports format, along with being associated with their respective report files. The Generic Consolidation option can be used with any carrier, and with combinations of carriers within the same consolidation. However, note that this consolidation does not affect the charges associated with each shipment, and each carrier will only see the single shipment and not the others within the consolidation. As such, this functionality is useful for internally grouping shipments and producing the consolidation documentation only.

Shipment Server. Server Configuration Utility. Label Changes in the UI

In the Server Configuration Utility, changes have been made to the labels used:

  • The term SSL has been replaced by HTTPS. So for example, Use SSL with Shipment Server is now Use HTTPS with Shipment Server.
  • Under Security Settings, the first setting Enable Identification Headers has been inverted to be Disable Identification Headers. This means that all security settings should now be set to True (previously this first setting had to be set to False). Note this is just a display change. Your underlying server settings do not change on upgrade and shipments are not affected.

PB Shipping API – USPS. Reports. Enabled Zero Balance

Where applicable, reports can now start with a zero balance.

FedEx Server. Resolved Working Days Issue With DeliveryDate Calculation

An issue has been resolved with FedEx Server in relation to DeliveryDate calculations. The calculation takes the provided ShipDate and adds the TnT days returned by the carrier. It did factor in non-working days for the service concerned, but only for the end date, not the start date (ShipDate). This could lead to incorrect calculations. For example, for Home Delivery, which only operates Tuesday to Saturday, if ShipDate was a Sunday, the DeliveryDate calculation was incorrect. To resolve this, for all FedEx services, the non-working day check is now also done on ShipDate. If it is a non-working day, the starting date used in the calculation is adjusted accordingly. This does not change the ShipDate given to the carrier.



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: The Task History table is now managed automatically.

Action: On upgrade, the Task History table is emptied and going forward will only store 30 days of history. If you need the data in this table, take steps to preserve it before the upgrade. After the upgrade, if you need more than 30 days of history, take steps to protect that data before it is cleared.

UPDATED: August 14, 2021