FlexGuide4 Release Notes v2.15 EN

Andreas Kalamala

21. October 2026

Changelog Release 2.15

Release 2.15 focuses on new ways to structure the layout, the control of mobile robots and operational reliability. With the new areas, locations can be grouped graphically in the Layout Editor and then used in filters, pick-up conditions, capacity rules and as an alternative area. Waiting orders and waiting locations make it possible to position vehicles close to the pick-up location before a transport order is released. The new loading scheme and configurable strategies for group assignment simplify the customizing of transport control. For mobile robots, FlexGuide4 now transmits trajectories in accordance with VDA5050 2.1 and responds safely to connection losses. A highlight is the new, more powerful graphics engine for the map display: Live Map, Layout Editor and dialogs respond noticeably faster when zooming, panning and editing, and the Live Map now offers an automatic detail mode. A new dashboard tile makes signal states visible in the control station and switches outgoing signals directly. EWM apps are now integrated directly into the dialogs, and the transport order overview offers additional filter and copy functions. Extended logging, log retention per log level, distributed background jobs and stricter security settings for MQTT and OPC UA strengthen operations and security. Release 2.15 thus stands for greater flexibility in customizing, precision in robot control and stability in operation.

Breaking Changes

Product Settings

  • The security of the communication interfaces has been increased: an IP whitelist can be configured for the integrated MQTT broker, and the MQTT bridge as well as OPC UA now validate the certificate of the remote party by default. Impact: The MQTT bridge validates the TLS certificate of the external broker, and for OPC UA servers with the authentication “Certificates”, unknown server certificates are rejected. After the update, connections using self-signed certificates will therefore no longer be established without adjustment. Required action: For the MQTT bridge, either store the corresponding certificate authority (CA) in the MQTT bridge settings or switch off the option “Reject unverifiable server certificates”. For OPC UA, enable the option “Automatically accept unknown server certificate” in the client configuration of the server and then re-establish the connection.
  • Automatic log deletion can now be configured per log level; the previous uniform retention period no longer applies. After the update, new default values apply (Silly, Debug and Verbose: 1 day, Info: 3 days, Warn: 5 days, Error: 7 days) – if longer retention periods are required, the values must be adjusted in the settings of the background job. This keeps error messages available for longer, while detailed diagnostic logs are cleaned up more quickly.

New Features

Dialogs

  • The EWM apps “Display handling unit” and “Display storage bin” are now integrated into FlexGuide4 and can be accessed directly from the menu after logging on. In addition, the source and destination locations in the dialogs are clickable and open the corresponding app in a new tab. Drivers thus get the EWM information they need on the move without switching systems.
  • The weight and weight unit of a transport order can now be selected and displayed in the dialogs and in the transport order information, including in “General warehouse activity”, “Drive transport order”, “Drive tour”, “Free relocation”, “Free pick-up” and “Create transport order manually”. Weight information is thus available exactly where the driver needs it.
  • Dialogs now automatically refresh the displayed data of transport orders that have already been loaded – such as source and destination location, material and quantity – at regular intervals. As a result, the driver works with up-to-date values even after picking up a transport order if data has changed in the background.
  • The new validation type “Overwrite field (also in follow-up transport orders)” is available in the validation customizing. A value captured in the dialog – for example the number of a pick HU created in the block storage process – is carried over to all subsequent transport orders of a multi-stage chain, so that multi-stage transports can be completed without re-entering data and without error messages.
  • The validation “Check exact location and overwrite destination location” is automatically skipped if no exact locations are maintained for the location to be validated. The remaining validation steps continue as normal. A uniform validation customizing can thus also be used for locations without exact locations, without causing error messages for the driver.
  • The URL of a dialog can now be displayed as a QR code directly in FlexGuide4. Key users and testers can thus open dialogs on a tablet or mobile data terminal with a single scan, without transferring the URL manually or using external QR code generators.

Dashboard

  • A new dashboard tile displays the current value (on/off) of a signal; outgoing signals can be toggled directly via the tile. Description, signal and color scheme are configurable. Important signal states are thus visible at a glance in the control station, and outgoing signals can be switched without detours.
  • In the dashboard configuration “KPI transport orders”, individual fault reasons can now be selected specifically for the status “In fault”. Faults that require urgent action, such as a blocked location, can thus be monitored separately from less urgent faults.
  • The quick creation button in the dashboard has been converted into a link that opens a configured quick creation directly in a pop-up. Transport orders can thus be created without leaving the dashboard.
  • The tile overview of the dashboards now shows the title of each tile, and the edit dialogs name the respective tile type, for example “Configure button”. In addition, the labels of the chart tile have been cleaned up. Users can thus recognize more quickly which tile they are editing.

