FlexGuide4 Release Notes v2.10

FlexGuide4 Release 2.10

The option to post EWM warehouse orders synchronously instead of exclusively asynchronously has been added, so that error messages from EWM (e.g., insufficient capacity at the destination location) are returned directly to the user. For each process, the customer can now use a flag to specify whether the posting should be synchronous or asynchronous; the default remains asynchronous. The logic is also designed so that it can be used for WM in the future and evaluated centrally.
The outdated MM adapter logic has been completely revised and aligned with the stable architecture of the WM adapter. The code, UI, and settings have been standardized, and the buffer tables and lock/unlock logic have been adopted. The adoption of WM special case handling makes MM synchronization significantly more robust. The result for the customer is a more stable, consistent, and future-proof system.
The information about the batch is returned in the MM interface.

A future improvement is planned that will allow flexibly definable areas to be created in the Layout Editor and linked to simple logic such as capacity limits or automation.

The new DMG Vendor Connector expands the portfolio of connection options for external vehicle fleets to FlexGuide4. Using the interface, FlexGuide4 can assign individual driving orders to specific resources or transfer the entire order pool to the external fleet manager. In addition, critical zones such as intersections or ramps can be controlled using area management.
The Vendor Connector can save the last order sent and recognize loading orders.

Going forward, logs will serve as the primary method for identifying customer issues. Therefore, the log output has been enhanced, and the export limit has been extended to support up to 100,000 log entries.

To enable efficient unloading at stations, the unloading sequence can be flexible. Manually recorded orders no longer need to be unloaded in a fixed sequence, as strict adherence to a predefined order is not always practical.

The “Test synchronization” button in the conditions for synchronizing EWM warehouse tasks enables reliable testing of the filters that have been set.
Empty fields will no longer pose a problem in the dynamic determination of the From/To location in the EWM interface.
A system error related to the validation of WM transport orders has been fixed.
The synchronization of the transfer order to SAP WM after a location change in FlexGuide4 works without errors.

The ExternalAPI role, which serves to prevent breaking changes to the APIs, now extends the corresponding action function in the Core module.
The operator role, which previously had access to functions beyond the permitted scope, has been restricted to its designated authorizations.

The action parameters for pick and drop operations are correctly transferred to the transmitted VDA order.

To prevent incorrect status changes of orders caused by multiple clicks, the “Add selected drive orders” button is now disabled when no internet connection is available or when a click has already been made and is being processed. This correction ensures that actions are performed only in a valid system state, improving both system stability and data consistency.
Internal orders created through the “Free Relocation” dialog are no longer incorrectly displayed in the “Drive driving order” dialog.
The issue of the validation field not appearing in the “Drive driving order with list” dialog when validation was only required in the second step (e.g., when only the To station required validation while the From station did not) has been corrected. The validation now functions reliably.
The value “0” is now accepted as a numeric value during validation.

In the “Group” column of the order overview, a selected value can be entered and saved to assign orders to a group.
Error codes are displayed correctly in the control station and in the logs.

Orders can no longer be set to an error state without specifying the order error.