Changelog

Fixed a bug where collection options that were set to enabled=false in Data Shop scripts were no longer shown in the Classic UI. Disabled collection entries are now displayed again and marked as disabled, so fixed values remain available while still being excluded from editing. Other drop-downs continue to show only enabled objects, so their behavior remains unchanged. This ensures that collection parameters now consistently include all defined values, including entries that are intentionally disabled.

Users can now start an automatic generator creation action directly from the entity list. The action lets users choose a domain model and then creates generators for the included domain entities in one step. After completion, users see a list of all generated generators, making the result transparent immediately. Existing generators with matching names are kept unchanged, so no existing configuration is overwritten.

File Scenarios can now be configured so generated files are attached directly to the related execution. When enabled, users see a Generated Files list on the execution detail page and can download each file directly there. When disabled, the execution detail page does not show generated files and the previous behavior remains unchanged.

Published announcements are now prominently displayed on the login page above the login form, ensuring users see important information before signing in. On the dashboard, relevant announcements appear as the first content element and can be collapsed, with the collapse state remembered for the current browser session. In the head bar area, announcements are shown as a bar below the header and switch automatically in a carousel when multiple messages are available, while still allowing manual navigation. All announcements are visually distinguished by type (info, error, maintenance) with dedicated colors and icons, and support formatted text via Markdown where configured.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Introduced the new “Data Index” object to provide a central, searchable overview of available test data per environment and accordingly application models. Users can now easily identify suitable test data sets based on business characteristics instead of searching directly in source systems. This helps to quickly find and reuse appropriate data for testing scenarios and to prepare data for Data Shop orders.

This new feature may only become available once the epic XDEV-2021 - XDM MCP Server has been fully completed. Information on the current development of epics can be found at epic overview.

Task executions can now be exported directly with a dedicated export action. The export is available in the task execution context where users manage and inspect execution results. This makes it easier to share execution outcomes with colleagues and use them in follow-up analysis. Users get faster access to execution data outside the application without manual copy steps.

Replaced a previous error message with a new warning to indicate the potential issue with the rule definition of a Data Relation Rule, if the same column is mentioned twice.

Fixed a bug where the extract failed while copying TEXT Columns in Postgres with values larger than 100MB.

Fixed a bug where conditional scripts in Data Relation Rules did not work correctly when working with null values. Now both conditional and lookup scripts in Data Relation Rules treat null values as real nulls instead of placeholder strings, ensuring that scripts can reliably check for and handle null values as intended.

Form inputs are now preserved when adding custom parameters across all affected forms. Users can attach one or more custom parameters without previously entered values (such as names, connections, or schemas) being cleared. The button for adding custom parameters has been renamed to “Attach” to make its function clearer.

After deleting an object, users are now correctly redirected back to the updated list view. The deleted item no longer appears in the list, and no erroneous “An unknown error occurred.” messages are shown.

The execution detail view now shows the backend-provided reason message for canceled workflow and task executions, in addition to the CANCELED status. Users can immediately see why an execution was stopped, such as missing heartbeat signals, without leaving the detail view. Error and status messages are displayed consistently whenever they are provided by the backend.

The Workflow Checker now evaluates complex call paths correctly when a workflow is referenced both indirectly and directly. False cycle detection no longer raised in this scenario. Users can save affected workflows without being blocked by an incorrect cycle error.

Clicking an Attribute Generator in the Entity Generator view now reliably opens the correct Attribute Generator detail. This fix ensures that the displayed list and the linked detail view stay in sync, preventing navigation to the wrong Attribute Generator.

For binary XDM File objects, the UI now shows a clear notice instead of raw Base64 content. In both view and edit mode, the code editor is hidden when the file content is binary. This prevents unreadable content from being displayed and avoids confusion during data inspection. Text-based file content continues to be displayed as before.

The documentation was updated with general security recommendations, addition of concrete guidance on rootless containers and restricted DB users.

