This section includes items that have been raised via Support and escalated to Development for resolution within this release.
FedEx Web Services. Corrected Duty Payer Mapping
The mappings relating to international duty billings have been changed for FedEx Web Services. This patch introduces the following logic:
- Sender billing will automatically assign the sender address and account number to the duty details given to the carrier. This is unchanged behavior.
- Recipient billing and Third Party billing will use the details from the “International/Duty” block, if address details or account number are provided. Otherwise, just the billing type flag will be submitted to the carrier.
The new logic allows for any combination of values to be passed to the carrier (i.e. full, partial or no address, account number or lack thereof). However, it is important to ensure that you are passing the correct sequence of values into the above nodes to ensure the carrier performs the correct billing sequence.
Note: This item introduces a number of breaking changes. Refer to the Possible Breaking Changes section of these release notes for more details.
eCertified. Added Ability to Reprint Output Items
The PierbridgePrint transaction has been extended to support reprinting ERR-based outputs using ShipmentID and PackageID parameters.
UPS API. Fixed AlternateAddressIndicator Used for Pickup
The AlternateAddressIndicator value will now be automatically set based on the address details given in the Pickup block versus the Sender address. If Street, Region City or PostalCode does not match, then the flag is set to “Y”. Otherwise, it’s set to “N”.
Note: The Pickup address vs. Sender address check ignores spacing and is case-insensitive.
End of Day. Corrected .NET Library Reference
Corrected a library file reference within End of Day process, which would result in errors when using a number of JSON-based carriers, e.g. PB Shipping API-USPS.
SendSuite Tracking. Fixed Secure Socket Layer Configuration
Corrected an issue with the link module between SendSuite Live and SendSuite Tracking not working correctly in HTTPS-only environments.
This section contains information about minor changes and corrections. It can include issues raised in previous releases that have been corrected.
Void. Fixed DisableExecution-Based Shipments
Corrected an issue with voiding a shipment processed with "DisableExecution" returning a "Failed" status.
Ship Release. Shipment ID and Package ID Always Returned
The Shipment ID and Package ID will be now returned when a shipment is released from hold, even if the release has failed. Additionally, the Transaction ID will now always return the value given in the release.
FedEx IGDD. Fixed Closing Document Printing
Resolved an issue whereby an incorrect filter would be used to find a document when closing an IGDD shipment for FedEx Server.
FedEx Server. Added Ability to Pass ITN during Consolidated Shipment Close
You can now add ITN Number in a consolidated close. This can be mapped annually via scripting, e.g. set within Consolidated Trailer Administration control, which has been accommodated with a new, ITN property.
UPS API. PaperlessCommercialInvoice Flag Now Allowed to be Set
You can now set the PaperlessCommercialInvoice flag in Ship Request to produce this document output as a PDF file.
Scale. Added Ability to Control Scale Timeout and Wait Times
The Scale Configuration Utility now has two new fields, Timeout (ms) and Wait Time (ms).
The difference between the scale driver timeout value and the wait value gives a scale time to react to the previous command before passing the next one. The default values depend on the scale type.
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: Billing nodes are no longer used for Recipient and Third Party details
Action: If an address or account number is provided, the International/Duty block is being used for these. Otherwise, just the billing flag is provided to the carrier.
Change: Removed ability to automatically copy the ShipTo nodes
Action: If the ShipTo details are required by the carrier, you must map these manually.
UPDATED: August 14, 2021