Live Map

  • The map display in Live Map, Layout Editor and dialogs has been switched to a new, more powerful graphics engine, and its performance has been significantly optimized. Zooming, panning and editing elements respond noticeably faster – especially in extensive layouts with many path networks, areas and background images.
  • Depending on the zoom level, the Live Map automatically switches to a detail mode that shows, among other things, node IDs, station names, direction arrows within the edges and a detailed vehicle representation; a hint at the bottom of the map indicates the active mode. The manual display settings previously required are no longer necessary.
  • If “Cancel Order” is triggered in the Live Map for a mobile robot with a FlexGuide transport order, FlexGuide4 now asks what should happen to the transport order – for example, setting it to “Ready” or “In fault”. The status of the transport order thus remains traceable and controllable after a cancellation.

Layout Editor

  • The Layout Editor offers the new object type “Areas”. Areas are drawn as a surface like zones; all locations within the surface are assigned automatically, and the assignment can be viewed in the location properties. Areas form the basis for new filters, pick-up conditions, capacity rules and alternative locations.
  • Saving in the Layout Editor has been standardized: changes are now only saved permanently via the save button in the upper toolbar. In the dialogs for creating, editing and deleting layouts and path networks, the button is now called “Apply” and initially only transfers the change to the current editing session. This provides a single, clear point in time at which all changes are saved.
  • For a path network created from a LIF file, the button “Upload new LIF” is available, which replaces the previous LIF with a new version. Updated LIF files can thus be adopted without having to recreate the path network.

Order Management

  • Quick creation has been revised: the counting logic and button behavior have been restructured, and the configuration screen is organized by topic and includes explanations. When the configured maximum number of transport orders is reached, users now receive a clear message when trying to create another one, instead of the click remaining without feedback.
  • The transport order overview has been extended: new filter variants can be created and named directly via a dedicated button, a reset button restores the column selection, order and width to the default, and the jump to external apps can be switched on or off per user in the renamed “Configuration” menu (off by default). Users can thus set up the overview faster and more precisely.
  • The new filters “Source area” and “Destination area” are available in the transport order overview; corresponding filters also exist for the layout. Users can thus see all transport orders from or to an area without having to select each location individually.
  • In the transport order overview, a selected transport order can be used as a template for a new transport order via “Copy transport order” – regardless of its status, i.e. also if cancelled or completed. All fields are pre-filled, and the new transport order is created in the status “Ready” by default. This saves manual re-entry, for example when a cancelled transport order is needed again.
  • With waiting orders, a transport order can already be assigned to a resource while it is still inactive: the resource drives to a waiting location – a new location type that is maintained in the Layout Editor and assigned to pick-up and drop-off locations – and executes the transport order directly once it is activated. The function is activated on the transport order type, including a maximum waiting time, and applies to mobile robots as well as to manual vehicles, for which the dialogs “Drive transport order” and “Drive transport order with list” receive their own waiting display. Vehicles are thus already standing close to the pick-up location when the transport order is released.
  • The new areas can be used in transport control: in the load carrier type matrix, pick-up conditions such as “Same source area” and “Same destination area” are available, capacity rules can refer to an area instead of wildcard patterns, and an alternative area makes all locations of an area mutual alternative locations. This simplifies customizing and increases the choice of possible destination locations when a location is occupied.
  • Two new options on the transport order type control group assignment: “Always assign group completely” prevents a group from being split across several trips, and “Fill up via loading scheme during group assignment” determines whether the remaining capacity is filled with further transport orders. For each process, it can thus be decided whether vehicle utilization or keeping a group together takes priority.
  • In continuous planning of tugger trains, the number of rounds is now configurable (up to 10 rounds); without an entry, 2 rounds apply as before. Routes on which more than two rounds are driven in a row can thus be mapped.
  • The configuration pages for transport chains have been arranged more clearly, the texts revised and supplemented with descriptions and info dialogs; the functionality remains unchanged. The configuration of transport chains is thus easier to understand.

Resource Management

  • Transport control has a new section “Loading scheme”, in which it is defined independently of resource types which load carrier types may be transported together and in what maximum quantity. In the resource type, the loading scheme is assigned instead of the previous load carrier type matrix. This makes customizing clearer, and a loading scheme can be used for several resource types.
  • Individual resources can now be excluded from transport order assignment directly on the resource via the setting “Exclude from order assignment”; charging and parking orders of mobile robots are not affected. The previous option “Assign orders” in the vendor connectors for MiR and Agilox no longer applies – anyone who used it now maintains the setting on the resource.