For Docker installations the XDM containers xdm3-core, xdm3-dataflow, xdm3-webui and xdm3-prime-ui now run as non-root user 1000:1000 by default.

Running RLP tasks with Groovy-based modification methods could fail stating that a modification method was not found, even though it was successfully executed earlier. This was caused by using soft collection for method references in the Groovy context. Now, Groovy scripts use hard references by default, which prevents this issue. See Groovy Script references for more information.

A new guide explaining risk class–based address masking has been added. Risk classes are used to classify natural hazards according to their severity. Sensitive addresses can be replaced with alternative addresses from the same or a similar risk class while maintaining the validity of the underlying risk assessment. It can be found here

In some situations, a Db2 on z/OS database did not provide labels for the metadata it returns. This lead to errors in the schema browser and table browser. Now, XDM uses the column index instead of the label to avoid this problem.

In some cases, the traversal trail of a data relation could not be followed. This previously caused the entire apply process to fail with an error. This error is now treated as a warning, allowing the apply process to continue.

An initial MCP agent service was added to the XDM installation as a dedicated prototype component. MCP tools were introduced for both the Consumer View and the Operator View to support MCP specific interactions. Internally, the solution was structured into specialized agents, each responsible for a dedicated task. The current delivery state is a prototype that will be iteratively extended and refined in future iterations.

This new feature may only become available once the epic XDEV-2021 - XDM MCP Server has been fully completed. Information on the current development of epics can be found at epic overview.

XDM now lets users import a domain model directly from a database schema. Users can select a connection, choose a schema, and pick one or more tables to import. For each selected table, XDM creates a corresponding domain entity with attributes based on the table columns. Foreign key relationships are reflected as mappings between the generated domain entities, and the imported entities are immediately visible in the domain model.

In Mapping, Selection, and Ignore Difference Rules, the Active column is now shown by default. Users can immediately see whether each rule is active or inactive without extra setup. The column is visible as soon as the relevant views are opened. This behavior applies consistently to all existing rules in those areas.

Users can now export list data as CSV files directly from the lists view through a dedicated export dialog. Before starting the export, users can choose the delimiter and select which columns to include, as well as define their column order for the CSV output. The export respects all currently active filters on the list so that only the filtered entries are exported.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed a bug in the Entity Copy Task, where the assignment of partitions from a Kafka Topic did not work correctly when a start timestamp filter was set, and the resulting messages are only present in some of the partitions.

In this case, the error You can only check the position for partitions assigned to this consumer occurred. This is now fixed, so that the expected messages are copied correctly.

When using script-based mapping rules for columns that access the baseObject (for example in JavaScript-based mapping rules [3]), a regression could occur in CTC/RLP-like tasks that read serialized files and map the contained columns. Under certain conditions, baseObject.columnProvider could be null, so calls such as:

failed with:

TypeError: null has no such function "getName"

This prevented the affected mapping rule from being executed.

The internal handling of the baseObject in these scenarios has been corrected so that:

If a column in the source and target tables had the same name but a different data type, and additionally, a column in the target table did not exist in the source table, but was filled by a modification method, the Data Extractor failed with an IllegalArgumentException due to a column count mismatch.

Lists with custom columns now refresh immediately so values in those columns are displayed without delay. Users now see complete row data after adding or updating custom columns, making configurable list views clearer and more reliable.

Fixed a bug in the Entity Copy Task, where the assignment of partitions from a Kafka Topic did not work correctly when a start timestamp filter was set, and the resulting messages are only present in some of the partitions.

In this case, the error You can only check the position for partitions assigned to this consumer occurred. This is now fixed, so that the expected messages are copied correctly.

If a column in the source and target tables had the same name but a different data type, and additionally, a column in the target table did not exist in the source table, but was filled by a modification method, the Data Extractor failed with an IllegalArgumentException due to a column count mismatch.

Fixed a bug in the Entity Copy Task, where the assignment of partitions from a Kafka Topic did not work correctly when a start timestamp filter was set, and the resulting messages are only present in some of the partitions.

