8.39.1 Release Notes
Possible Breaking Changes
What has changed | What to do |
---|---|
New App versions available. | If you are using modified Apps, you must replicate your changes in the new version. See App Changes below for a summary of the items that have affected Apps in this release. |
Apps
Current App versions and any changes are listed below. See Upgrade Apps and Snippets for general advice. To get access to the listed features, download the newest version of the App.
App | Version | ID | Description |
---|---|---|---|
Administration | 1.56 | 368009 |
|
Warehouse | 1.51 | 362922 |
|
MailCenter | 1.47 | 366636, 362922 |
|
Desktop | 1.40 | 362922 |
|
Store | 1.33 | 362922 |
|
Supplier | 1.33 | 362922 |
|
View | 1.30 | - |
|
Desktop Shipping | 1.23 | 362922 |
|
Other Changes
ID | Salesforce | Description |
---|---|---|
366634 | - | Shipping Apps. Empty bulk lists can no longer be processed. Bulk lists containing no recipients can no longer be processed when operating in product shipping Apps. An error message now presents if no contacts are found in the list. |
368193 | - | HubCapp Peripheral Agent. Updated handling of Generic Driver Settings. Configuring the Generic Driver Settings RX Expression and TX Expression via the HubCapp Peripheral Agent now functions as expected. Previously, attempting to save detail in these fields would fail. |
366037 | SF30333 | HubCapp Peripheral Agent. Port configuration now saved. The configuration of the Serial Port field is now saved as expected by the HubCapp Peripheral Agent. This fix corrects issues whereby the port was always set to COM1. |
366982 | SF30373 | Yamato. Payment Terms now passed correctly in requests. Updated handling of Payment Terms when operating with Yamato. Payment Terms are now passed in product ship requests as following:
|
367340 | SF30399 | Transtream. Updated treatment of CrossPage communications. An issue has been resolved whereby CrossPage communications did not function as expected following upgrade to Transtream 8.38.0. This was due to changes made to the default value of the Google Chrome Referrer-Policy setting. Now, when accessed via HubCapp, the Referrer-Policy header is set to no-referrer-when-downgrade. |
357324 | - | Transtream. Improved App login logic. An issue has been resolved whereby after logging out of a direct App URL, a subsequent log in would direct users to Product Admin. |
366636 | - | MailCenter App. Updated handling of default rate group. The MailCenter App now loads the correct rate group when operating with the Use Default Rate Group App setting enabled. |
361096 | SF29905 | Outputs. Corrected handling of permissions for ActiveReports. An issue has been resolved whereby ActiveReports documents did not generate as expected when the associated output permissions were set at the profile level. |
355742 | SF29908 | UPS. Amendments to tracking logic. Updated the tracking logic used for UPS shipments to accommodate changes made to the carrier’s tracking website. Tracking now functions as expected for all UPS carriers. |
362922 | - | Shipping Apps. Improved return address logic. Shipping Apps are now prepopulated with a return address on load. The address is taken from the Returns address as defined within the user’s location in the Administration App. In support:
For detail, see Warehouse App - Address Details. |
368009 | - | CargoWise One. Updated Charge Type handling. Saving configuration changes to Charge Types via the Administration App’s Reference Data tab now functions as expected. Previously, the External System Code field was not saved to the system, causing errors when operating with CargoWise One invoicing.
Note that Charge Codes must first be configured in CargoWise One before they can be added to Transtream. Additionally, the following Charge Types must have an External System Code value configured for CargoWise One to accept invoices: Fuel Charge, Total Accessorial Charge, Total Shipping Charge and Total Charge. |
362629 | SF30170 | FedEx SameDay® City API. Zip Codes now handled correctly. Errors no longer present when rating and shipping zip codes containing more than five characters with FedEx SameDay® City API. Previously, Ship To and Ship From addresses containing a zip code consisting of more than five characters could not be processed. Note that only the first five characters are passed to the carrier. |
See Versions for a list of the latest production installer and App versions.
8.39.1 released to Transtream Production on 26 November 2020. Article last edited 11 January 2021