This release contains the first general-availability version of the new Scan feature on the mobile, as well as an enhancement to the despatch process on the web app for more accurately calculating package dimensions when shipping kitted items. It also delivers a number of bugfixes related to the way the system handles dates and times.
New Feature: The first general-availability version of the Scan feature on the mobile app will be available with this release. If you have not been involved in the early access program for this feature, you will need to enable the permission before your users can access it. You can do this from the Setup module by assigning the "Perform" and "Scan barcode" permissions to a role. To find out more information about this feature, please take a look at the user guide here (486349).
Enhancement: Improved the logic for calculating package dimensions during despatch when dealing with kitted products. Previously, the system would try to calculate the package details by examining the individual components in a package. With this release, the system now has the ability to use the kit parent dimensions instead. This can be beneficial in situations where the complete kit may be packaged differently from the individual components when sold separately. By default, the previous behaviour will be maintained with this release, so please raise a ticket with the helpdesk if this new logic would be useful for you (644635).
Resolved Issue: Fixed several bugs related to the way the system handles dates and times. The system should now be more consistent with the way it interprets, presents, and converts dates and times - particularly when dealing with sales order requested delivery dates. We also have some additional related changes planned for the next release (358705, 363451, 637174, 625802).
Resolved Issue: Fixed a bug that could cause actions to be visible to users on the mobile app even if they are not part of the role to which the action was released (358748).
Resolved Issue: Fixed a bug that prevented some advanced search conditions from working correctly when they referenced the "sequence" field on locations (354917, 367285).
We are keen to give you more transparency on upcoming changes to your system, particularly those that may impact integrations or other critical business workflows. To that end, we've put together a new page that you can check any time to see what is coming in the future:
Coming Soon
Coming Soon
These numbers come from our internal work tracking system, and we present them here for you to reference if you have any questions. If you've raised a specific issue on the support desk, then we'll come back to you on that ticket with any relevant updates.