Technical Release Notes 2024

Important Note:

Prior to installing updates of ShipIT 365 please understand that it is extremely important to test our software with the latest version. 

Especially when integrated software, such as Tasklet, or customization's are in place.
Such customers should be instructed to never implement app updates directly in production environments. 
Furthermore, keep in mind that corresponding versions of apps related to ShipIT should be updated together ShipIT. So for example, when the Tasklet Integration app is installed ensure that the ShipIT app and the Tasklet Integration app are updated to the same version.

Version	Release Date
23.11.3020.2	29-07-2024

The following issues have been resolved:
Renumbered field Account No. (Bill-to) for Purchase Header table to avoid errors when posting purchase documents, causing a data type error when transferfields was used.
Added additional check on sell-to customer and buy-from vendor e-mail type to only overwrite default value from ShipIT Setup on source document if type for customer/vendor is defined.
Connector for Mobile WMS: Fixed rounding precision error that could occur on clean install when setting initial values during synchronization of packages.

Version	Release Date
23.11.3020.0	11-07-2024

The following improvements have been implemented:
When the booking and/or printing of a Transport Order fails the error message is now returned on the Tasklet Mobile Device when “Continue after TO Fails” is activated in the Mobile WMS Setup. Note: Even though a error message is given, the process has still continued and the warehouse shipment has been posted.
The Gross Weight (Customs Article Gross Weight) is now also forwarded in the nShift Ship API.
In Transsmart it is now possible to use a different (Transsmart) account number for invoicing. The Transport Order has been extended with an Account No. (Ship-to) and an Account No. (Invoice). Also the source documents (sales orders, etc…) have an Account No. (Invoice) field. The Account No. (Invoice) is copied from the Bill-to Customer No..
In the Tasklet Mobile WMS ShipIT integration app it is now possible to setup weight conversions or package dimension conversions. This could be useful when for instance the weight on the scanners is entered in a different measure than the measure that the shipping provider uses. So, for instance, when packages are measured in KG’s and you are using nShift Ship (where grams are used in the communication). On the Provider Setup pages a Conversion Factor (Mass) (and rounding precision) and a Conversion Factor (Linear) can be entered.

The following issues have been resolved:
After synchronization of the basic data with Transsmart it could occur that Service Levels and/or Booking Profiles that were removed were still partially visible in ShipIT 365.

Version	Release Date
23.11.2978.0	21-06-2024

The following improvements have been implemented:
Important performance improvement when working with Warehouse Shipments

Version	Release Date
23.11.2951.0	18-06-2024

Attention:
For on-prem installations the customer license needs to be refreshed, because we had to extend the ShipIT license range.

The following improvements have been implemented:

It is now possible to print labels when working with Sendcloud using a PrintNode account.

For more info see this page.

The cancel delete transport order is now processed on the nShift Ship portal.

The following issues have been resolved:

The Create Transport Order action was not available on an (non-posted) Sales Return Order, when the transport orders were based on posted documents.

This is incorrect, because with Sales Returns the transportation happens prior to posting (the receipt).

Version	Release Date
23.11.2897.0	28-05-2024

The following issues have been resolved:
When packages have been entered on a sales document and these packages were transferred to a Transport Order, then a new default package was added to the Transport Order as well.
Sendcloud: Unstamped letter took first Shipping agent code and Service when services were not specified in the Sales Document
Sendcloud: Transport Order became ‘locked’ when one of multiple packages were in the error state.

The following improvements have been implemented:
With the Tasklet integration active it is now possible to mark license plates listed on a Transport Order back into the untransferred state, when that Transport Order is deleted.
Several performance improvements when registering transport orders in combination with the Tasklet integration.
It is now possible to postpone updates of source documents when booking a Transport Order. The synchronize Transport Order will then update the source documents. For this purpose the “Skip updating Source Docs after booking TO” field has been added to the ShipIT Setup. See the documentation in the Setup page for impact and how to enable this.
In the Tasklet integration it is now possible to continue the posting of a warehouse shipment even when the booking of a transport order returned an error. As a consequence there won’t be a label, but it means that the warehouse employees can process the warehouse shipments. The transport order can be checked, adjusted and printed afterwards. However, it will also mean that track & trace information will not be set on the posted documents. For this purpose the “Continue after TO Fails” field has been added to the Mobile WMS Setup. See the documentation that describes the Mobile WMS Connector for impact and how to enable this.

