Today, 11-Dec-2023 we deployed below changes and fixes to our Beta environment.
The release to Accept is scheduled Monday 18-Dec-2023.
The release to Production is scheduled Tuesday 19-Dec-2023.

Integration nShift Transsmart and nShift Returns

• We have partially completed the integration with our Returns platform. When activating the Returns integration, all shipments with status LABL will be sent towards our Returns platform. In there, consumers/customers can initiate the return order flow. Return orders that are created will automatically be booked and printed in Transsmart's environment. That part is still under construction the coming weeks. For more information about the Transsmart - nShift Returns integration please contact our Sales department.

DevDocs changes

• In https://beta-devdocs.transsmart.com/#_delivery_note_lines we have added information about the fact registering Delivery Note Lines on shipment level will go End of Life in the future and new implementations should only integrate on package level; not anymore on shipment level. There is no EOL date yet but in case you have integrated on shipment level, we strongly advice you to change this as soon as possible.
• In https://beta-devdocs.transsmart.com/#_act_on_behalf we have added information about the working of the act on behalf functionality. It was already possible for a long time to for instance send in shipments for child accounts but this was not yet documented in the DevDocs.

Booking profiles

• In menu [Manage account, Booking Profiles] we have added the possibility to exclude the fields Cost center, Incoterms, Payment terms and/or Mail Type. By default, when creating a new booking profile these four fields are not selected anymore. Before, the fields were stored as value “” (= empty) instead of null (= not applicable). This could cause unwanted behavior that when selecting a booking profile in an existing shipment, it would make empty these values instead of leaving them unchanged. Note: this does not affect the existing booking profiles so if you want to make use of this new functionality for existing booking profiles, you need to modify those. 
  

Various changes and fixes

• In the shipment overview page, in specific scenarios when shipments contained validation errors, the button ‘Book’ did not work for shipments with status NONE, NEW and BOOK. This is solved now.
• In menu [Manage account, Email Settings] when zooming into a Mail template, you can create/change sending triggers. When creating/changing a sending trigger with Sending time = “Scheduled” and Trigger = “Every 60 minutes”, it didn’t correctly store the value. This is solved now.
  
• When saving a newly created trigger, before the screen jumped back to the ‘New trigger & time’ and as a user I would expect to keep seeing what I just created. We have changed this behavior so when now creating a new trigger, after pressing ‘Add time +’ it will keep showing the same page.
• During implementation of nShift PUDO service we found out it was returning the house number in the same field as the street name. Some of Transsmart’s carriers expect the house number to be in a separate field and also customers are using both fields. The problem was that if you would send in separate fields and would do a location select call, after selecting a pudo point, it would put the house number in the street name. To prevent this from happening, we had temporarily built in parsing logic. This parsing logic is now removed because the nShift PUDO service now has added the house number as separate field.