Release Notes Version 20250509.6
This version was release to production on the 11th of June 2025
New Features & Enhancements
Daily Notes: You can now enter a note (e.g., “John is away”) and apply it across a date range, instead of entering it for each day individually.
Delivery Weights: If a delivery contains parts with no recorded weight, the run card weight will now display in red for visibility.
Switch Route Moves: Switch routes can now be moved directly from the dispatch board.
Kit Parts Display: Kit parts are now better organized on the run page. They appear under a dropdown grouped by their parent part, and a bug preventing orders with kit parts from being moved has been fixed.
Ship Routing Updates: When a release is moved to a new run, its ship routing value is automatically updated.
BDP Plant Settings: Admins can now choose which plants are allowed to send data to BDP via general settings. By default, all plants are selected, but disabling unused plants will prevent unnecessary data from being sent and ensure that BPM logic does not impact plants that don’t use BDP.
Transfer Order Weights: Part weights are now supported for transfer orders.
Performance Improvements
Resolved an issue where excessive attribute calls on the dispatch board caused the page to become unresponsive.
Fixed a problem where duplicated lines were inflating the amount of data returned from the BAQ.
Improved card rendering performance — previously, having many cards on the board caused lag and temporary unresponsiveness.
Enhanced data filtering performance when using advanced filters. Previously, all data within the date range was returned without server-side filtering, and then filtered client-side — causing major slowdowns when handling large data sets. Now, filters are applied on the server before data is returned, significantly improving speed.
Optimized Sales Order and Transfer Order BAQs by removing circular joins that were causing slow performance.
The selected plant at login is now applied automatically as a default filter in the BAQ. This means only data for that plant is retrieved on first load, reducing the initial load time. Users can still change the filter to include all plants if needed.
Removed part descriptions from the BAQ and now retrieve them only on the run page. This reduces BAQ size significantly — previously, if one order had 20 releases of the same part, the same (often large) description was returned 20 times, bloating the data payload.
Improved BPM performance when saving data. Previously, searches for order releases were done across all companies using a string-based SysRowID, resulting in full table scans. Now, we convert the SysRowID to a GUID and include the company in the filter. This allows proper index usage and significantly speeds up the search. Additionally, we removed redundant logic that unnecessarily looped through the data again after the main search.
Last updated
Was this helpful?