Traffic Management

  • The buffer for the permitted deviation from the last node for a new order is now defined in the resource type details as a fixed value in meters instead of a flat 10 % – also for mobile robots. The input field appears as soon as “Allow deviation from last node for new order” is activated and is 0 m by default; for existing resource types with this setting activated, the value should therefore be checked. The tolerance can thus be adapted precisely to local conditions, independent of the distance.
  • In the resource type details, the Traffic Management section allows the safety margin of a mobile robot to be automatically doubled in length and width while it is being controlled manually. In automatic mode, the normal safety margin still applies. Other robots thus keep more distance from manually moved vehicles.
  • The automatic detection of keep-clear nodes has been extended: nodes outside an exclusive zone that lead directly out of the zone via an edge are also marked as keep-clear nodes, provided they do not belong to a location. A mobile robot can thus leave an exclusive zone at any time and release it for other robots.

SAP

  • Additional header data is transferred from SAP WM transfer orders, including sales document, transfer requirement number, material document number, requirement number and type, queue, priority as well as creator and creation time. The fields are available in the overview of available variables for user-defined fields and can thus be used in dialogs and overviews.
  • In the EWM block storage process, the driver can now also pick up a handling unit (HU) whose stock is smaller than the requested quantity – for example the front-most HU in the storage bin. FlexGuide4 checks the stock and block status of the HU when scanning and carries forward the remaining quantity via a follow-up transport order in line with the SAP standard; operation in the dialog remains unchanged.
  • SAP Logistics Management (SAP LGM) is now available under “SAP systems” with its own page for conditions and configuration. FlexGuide4 can thus connect SAP’s new warehouse management system in addition to EWM, WM, MM and PP.
  • The structure and texts of the EWM synchronization pages have been revised and supplemented with descriptions; the functionality remains unchanged. The settings are thus easier to understand.
  • The supplementary import conditions for EWM warehouse tasks now also offer the comparison operators “List contains” and “List does not contain” as well as the condition field queue; existing conditions continue to work unchanged. For example, several storage types can thus be maintained in a single condition and the warehouse tasks to be loaded can be narrowed down more precisely.
  • The test pages of the SAP adapters for WM and EWM now display the data read completely in its original format, and a handling unit can additionally be read in the EWM test area. Consultants can thus see all fields that the interface delivers and that can be used in FlexGuide4.

VDA5050

  • In the order sent to mobile robots, FlexGuide4 now also transmits the curve paths (trajectories) stored in the layout in accordance with VDA5050 2.1, provided the robot supports this according to its factsheet. Robots thus drive planned curves around obstacles, racks or pillars exactly as intended in the layout.
  • For orders without an action at the target node – such as “Send to node” or parking trips – FlexGuide4 can now automatically add fine positioning at the last node, configurably. Vehicles that require this action thus align themselves exactly at the target instead of merely stopping within the deviation tolerance.
  • The connection messages of mobile robots according to VDA5050 are now fully evaluated: in the event of an unexpected connection loss, the robot is marked as not controllable and receives no new orders, while its blockings in traffic management are retained. This prevents other robots from entering areas in which a robot that can no longer be reached may still be moving.
  • Support for mobile robots of the type Jungheinrich SOTO has been extended: a new tour planning algorithm bundles several transport orders into one tour, observing FIFO at the pick-up racks and LIFO in the robot’s compartments, and transmits it as a single VDA5050 order. After switching between manual and automatic mode, the robot continues the tour at the point where it was interrupted, and if a pick-up fails, the affected transport order is cancelled or set to fault, depending on the setting.

Vendor Connector

  • MiR vehicles are now displayed in the Live Map as mobile robots – with status, current state and error messages, battery level, position, path network and current transport order, as with VDA5050 vehicles. Instant actions and the planned route are not available for MiR vehicles.
  • Mission mapping for MiR vehicles now supports dual cycles with two source and two destination locations each, as well as wildcards (* and ?) in the location specifications. Grouped transport orders can thus be driven with a suitable MiR mission, and one mapping entry covers many locations at once.
  • Faulty responses from connected vehicle systems are now logged by the vendor connectors with HTTP status code and response content. Connection problems, for example via a gateway or the Cloud Connector, can thus be narrowed down more quickly.

Product Settings

  • Search and filter entries in the log view, including the selected time period, are now stored in the URL. Filtered log views are thus retained after reloading the page and can be saved as bookmarks or shared as a link.
  • Logging has been extended: changes to the central configuration and changes from the transport order overview are logged with timestamp, user and old and new value, and the log level can be set per function instead of only system-wide. In the event of an error, it is thus traceable who changed what and when, and detailed logs can be activated specifically for individual functions.
  • Background jobs such as order creation, archiving, SAP synchronizations and cleanup jobs are now automatically distributed across multiple instances when several instances are operated. If an instance fails, another one takes over the job after one minute at the latest, and aborted runs no longer block a job permanently. Synchronizations with SAP and other background processes thus continue to run even if instances fail.
  • The overview of background jobs now shows the duration of the last execution. Unusually long run times of individual jobs can thus be identified immediately.
  • The appearance and behavior of the save button have been standardized on the pages resource type, configuration of conditions for EWM, WM, MM, PP and LGM, and dashboards. Users thus find the save function in the same place and with the same behavior on these pages.
  • The user interface is based on an updated SAPUI5 version; operation remains unchanged.

