Today 6-Sep-2022 we have deployed below changes and fixes to our Beta environment.
The release to Accept is scheduled 12-Sep-2022.
The release to Production is scheduled 13-Sep-2022.
General note: because it’s possible that users are working in the MyTranssmart dashboard at the moment of the deployment, it is recommended that users log off the dashboard, press Ctrl + F5 to reload the current browser page including the browser cache and log in again.
Shipment overview page changes
- In some specific cases, deleting a shipment with status ERR showed a "Success - Shipments deleted" message while in fact it did not delete the shipment but should show a message with reason why the shipment could not be deleted. This is solved now.
- In the overview page you are able to add columns and after that, search within those columns. Searching for multiple additional references could result in long waiting times in case of many shipments/results. It was fast when searching for 1 column e.g. for Invoice only. This is solved now. We still encourage to specify for which column you would like to search.
- After deployment of the release at 1-Aug-2022, loading shipments in the overview page encountered long waiting times. The fix for this was already deployed at 8-Aug-2022.
Shipment details page changes
- When downloading a shipment label not all special characters were correctly shown. This was already solved and deployed at 2-Aug-2022.
- Despite the fact that in MyTranssmart we have a fixed set of possible Internal Reference types e.g. ORDER and INVOICE, via the API it’s possible to send in any value. From now on we will also show these additional references in the section Shipping information.
- Select Pickup Point: from now on we will also show the carrier code and carrier long name when hoovering over the carrier logo. Example:
- Run carrier selection: after selecting a proposed line, the field Delivery date was not refreshed. This is solved now.
Manifest changes
- In the manifest page the filter of field ‘Country’ was a multi select dropdown but the manifest call only supports one (or all) countries in one manifest call. Selecting more than one country was never implemented in our backend/API so we have now aligned this dropdown to a single select value:
- We have improved the performance and stability of the Manifest page in case of manifesting many shipments.
API/DevDocs changes
- In specific scenarios of doing many status calls for a wide date range / large amount of shipments, timeouts could occur. We have improved this process.
- We have improved the validation for creating/booking a shipment without or with empty additional reference Type.
- We have improved the validation for creating/booking a shipment without or with empty package Quantity. Note that we again allow to send in quantity “0” for a package line as long as there is at least one package line with a quantity greater than zero filled. We do still encourage not to send in quantity “0” because these lines are not (& were never) processed by our backend.
- In the API token settings and configurations of the account are stored. The more settings and configurations exist, e.g. carriers, service levels and subaccounts, the bigger the token size will be. We have made improvements to reduce the token size.
- The direct link API now also supports Act on Behalf functionality which can be used when working with subaccounts. We have also updated the DevDocs documentation in https://devdocs.transsmart.com/#_direct_links
- In (pick-up) locations retrieval we have solved an unrecognized field "Date" in the error response from PNL API which occurred when the zipcode was empty in the request. To be able to handle this error message correctly we have refactored a part of the location select call.
- https://devdocs.transsmart.com/#_get_list_of_incoterms was showing "Unresolved directive" errors. This is solved now. We have also taken out the documentation of getting one incoterm because that call is obsolete since we moved to APIv2 two years ago.
Email template changes
- In the Email Settings overview page we have added a new button ‘Validate SPF records’. After you have added one or more SPF records at your domain provider, you can press this new button and the system will check and update all email templates. From that moment on, emails can/will be sent for the email templates that were blocked before. Note: it will also check email templates which were not blocked so if SPF records are not correct anymore, those email templates will be blocked for sending mails.
- SPF records check: we now use MxToolbox instead of Linux DNS Lookup
- SPF records check: we have improved the validation if a technically correct email address is filled in.
Various changes and fixes
- SmartScan: the statement “PRINTADDREFCUSTOMERORDER_” was not working. This is fixed.
- We have added a status page icon to the MyTranssmart menu bar which has a link to https://statuspage.transsmart.com/. Please subscribe to this page to stay informed about the uptime of our systems.
- Fixed unjust message Successful when uploading a shipment file without header in the Excel file.
- In some specific scenarios the upload of shipment files failed and returned an error “Unauthorized”. This is solved now.
- We have improved the error message when trying to create a new user with duplicate Email address. It will now show the error “CONFLICT - While creating setting.
user: {username@domain.com} already exists.”. - The MyTranssmart platform is built with Angular. In week 2 of year 2022, we had updated it to version 13. Now we have updated it to version 14.
2 comments
Today 12-Sep-2022 we have deployed the changes and fixes to our Accept environment.
The release to Production is scheduled tomorrow 13-Sep-2022.
Today 13-Sep-2022 we have deployed the changes and fixes to our Production environment.
Note: because it’s possible that users are working in the MyTranssmart dashboard at the moment of the deployment, it is recommended that users log off the dashboard, press Ctrl + F5 to reload the current browser page including the browser cache and log in again.