In this case, the error You can only check the position for partitions assigned to this consumer occurred. This is now fixed, so that the expected messages are copied correctly.

If a column in the source and target tables had the same name but a different data type, and additionally, a column in the target table did not exist in the source table, but was filled by a modification method, the Data Extractor failed with an IllegalArgumentException due to a column count mismatch.

Added a new parameter called Disable Indexes Before Load in the tab Other Options under Processing for Native Table Copy Tasks and Native Table From Icebox Tasks. It is used to deactivate all indexes before the copying process, decreasing the total runtime of the copying process. After the copying process is finished, all indexes are reactivated again. Note that a task using this option can only be executed if the used database system supports deactivating indexes. Currently only Oracle and MS SQL Server databases support this option. This option is deactivated by default.

More Information about the parameter can be found here.

Users can now import rule lists directly from CSV files through a dedicated import dialog. The dialog allows choosing a CSV file, specifying a custom delimiter with a default of semicolon, and selecting between “Add” or “Replace” import modes. Depending on the selected mode, entries are either added to existing rule lists or replace and merge existing entries. After the import, users receive clear visual feedback indicating success or failure and, where available, the number of affected entries.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Files can now be uploaded directly to File and Mapping Table containers whenever the upload action is available. A dedicated upload dialog allows selecting exactly one file, with the file chooser restricted to the appropriate file types for the current container. During upload, a progress indicator is displayed in the dialog. After completion, a toast confirms successful uploads, while clear error messages are shown in the dialog if the upload fails.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Users can now clear a mapping table container to remove all contained entries in a single action. Before clearing, a confirmation dialog explains the impact and lets users cancel if needed. After successful clearing, a toast notification provides visual feedback. If clearing fails, an error message is shown directly in the dialog so users understand what went wrong.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Users can now download the contents of file and mapping table containers directly from the application whenever a download option is available. A confirmation dialog clearly informs users about the download and starts the process once the download button is confirmed. While the download is being prepared, the download button shows a loading state for better feedback. On success, the data is downloaded as a file named after the selected file or mapping table container, and in case of an error, a clear error message is shown in the dialog.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed an issue where the application model was missing (null) for row level delete tasks in the Stage 3 Apply Row Operations report. Additionally, the corresponding stage log now correctly shows the display name of the application model for row level delete tasks.

Fixed an issue where the Helm Chart property xdm.jwt.token-valid-time was not correctly propagated to the deployment, causing the default value to be used instead of the configured one. Note that the property has been renamed to xdm.core.jwt.token-valid-time but can still be set using the old name for backward compatibility.

Additionally, the Helm Chart property xdm.core.jwt.token.expire-time has been renamed to xdm.core.jwt.token-expire-time to align with the naming convention of the above-mentioned property. As well, the old name can still be used for backward compatibility.

Improved the task scheduling to make it more stable under highly parallel conditions.

Fixed a bug where an Exclude Rule in a Compatibility Table Copy Task did not recognize generated always columns as identity columns. This caused the execution to be aborted in stage one. The Exclude Rule logic was updated to correctly identify generated always columns as identity columns, allowing the task to execute successfully when such columns are present.

The Consumer view button is now visible and accessible to all standard XDM users, not just admins. This allows administrators and users to switch directly to the consumer view. The consumer view opens in a separate browser tab.

Row actions in embedded entity lists now stay on the parent entity detail view instead of unexpectedly navigating to the selected child entity. When triggering a delete from an embedded list, the confirmation dialog opens while the underlying view remains on the original entity, and after confirming, you stay on that same parent detail view. Navigation after executing a row action now only occurs if it is explicitly requested by the corresponding action, preventing unintended context switches.

The tables ADDRESSES and FIRST_NAMES in the default mapping table container contained formatting inconsistencies. These included invalid house number formats (e.g. ranges instead of single values), improperly formatted fields (e.g. semicolon-separated entries), and street values exceeding 80 characters.

