Friday 16-Feb-2024 we deployed below changes and fixes to our Beta and Accept environment.
The release to Production is scheduled Sunday 3-Mar-2024.

Spring Boot upgrade

• We have performed a major upgrade of our Spring Boot framework to version 3.2 which was the reason this release took a bit longer to come out.

DevDocs changes

• In https://accept-devdocs.transsmart.com/#_5_1_2_for_multiple_shipments we have extended the explanation of some fields:
  • dateFrom: Insert date/time from, of the status event when processed into the database.
  • dateTo: Insert date/time to, of the status event when processed into the database.
  • maxResults: Maximum number of status updates to collect. One shipment can have mutiple status updates so the amount of shipment can be lower. Example: when maxResults = 1000, you might get back 100 shipments with 10 updates per shipment.
  • currentStatusOnly: Only include the last status per shipment and collo, not the complete history; this parameter only works when the parameter 'isDetailed' set to true. It will first collect all status events matching the maxResults and then only send the last status event. So the set of data will be smaller than the maxResults value.
• In the status response message the date format is different (dd-MM-yyyy HH:mm:ss) than the standard format we use (yyyy-MM-dd HH:mm:ss). We cannot change the format in this version of the API since customers/integrators implemented it like this. The DevDocs are now showing the used date/time format. If we decide to change the format in the status response, it will be done in a newer version of the API so that will not have impact on existing integrations.
• For the field additionalReferences.type we have added the 17 preferred values. These values are also the predefined ones that can be filtered on in MyTranssmart.
• In the sub sections of https://accept-devdocs.transsmart.com/#_2_4_shipment_manifesting  the wrong date format was described for the fields 'date' and 'dateTo'. It was showing Format yyyy-MM-dd HH:mm:ss but it's not possible to fill in a time, so the description is adjusted to yyyy-MM-dd. 

SmartScan

We have added new codes to put shipments to status ONHOLD and put them back to status LABL again.

In MyTranssmart the button ‘Onhold’ already exists. See https://helpcenter.nshift.com/hc/en-us/articles/7395768440220-Status-ONHOLD

We have now also added the scan codes ONHOLD and ONLABL to be able to change the shipment status via a scan action.

In the shipment details page:

• ONHOLD: will change the status of a shipment from LABL to ONHOLD
• ONLABL: will change the status of a shipment from ONHOLD to LABL

In the SmartScan page (https://my.transsmart.com/dashboard/shipments/smartscan):

• ONHOLD_ref1234
  will change the status of the shipment with reference "ref1234" from LABL to ONHOLD
• ONLABL_ref1234
  will change the status of the shipment with reference "ref1234" from ONHOLD to LABL
• ONHOLDMULTI_ref1234,ref1235
  will change the status of shipments with references "ref1234" and "ref1235" from LABL to ONHOLD
• ONLABLMULTI_ref1234,ref1235
  will change the status of shipments with references "ref1234" and "ref1235"  from ONHOLD to LABL

Various changes and fixes

• We have improved the performance of our rates call /v2/rates/{{account}} In specific situations the response for the same call could take longer than intended. This is solved now.
• In some specific cases the reset password page did not work properly and gave a CORS error when looking in the Developer tools of the browser (with <F12>); this is solved now.