⭐️ Server-Side Form Validation: There are scenarios where the current client-side validation_javascript within forms cannot perform more advanced validation methods such as cross-field validation, dynamic/runtime validation, or validation across large datasets. This can lead to incorrect data being sent to your systems without a way to proactively catch the mistakes.
For example, you may want to validate that the trailer number a driver inputs matches a trailer number your system knows or expects. Today, you cannot pass the list of valid trailers at runtime so the driver may end up fat-fingering the input and submitting the form. After submitting the form the driver is then taken back to the load screen where they see the same workflow action they just completed because your system determined the data was invalid and did not advance their workflow. When the driver goes to resubmit the form, all of the data they previously input is erased and they have to re-enter the form data.
With server-side form validation, you can now configure workflow actions to send the form data to your server for validation while the driver waits for a validation response. Using the example above, when the driver attempts to submit an invalid trailer number, your system can catch the error and present them with an error before the driver submits the form, so they do not have to re-enter all of the form data. You provide your own error message for any input field(s) that you deem invalid and they are shown to the driver directly in the app. The driver can then edit those fields and resubmit the corrected form.
🔧 Login Screen Help Link: The link in the upper right corner of the Login screen was not as visible to users as it could be, so we’ve made it a button and moved it so that it appears within the main body of the login screen.
iOS
🔧 Reduced the amount of time necessary for a barcode to be visible before it registered as a scan.
🐞 Fixed a bug where the barcode scanning camera view on forms did not accurately reflect the view from which barcodes could be read. This could lead to users scanning barcodes they did not see on the camera. This would also prevent barcodes from being scanned at all if more than one barcode was in view.
🐞 Fixed a bug where forms did not automatically scroll to show the camera preview when opening a barcode field on forms.
Android
🔧 Improved barcode detection to require higher confidence before registering a scan.
🐞 Fixed a bug where the barcode scanning camera view on forms did not accurately reflect the view from which barcodes could be read. This could lead to users scanning barcodes they did not see on the camera. This would also prevent barcodes from being scanned at all if more than one barcode was in view.
✅ As usual, this version of the Platform mobile app is designed to be backward-compatible with your existing web services and doesn’t require server changes prior to being deployed. If a future version introduces a backward-incompatible change, we’ll note that in this portion of the release notes.
Server and App Editor
The following items are server-side changes and are available without a mobile app update.
🔧 Trip Planner Studio – Build a New Route: The Build a New Route feature in Trip Planner Studio has been updated to use HERE’s updated SDKs, so that new routes – given the same inputs – will match routes delivered to drivers within the mobile application. In addition, we’ve made updates so that search suggestions render faster when inputting addresses.
🔧We’ve optimized database connections to ensure our systems meet uptime requirements and expectations.
🔧 If you’re using the division_code property in your authentication response, a verify call will immediately follow the initial authentication to verify the user. This is existing behavior; however, now the user will not be logged in if the verify call fails.
🔧The Screens API now accepts a JSON body for PUT requests.