All issues have been corrected to ensure consistent formatting and valid, realistic address data. To use the updated data, the mapping table container must be downloaded and re-imported.

Kafka sources now support configuring an optional consumer group for protected topics. This allows XDM Kafka users to align the Kafka consumer with the permissions configured on the Kafka broker, ensuring that the consumer can successfully access and read from the required topics.

The consumer group can be set on the Kafka topic and, if needed, overridden in the Entity Copy Task Template. When reading from Kafka topics, the consumer uses the configured consumer group. If no consumer group is configured, the default group ID is used.

With function level FL509, DB2 for z/OS introduced a new product signature (PRID) format that includes alphanumeric characters (e.g., DSN1301A). This caused issues in version parsing inside XDM, which expected a purely numeric format. The version parsing logic has been updated to handle the new format correctly.

The display of permissions and related entries has been improved to better match the current view and user context. Depending on where the information is opened, only the fields and details that are relevant for that specific situation are shown. This creates a clearer and more consistent user experience and makes permission settings easier to understand.

The execution view has been enhanced to provide information about the workflow execution progress and status. Users can now see the overall workflow progress, including the current step and its status, as well as logs and details for each stage of the workflow.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

A Content Security Policy has been added for both the Classic UI and the Prime UI to improve browser security. This limits which sources can be used for loading content and helps reduce the risk of unwanted or unsafe content being executed. It also prevents the application from being embedded in external frames.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

Local user passwords should be stored as SHA-256 hashes, rather than in plain text or using insecure hashing methods. On startup, the system issues a warning if weak password hashing methods are detected in the users.txt configuration. This warning is displayed for each user for whom an insecure algorithm has been configured.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

Added validation for SQL in task execution reports to block calls to disallowed stored procedures and functions. PostgreSQL procedures or functions starting with pg_ are now rejected, while common standard functions remain allowed. If disallowed SQL is detected, execution is skipped, no report data is returned, and the user receives a clear security-related message.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

After every successful login, the application now issues a new session so previously known session IDs can no longer be reused for the authenticated session. Users remain signed in and can continue using the application normally with their existing permissions and functions unchanged. When logging out, the session cookie is removed to help ensure the session is properly ended.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

The new interactive database browser component allows users to explore the structure and content of connected databases directly within the XDM interface. Users can view schemas, tables, and columns, as well as data, without needing to switch to an external database management tool. This feature provides a convenient way to understand the data sources being used in tasks and workflows, and to quickly verify the structure of the data before configuring tasks that depend on specific database schemas.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

After login, the xdm_session cookie is now marked as Secure. This helps protect authenticated sessions by ensuring the cookie is only sent over secure HTTPS connections.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

The communication between backend and front end used Cross-Origin Resource Sharing (CORS) headers to allow browser-based access to the application. These headers are not required anymore, reducing unnecessary browser access to the application.

This new feature may only become available once the epic XDEV-2022 - Penetration Test Findings has been fully completed. Information on the current development of epics can be found at epic overview.

If the subset apply of XDM could not insert a row into a database table due to a discard, it will no longer attempt to insert child rows when using the fill mode APPEND. This prevents that parent rows will have duplicated child rows as previously both the original and the generated row would be present.

Furthermore, in all fill modes, rows will be listed as cascade discards in the apply statistics instead of normal discards if their parent row was also discarded.

When using multiple interdependent Attribute Generators in an Entity Scenario Generator, the creation order specified in the entityGenerationConfiguration was not correctly taken into account. Now, the Attribute Generators are processed in the order in which they are specified in the entityGenerationConfiguration of the Entity Scenario Generator.

Fixed an issue where the value drop-down for mapped form parameters stayed empty when adding a new possible value. The drop-down now correctly shows the available XDM objects and saves the selected entry properly. The default value is no longer a mandatory field.

When using multiple interdependent Attribute Generators in an Entity Scenario Generator, the creation order specified in the entityGenerationConfiguration was not correctly taken into account. Now, the Attribute Generators are processed in the order in which they are specified in the entityGenerationConfiguration of the Entity Scenario Generator.

