Release Notes 7.4.11

X4BUG-1824

Server log: Error and adapter messages were previously logged in the server log without reference to the triggering process. As a result, a unique assignment was often not possible. This error is now fixed and log entries also contain the process ID (PID) or process context, so that warnings and errors can be uniquely assigned to the initiating process.

X4BUG-1838

Update Tool: The backup behavior has been changed. The --backup=/path/to/backup option can be used to specify a previously manually created backup directory. If the option is not set, the backup is created automatically.

X4DOC-294

Bing Maps Adapter: The Bing Maps adapter used so far is marked as deprecated due to the discontinuation of the underlying Microsoft API (May 2024, complete shutdown for Free Tier from June 2025). A successor based on Azure Maps will be provided in a future X4 BPMS version.

X4BUG-1829

Keycloak Management Adapter: For newly created users, the CreatedTimestamp element was incorrectly set to 0. This causes the Keycloak administration console to display the timestamp as 01.01.1970, 01:00:00 (Unix epoch). This bug is now fixed and the item contains the correct creation date and time of the user.

X4BUG-1869

Log4J Adapter: Process information was previously output with the PID (Process ID), while the system has internally switched to the PUID (Process Unique Identifier) since version 7.0. This led to inconsistencies in the traceability of log entries. The adapter now offers the option of logging either PID or PUID. For new systems, PUID is preset as the default; existing systems can choose between the two options.

X4BUG-1892

MQTT Publisher Adapter: In X4BPMS version 7.4.6, an error occurred while sending messages to a RabbitMQ server: Once the adapter was reached in the process, it hung up. No error was written to the server log, and when running from a Process Starter, the server eventually reached its resource or thread limits because processes did not terminate properly. This bug is now fixed.

X4BUG-1902

GDV Writer Adapter: The adapter used system encoding so far, which resulted in erroneous GDV files after the conversion from ISO-8859-1 to UTF-8. The adapter now supports explicit encoding. By default, ISO-8859-1 is used.