Bug Fixes

Dialogs

  • In the dialog “Drive tour”, with continuous tour planning active, the tour is now also replanned and filled up with further open transport orders of the route after several transport orders are dropped at the same time – for example with consolidated transport orders. Previously, the tour remained under-filled in this case until a single transport order was dropped again.
  • In the dialogs “Drive transport order with list” and “Free pick-up”, transport orders no longer disappear from the list without notice if they were confirmed or cancelled externally, assigned to another resource or their path was blocked. When reloading, the driver receives a warning that names the affected transport orders.
  • In the dialog “Free pick-up”, with validation active and automatic drop switched off, the drop button now remains disabled until the destination location of the selected transport order has been successfully validated – also after a drop, a rejection or a change of order. Transport orders can therefore no longer be completed without scanning the destination location.
  • The switch for continuing tours on the same route without changing routes is now effective. If it is deactivated, the driver is taken to the route overview after completing a tour and can choose the next route, for example based on overdue transport orders.
  • In the transport order PDF with user-defined fields, the field label and value are now aligned even for long, wrapping texts. The printed transport order documents thus remain clearly legible.
  • The button for automatic transport order assignment now remains visible and usable in the dialog for every screen format. Previously, it disappeared after a format change until the dialog was opened again.
  • If the second PDF print template is selected in the dialog, this selection now remains visible after reloading. The correct template was already printed before; only the display jumped back to the first template.

Layout Editor

  • Several issues in the Layout Editor have been fixed: the dialog “Parallel changes detected” now only appears for actual changes by other users and also reports layout IDs that are already in use, together with the layout and user. Undo now works in the correct path network and updates the detail area, a LIF import no longer removes a previously opened path network, the detail area no longer flickers during input, and changing the displayed vehicle type on an edge no longer reports unsaved changes. In addition, the term “path network” has been standardized in the user interface.
  • The save logic of the Layout Editor has been additionally safeguarded so that changes to layouts can no longer remain unsaved unnoticed. Saving remains unchanged for users.

Order Management

  • The number of transport orders per status on the quick creation buttons is now updated much faster – even if the status changes outside the dialog, for example when a transport order goes into fault. Users can thus see promptly how many transport orders are open, in process or in fault.
  • If the creation status in a quick creation is changed from “Reserved” to another status, the previously stored resource is no longer used when creating transport orders.
  • In the transport order overview, search fields (e.g. material number) and selection filters (e.g. status or location) are now applied together. Previously, set selection filters were ignored as soon as a search field was filled, so that unwanted transport orders also appeared in the result list.
  • Customized table columns are now retained after reloading the page instead of reverting to the default columns.
  • If the creation status “Inactive” is configured for the triggering transport order in a chaining, the transport order is now also created with this status instead of “Ready”.
  • If the due date of a transport order is supplied via external data enrichment before the transport order has been completely created, the buffered value is now reliably added afterwards. Affected transport orders no longer have to be activated manually.
  • The tour overview now loads reliably even with many tours and shows the tours in the calendar. Previously, loading could abort with a server error, especially if the transport order overview had been opened beforehand.

SAP

  • If the confirmation of a transfer order fails in SAP WM, the corresponding transport order in FlexGuide4 is no longer completed anyway. The transport order remains open, so that the automatic retry takes effect and the stock levels in SAP and FlexGuide4 do not diverge.
  • When confirming a warehouse task to a resource in SAP EWM, the system now checks whether a resource is specified. If it is missing, the confirmation is rejected with a clear message instead of posting the warehouse task to an empty target resource and creating an inconsistent state in EWM.
  • The configured interval for SAP WM synchronization is now taken into account; previously, synchronization always ran every 10 seconds regardless of the setting.
  • SAP adapters can now only be started if the technically required information such as destination, base path and plant or warehouse number is maintained. Incomplete configurations are thus noticed immediately instead of filling the log with connection errors.

Vendor Connector

  • The mapping table in the MiR vendor connector now assigns locations via the names of the MiR positions instead of requiring their technical IDs. Time-consuming determination and maintenance of the IDs is no longer necessary, and transport orders are reliably handed over to the MiR vehicle.
  • The status of a vendor connector is no longer changed by importing a customizing. Previously, a connector could be displayed as online after the import even though it was not running.

Product Settings

  • Several security vulnerabilities in the SAP application router used (SAP Security Note 3786038, CVSS 7.0) have been closed by updating to the corrected version.
  • In the English user interface, the menu area “Administration” is now called “Operations”. The name makes it clearer that no administrative settings are made there.

Hotfixes FlexGuide v2.15

Changelog Release 2.15.3
Changelog Release 2.15.2
Changelog Release 2.15.1