Fixed an issue where Subset Extract with a user-defined primary key on the start table failed with an IndexOutOfBoundsException. The primary key is now handled correctly and all required columns are written as expected.

There is a new property Override Auto-Generated Values on Compatibility Table Copy Task Template, Compatibility Table From Icebox Task Template, Row Level Processor From Icebox Task Template, Row Level Processor Task Template. By setting this property true, the task will copy the values of auto-generated columns from source to target database, instead of letting the target database generate new values. The property is only supported for PostgreSQL databases so far.

Postgres does not allow overriding auto-generated columns that are not identity columns, and only allows this in INSERT statements, not in UPDATE statements. Therefor, this property is only supported for identity columns in combination with one of the Fill Modes INSERT and TABLE REPLACE.

Added support to configure path-style access for AWS S3-compatible storage. Further information can be found here.

Added Entity Filter Rule support for Entity Copy Tasks to filter copied records based on the payload. With a Filter script, you can access the payload of an entity record and decide, if it should be filtered.

Entity Filter Rules can be defined on a Domain Entity or an Entity Copy Task / Template. Filtering on the Domain Entity is applied before processing the Entity Filter Rules on the Entity Copy Template and the Entity Copy Task.

Further details and examples concerning the Entity Filter Rules can be found in the Entity filter rules section of the user manual.

This new feature may only become available once the epic XDEV-2000 - Support for Kafka Topics has been fully completed. Information on the current development of epics can be found at epic overview.

Added a database index on the task_execution_classification_term_data table to improve query performance while generating task execution reports.

Permission settings have been improved and made more consistent across the application. Users can now also manage list permissions directly in the Task Template list. Permission views were updated to provide a clearer and more uniform layout. In addition, Object Types in default permissions are now easier to manage with a two-column checkbox list, including select all or none options.

All list views now include a Refresh button in the action bar, so users can quickly reload the currently displayed data.

An About page is now available from the footer in both the Consumer and Operator views. It gives users quick access to key product information such as the current application version, manufacturer and contact details. The footer also now includes direct links to the UBS Hainer website and the accessibility information in the manual, while the application version is additionally shown on the login screen.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

XDM users can now approve or reject requested executions directly in the user interface. The actions are available in the list view as primary actions and also on the requested execution itself when supported. Approving opens a confirmation dialog, while rejecting allows users to enter a reason for the decision. After completion, the user receives clear success or error feedback, and approved executions can also be opened directly for further follow-up.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Announcements can now be published or hidden using dedicated actions when these options are available. Before the visibility status is changed, a confirmation dialog clearly explains whether the announcement will be made visible or hidden. After the action is completed, users receive a toast message confirming success or showing an error if the change could not be applied.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed an error that caused tasks to crash when using generated scripts with domain model or entity names containing invalid characters, which resulted in non-compilable class names. Names are now being sanitized into valid, conflict-free class names.

When adding a grantee in object permissions, the user selection list is now shown in alphabetical order. This makes it easier to find the right person in larger user lists and improves overall usability. The sorting is based on each user’s display name to provide a clear and predictable order.

When you add one or more tags while editing an object and save your changes, the selected tags now remain assigned to that object. The tags are still visible after saving and also when reopening the same object later. To make this area clearer, the label in the entity details view has been renamed from Tag Filter to Selected Tags.

When navigating from an entity list via the context menu into related sublists (e.g. Rules, Usages, History), the application now correctly opens the corresponding entity details view with the appropriate tab selected. Previously, users were redirected to a separate list view that was not accessible through the standard navigation and could only be identified via breadcrumbs. This change ensures consistent navigation behavior and improves usability when accessing related entity information.

Revalidation now refreshes affected fields more reliably in task templates and related selections. Lists based on domain models, task template properties, and custom default values are now updated more consistently after changes. This helps ensure that users see the current available options and values without needing repeated attempts.