Version	Release Date
22.11.2808.0	08-04-2024

Attention:
If you have implemented a customization on ShipIT 365 that is using our so called “pin code” solution, then please reach out to us to get your license upgraded, prior to upgrading to this version.
For better security and traceability we have migrated the “pin code” to the customer license.

The following issues have been resolved:
The error message “`Could not write message to OutputStream: Error during saving a multipart message`" could occur in the communication with Transsmart.

Version	Release Date
22.11.2786.0	28-03-2024

The following improvements have been implemented:
Mobile Phone No. has been added to the Transport Orders and is included in the shipments for all the providers.
The Tasklet integration can now also be used with transport orders that are based on posted documents. The “Base Transport Orders on” field in the ShipIT Setup Card determines if the transport orders created from the Tasklet device are based on the unposted warehouse shipment or on the posted document, like a sales shipment. When the Transport Order is based on posted documents, the Transport Order is created during the posting of a warehouse shipment.
The transport order is now registered prior to posting the warehouse shipment, when working with unposted documents in the Tasklet integration. As a result the track & trace information is available on the posted source documents as well. The default flow is that the registration of the Transport Order updates the unposted source documents (e.g. the sales order) with track & trace information and then when these source documents are posted the track & trace information is forwarded from the unposted document to the posted document.
Documents and Labels generated by providers are now automatically downloaded and stored as an attachment on the Transport Order. A zip file is generated with all the files related to the transport order and is stored in the Attachments Factbox. Labels for packages are also stored separately in the database. Besides the pdf files also other file types, like ZPL files, are now included. For this reason, the manual action to download labels is discontinued. Please Note: not all shipping providers provide labels or other documents in their API’s.
It is possible to indicate that attachments should be automatically deleted when a Transport Order is archived. This could help in reducing the size of the database when a lot of transport orders are processed on a daily basis. A setting called “Remove Attachments on Archiving” has been added to the ShipIT setup to control this.

Attention:
When you are working with the providers Sendcloud or Easypost and you are using the option “Base transport orders on” Posted documents in the ShipIT Setup, in combination with the option to automatically create the transportorders, then the option “Automatically select applicable Ship.Method” must be set in the Provider Setup.

The following issues have been resolved:
The file names generated for shipment documents or package labels, which were stored inside a zip file were not always unique and didn’t have file extensions.
Some default values on the Provider Setup, like the cost center, the email-type and the account no., were not always set correctly on new transport orders or source documents.
When only one provider is active the provider was not automatically selected on purchase return orders, transfer orders and service orders.
For Sendcloud an additional check has been added that makes the weight of packages mandatory prior to booking transport orders, to prevent an issue on the Sendcloud portal.
For Sendcloud and Easypost the selected service or rate on the source documents was not always forwarded correctly to transport orders.
For Transsmart it could sometimes happen that the references to packages between ShipIT 365 and the Transsmart portal got lost. This resulted in an error “The Transport Order Package does not exist”.

Version	Release Date
22.10.2667.0	23-02-2024

The following improvements have been implemented:
Full support for custom events when working with the Create and Book option for Transport Orders.

Version	Release Date
22.10.2596.0	12-02-2024

The following issues have been resolved:
When printing individual labels the status was not updated.
In very exceptional cases the api response after booking shipments returned an error that couldn’t be handled. This error message is now logged, so that the response can be further analyzed. Also the Transport order gets the booked status, so that it can be still be synchronized after the error message occured.
The cost center didn’t always get the default value from the provider setup.
The license check on the Setup Card and in the Setup Wizard was sometimes returning the wrong error message.