Changelog Release 2.15.3

Bug Fixes

SAP

• Fixed an issue where, in certain situations, warehouse tasks locked in EWM were no longer rechecked, so the associated transport orders remained locked even after being unlocked in EWM; in addition, long response times from EWM could result in two transport orders being created for one warehouse task. The synchronization with EWM has been made more robust: locked warehouse tasks are reliably checked again and released once unlocked, confirmed warehouse tasks are completed correctly, and duplicate transport orders are prevented.

Product Settings

• The Node.js runtime used by FlexGuide4 has been updated to a version that closes recently disclosed security vulnerabilities; an unpatched version can no longer be used when deploying to SAP BTP. Applications that are already running receive the secured version only after a redeployment or restage.

Changelog Release 2.15.2

Release 2.15.2 is another hotfix for Release 2.15, focusing on robust order transfer from SAP EWM. A single maintenance error in the path network no longer blocks the creation of the remaining transport orders of a synchronization run, and warehouse tasks that were not created are taken into account again in later runs. Transport orders from initially blocked warehouse tasks adopt the current data from EWM after unblocking, including the due date. In addition, the assignment of a transport order is retained even if an update from EWM arrives at the same time. In the event of an evacuation, mobile robots that cannot turn on the spot now choose the evacuation location based on the route that can actually be driven. Permissions have also been tightened: background processes can now only be activated or deactivated by key users and administrators. Release 2.15.2 thus stands for greater reliability in the EWM connection, in emergency operation and in the assignment of permissions.

Bug Fixes

Evacuation Management

• During an evacuation, the spatially closest evacuation location was always chosen – even if a mobile robot that cannot turn on the spot could only reach it via a detour. This could lead to unnecessarily long evacuation trips. The evacuation location is now chosen based on the route that can actually be driven, so that vehicles reach a safe location directly.

Product Settings

• Users with the Operator role were able to activate and deactivate background processes in the settings under “Jobs”. This permission is now reserved for the KeyUser and Admin roles; for operators, the status of the background processes is read-only. This prevents background processes from being switched off by users without the appropriate authorization.

SAP

• If no transport order could be created for a single warehouse task during EWM synchronization, for example because there was no drivable path to the source or destination location in the path network, the creation of all other transport orders of the same synchronization run was discarded; these warehouse tasks were then only transferred again after a change in EWM. Now only the affected warehouse task receives a creation error, all others are created as transport orders as usual, and warehouse tasks that were not created are taken into account again in one of the following synchronization runs. A single maintenance error in the path network thus no longer blocks the order transfer from EWM, and there are no more gaps in the numbering of transport orders.
• Transport orders for warehouse tasks that were created as blocked in EWM did not receive a due date, because blocked transport orders did not adopt updates from EWM. As soon as the warehouse task is unblocked, FlexGuide4 now updates the corresponding transport order with the current data from EWM, including the due date. Complete order data is thus also available for dispatching for warehouse tasks that were initially blocked.
• If an update from EWM arrived at exactly the moment FlexGuide4 assigned a transport order to a resource, the order status could be reset from “assigned” to “ready”. A completed assignment is no longer overwritten by simultaneous updates from EWM, so that the transport order reliably stays with the assigned resource.

Changelog Release 2.15.1

Release 2.15.1 is a hotfix for Release 2.15 focusing on reliable login. For installations with long organization or space names, or names containing special characters, logging in was not possible after the update. Login now works regardless of how these names are written, without any additional adjustments to the deployment. Release 2.15.1 thus stands for secure and reliable access to FlexGuide4.

Bug Fixes

Product Settings

• For installations whose organization or space name is very long or contains spaces, capital letters or underscores, logging in was not possible after the update; instead, the message “redirect_uri does not match the configuration” appeared. Login now works regardless of the length and spelling of these names, and users are correctly redirected to FlexGuide4 after logging in. A workaround used in the deployment in the meantime is no longer required.