Users can now reliably update the Active/Inactive status while editing an item. Previously, the selection could be changed in the form, but saving did not apply the new value and showed a failed save message. This has been fixed so the selected status is now correctly sent and stored after saving.

Implemented API token creation and management in User Settings. Implemented token-based authentication for the XDM REST API, enabling users to authenticate using API tokens and thereby improve the support of non-interactive, automated pipelines and integrations with external systems. For further details on how to create and use API tokens, please refer to the Token Based Authentication section of the user manual.

Modification Methods were updated to expose all source columns (including dropped ones) and any additional SELECT-only columns, improving flexibility for complex modifications and migrations. Internal processing was adjusted to handle mapped column names, additional target columns and complex migration scenarios correctly.

This new feature may only become available once the epic XDEV-2013 - Batch Row Refactoring has been fully completed. Information on the current development of epics can be found at epic overview.

The performance of entity copy tasks with kafka topics has been improved. The functionality of the microservices modification-processor, kafka-sink and kafka-source is now integrated into the dataflow server.

The task template detail view has been streamlined to make it easier to use, especially for users who are less familiar with XDM. By default, only the most relevant fields are shown, while expert-level properties are hidden from the main view. If needed, users can still open an overview dialog to see all available properties with their current values.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Several UI views were reviewed and improved to provide a more consistent and user-friendly experience. Field layouts were reorganized to remove unnecessary empty spaces and to ensure that related fields are placed closer together. Groups and sections within forms were streamlined where possible, resulting in clearer and more intuitive detail views.

In addition, recurring fields such as Display Name and Description are now positioned more consistently across different views, helping users find commonly used information more quickly. Some configuration areas were simplified, and related settings were consolidated to better reflect their functional relationships.

List views were aligned with the Classic UI by adjusting the default column configuration so that commonly used information is visible by default. Naming conventions and certain labels were also brought closer to the Classic UI to provide a more familiar experience for existing users.

The display of property fields has been updated to improve readability. Labels are now shown in italic, while set values are highlighted in bold. Empty fields remain easy to identify through an italic and bold empty message. This helps users recognize filled and unfilled fields more quickly.

Task executions can now be managed more precisely with dedicated actions for Resume, Restart, Cancel, and Cleanup whenever these options are available. Resume and Restart now also offer an "and View" variant, so users can jump directly to the newly started or continued execution. Clear confirmation dialogs and feedback messages help users to understand what will happen and whether the action was successful. This makes it easier to continue interrupted runs, restart executions, stop active ones, or clean up no longer needed execution files.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

XDM users can now schedule tasks and workflows directly when the corresponding schedule action is available. For scheduled task executions, pause and resume actions are now available when supported by the object and its links. Scheduling supports either a future start time or a cron expression, and the UI guides users with confirmation/error dialogs and success feedback after execution.

This new feature may only become available once the epic XDEV-2011 - UI Modernization has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed an issue where it was not possible to load tables that include generated always system-period columns without a history table in DB2 LUW. In this situation, the load was marked as successful, but the target was empty. Also, a warning message has been added for situations where 0 rows are loaded into the target, with a reference to the utility message that caused this.

In some cases, creating a credential was not possible. After entering the data and clicking Save, an error message was shown and the credential was not created. Credentials can now be created successfully again.

Added Entity Filter Rule support for Entity Copy Tasks to filter copied records based on the payload. With a Filter script, you can access the payload of an entity record and decide, if it should be filtered.

Entity Filter Rules can be defined on a Domain Entity or an Entity Copy Task / Template. Filtering on the Domain Entity is applied before processing the Entity Filter Rules on the Entity Copy Template and the Entity Copy Task.

Further details and examples concerning the Entity Filter Rules can be found in the Entity filter rules section of the user manual.

This new feature may only become available once the epic XDEV-2000 - Support for Kafka Topics has been fully completed. Information on the current development of epics can be found at epic overview.

