Today 10-Nov-2022 we have deployed below changes and fixes to our Beta environment.
The release to Accept is scheduled Monday 14-Nov-2022.
The release to Production is scheduled Tuesday 15-Nov-2022.
Note: this is the last release before the announced freeze period which will be between 16-Nov-2022 and 2-Jan-2023. Our next release is planned for week 2 of 2023.
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.
New page: Change Log
- We have started a pilot phase for a new feature we have added in the Manage account section: the Change Log page. We will start with a small group of pilot customers and we aim to have this available to all our customers in January 2023.
Shipment details page changes
- In the shipment details screen when manually adding a package to the shipment, the description of the package code is not copied to the description of the package line anymore. The reason is that the package code description is an internal description (e.g. Red large box) and the package line description is an external description of the package content which is also sent to the carrier (e.g. books or electronic parts).
Location select / PUDO (PickUp DropOff) points
- We have migrated the location select connection from the Unifaun platform to the new nShift PUDO platform for the following carriers:
- COR (Correos Spain)
Email Settings
- When sending a test email in a mail template, the fields in the status table of a shipment were not filled. For instance the field $!item.shipment.get('str_accep') which should show the name of the person who accepted the receipt of the parcel, was empty. This is solved now.
- We have improved the SPF records lookup and we now also check the transcript and information section whether it contains the SPF record for transsmart.com
Various changes and fixes
- In the previous release, in the address book we changed the search field so you were able to search on a part of the name or address (“Contains”). Before, you could only find an address when you exactly typed the first letters of a name ( “Starts with”).
Since we want to support both search methods, we have added a setting for this in the address book. The default value is “Starts with” as it always was before last release.
When the setting is set to “contains” you are able to search in the name, street, postcode and city.
If you work with subaccounts, the subaccount will have the same setting as you select for the parent account. So if you change it on the parent account, it will also change on the subaccount(s). As soon as you change the setting on the subaccount, it will keep that setting regardless changes in the setting on the parent account.
Starts with:
Contains:
- In menu [Manage Account, Packages], when making changes in Packages -for instance editing or deleting them- the changes were not visible in My Details, Account Settings and the shipment details page when adding a new package line to the shipment, until logging off/in MyTranssmart. This is solved; changes made in packages master data are directly visible in My Details, Account Settings and the shipment details page.
3 comments
Today, 14-Nov-2022, we have deployed below changes and fixes to our Accept environment.
The release to Production is scheduled tomorrow, Tuesday 15-Nov-2022.
Today, 15-Nov-2022, we have deployed below changes and fixes to our Production environment.
Note: this is the last release before the announced freeze period which will be between 16-Nov-2022 and 2-Jan-2023. Our next release is planned for week 2 of 2023.
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.
Additional release note
Resetting a password did not work anymore; this is solved now.