The Entity Copy Task now supports Entity Modification Methods, allowing the users to adjust the data during the copy process. These Entity Modification Methods are linked to a Domain Entity with the use of an Entity Modification Rule. The documentation has been extended with additional examples and usage notes to demonstrate how to utilize modification methods in Entity Copy Tasks effectively.

This new feature may only become available once the epic XDEV-2000 - Support for Kafka Topics has been fully completed. Information on the current development of epics can be found at epic overview.

Increased the maximum credential password length from 512 characters to 1MB to allow storing and using long tokens (e.g., JWT) directly in credentials and accessing them in Stage Hooks, avoiding insecure storage in config files. Existing credentials continued to work unchanged.

The new clear and organized display of parameters makes managing embedded objects intuitive through a simple and user-friendly interface:

A common application would be, for example: A user is working on a data shop with various configuration parameters. The new feature allows the user to easily add, edit, and delete parameters without needing to manually adjust the underlying data structure. If a parameter is deleted, the change is instantly reflected in the parent system, which updates the data accordingly.

Known issue: When creating a new form parameter in a data shop that uses mapped properties referencing another XDM object (e.g., targetEnvironment), the "Possible Values" drop-down appears empty, although it should display the XDM objects.

Fixed an issue where the report generation appeared to be stalled. The stage was marked complete in the logs but still shown as running in the UI. Updated stage status handling to reflect ongoing processing until reports are fully generated.

Fixed an issue where Domain Entities created via JSON import included an empty endpoints array, causing Entity Copy Tasks using the entity to fail with an internal server error. The import logic was updated to no longer generate the endpoints array when empty, allowing tasks to complete successfully.

Registering a new Icebox generation became increasingly slow as more generations accumulated. For example, with ~8,000 generations on a task template, the registration step could take several minutes.

Root cause: the registration step retrieved the full list of existing generations to calculate the next generation number. Fix: the step now fetches only the latest generation and derives the next number from it.

This change was implemented in a central/shared code path and may improve performance in other areas as well (e.g., workflows creating new tasks from task templates when many tasks already exist).

To enhance the performance of XDM overall, modifications have been made to the underlying database schema. The way in which object parameters were stored in the SingleValueParameter and MultiValueParameter tables has changed. Parameters are now stored directly as JSONB columns on the respective objects. This significantly reduces the number of database queries required to resolve parameters, resulting in shorter loading times and improved performance for various XDM actions, including the pre-execution check, RebuildGraph and other operations involving intensive parameter access.

The SingleValueParameter and MultiValueParameter tables will remain in place for the time being. The parameter tables linking the objects to the parameters are also retained. Existing data will be migrated to the new JSONB format automatically when the application is started, ensuring the original dataset remains available during the transition period.

The Neo4j-based XDM relationship store has been replaced with a simple Postgres table. Existing relationships will be created automatically in the new table when the core-server is started for the first time. Referencing behavior remains the same – objects cannot be deleted as long as dependent relationships exist.

The Neo4j container and the associated settings are therefore obsolete. In Docker setups, the Neo4j service should be removed from docker-compose.yaml, and the following environment variables should be deleted from the core-server and dataflow-server configuration.

No further adjustments are necessary for Kubernetes installations, provided that the current Helm Chart is used – the Neo4j container has already been removed there.

Fixed a bug where the Exclude Rule for column A caused modified data to be incorrectly inserted into column B instead of being excluded as intended. The Modification Rule now correctly ignores changes when column A is excluded, ensuring that data for column A is ignored and remains excluded without affecting other columns.

Trying to delete a Permission Recipient with user default permissions caused a 500 error. The deletion process was updated to ensure that it completes successfully without errors.

Fixed an issue where automatically generated keys from Db2 were not correctly transferred to dependent columns in PostgreSQL during RLP copy. The fix ensured that the 'Generated Always' columns were included in the generated columns list, allowing the generated keys to be accurately stored in the referenced table, thus maintaining the integrity of data relationships.

When Groovy Scripts were called many times during a very long workflow or a task execution, it could happen that a MissingMethodException was thrown after some time, causing the execution to fail. This was caused by a setting in the Groovy Script engine, that used soft references for generated classes. Therefore, classes could be removed by the garbage collector, which caused the exception. To prevent this issue, you can now set this new environment variable in the dataflow container:

xdm.script.groovy.hardReferences=true

Further information about this setting can be found in the configuration of Groovy script references section of the user manual.

When using a RLP Task with fill mode MERGE and a user-defined primary key on a nullable column, the comparison with NULL values always generated an INSERT instead of a MERGE SQL statement. User-defined primary keys now have a new flag markNullValuesIdentical which defines whether two NULL values are equal or not. The MERGE ON clause was updated to correctly compare NULL values. When comparing nullable columns, a cast to the correct datatype was added because NULL values have no valid datatype.

The Entity Copy Task now supports Entity Modification Methods, allowing the users to adjust the data during the copy process. These Entity Modification Methods are linked to a Domain Entity with the use of an Entity Modification Rule. The documentation has been extended with additional examples and usage notes to demonstrate how to utilize modification methods in Entity Copy Tasks effectively.

This new feature may only become available once the epic XDEV-2000 - Support for Kafka Topics has been fully completed. Information on the current development of epics can be found at epic overview.

When Groovy Scripts were called many times during a very long workflow or a task execution, it could happen that a MissingMethodException was thrown after some time, causing the execution to fail. This was caused by a setting in the Groovy Script engine, that used soft references for generated classes. Therefore, classes could be removed by the garbage collector, which caused the exception. To prevent this issue, you can now set this new environment variable in the dataflow container:

xdm.script.groovy.hardReferences=true

Further information about this setting can be found in the configuration of Groovy script references section of the user manual.

Fixed Kafka Copy Task issues where some logs were missing in stage logs/exports and where offset gaps in a topic caused kafka-source to abort or copy messages incompletely. Also improved Error and Exception Handling.

The modification methods in the Configuration Object Repository are now provided as Groovy examples.

The JavaScript versions of these methods can still be used in XDM, but we recommend using the Groovy methods instead.

A new guide has been added that describes how to add a mapping table to XDM that acts as a shuffling table for data from an existing table. It can be found here.

A list of all system parameters was added to the custom parameter reference. The names of the system parameters can not be used as variable names for custom parameters.

Access to columns via index-based data has been replaced by access via column names. This ensures correct mapping and stable, error-free copies and changes in selection, exclude, mapping, modification and reduction scenarios, even when the order or number of columns changes. This change only affects the product code. Customer-defined scripts remain unaffected and do not require any adjustments.

This new feature may only become available once the epic XDEV-2013 - Batch Row Refactoring has been fully completed. Information on the current development of epics can be found at epic overview.

Added an import endpoint to Domain Entities that generated a configuration script from an uploaded JSON. Attributes were created for each top-level key, and lists/mappings are set to OBJECT. This enabled faster entity creation from example JSON without manual attribute setup.

More details can be found in the Domain Entity - Import List Action section of the user manual.

This new feature may only become available once the epic XDEV-2000 - Support for Kafka Topics has been fully completed. Information on the current development of epics can be found at epic overview.

Removed support for SSH private keys from Credentials because the private key was not implemented and therefore was not used in XDM. The following fields: Certificate based authentication, Key Format and Private Key, was removed to prevent clear-text display and export, and to eliminate any risk of unauthorized access or data leakage.

Fixed an issue where tasks ran extremely slowly when Trace logging was enabled, causing steps to appear stuck due to excessive log output. Logging was adjusted to reduce Trace verbosity, restoring normal step execution time. Internal HTTP payloads will no longer be logged.

Fixed an issue for entity copy tasks that copy from Kafka topics. When multiple Kafka messages shared the same key, only a single message was copied.

A complete overview of how to work with Configuration as Code (CasC) has been added to the Working with XDM section of the user manual. It can be found here.