Changelog

In the Prime UI script editor, Ctrl+S (and Cmd+S on macOS) now saves changes both in the embedded editor and in full screen mode without leaving the current editing context. The browser default save-page action is suppressed, and the current working position in the code editor is preserved.

Side menu sublists are now displayed in alphabetical order to improve navigation clarity. The sorting automatically adapts to the currently selected language, which ensures a consistent menu structure. As part of this update, the sublist 'Events' was also moved from 'Executions & Monitoring' to 'System & Configuration.'

The result of "Check Admin Database" is now shown in a clearer and more structured way in Prime UI. This makes it easier for users to understand findings at a glance and act on relevant issues faster.

String-valued Modification Parameters that are null or left empty are once again passed as an empty string ("") instead of the literal string "null". This restores the behavior of previous versions and avoids requiring customers to adapt existing configurations. The definition of how a value is represented in a Modification Parameter is now documented in the Modification method reference section of the user manual.

When using Generic Extract in table copy tasks, Tablespace where mapped incorrectly. This could lead to a NullPointerException when minor structural differences between source and target tables were present.

Using an entity generator which produces different entity types, each type was stored into a separate Data Repository. Now, only one Data Repository is used for all entity types created by a generator source. Details about the entities found in a Data Repository can be seen in the meta information of the repository.

Logging in to XDM with an Active Directory account over LDAP now succeeds. This fixes an error when evaluating user fields that reported: “An Authentication object was not found in the SecurityContext.”

Generators for long text columns now create strings that are limited to a maximum of 1024 characters if not explicitly configured otherwise.

Opening a Modification Set no longer fails with a NullPointerException when its Modification Rules reference Modification Methods with parameters. The affected rule list is now loaded and displayed correctly in Prime UI.

Ordering a Data Shop in Prime UI no longer fails when the Data Shop has no parameters configured. The request handling now safely processes missing parameter resources and the order can be started as expected.

Entities that use the internal labelPrefix flag could not be saved in the Prime UI. For example, Data Repositories and Data Indexes could not be changed.

Generator-based entity processing now works with the shared Entity Node standard, improving compatibility with other supported connectors. Tasks that use a compatible connector now run in a dedicated “Direct Entity Processing” stage for clearer execution flow and transparency. Relevant processing logs are now available directly in the stage logs, making task behavior easier to follow during execution. The standalone generator-source service is therefore no longer required and can be removed from Docker Compose and Kubernetes environments.

Logging in to XDM with an Active Directory account over LDAP now succeeds. This fixes an error when evaluating user fields that reported: “An Authentication object was not found in the SecurityContext.”

Custom Parameters now support additional types: Kafka Topic, Webservice, Entity Generator Scenario, File Scenario, and Data Repository. These parameters can be set and used dynamically within workflows and via the Data Shop.

Administrators can now delete Data Repository entries directly from the Data Repository view when they are no longer needed. The deletion removes both the catalog entry and the associated stored data. Deletion is only possible if no existing task still references the repository for reading, ensuring that repositories in active use cannot be removed.

Now that this feature has been completed, the following previously blocked issues can be addressed.

This new feature may only become available once the epic XEP-8 - Test Data Repository has been fully completed. Information on the current development of epics can be found at epic overview.

It is now possible to use workflow parameters in Data Shops. Possible Parameters are Execution Platform, Execution Retention Period,Delete Execution Files On Success, Task Execution Report and all custom parameter defined on the workflow template.

Users can now not only set a date and time using the calendar but also enter them manually. This speeds up planning for later runs and working with announcements and API tokens.

Domain entity configuration scripts can now define an optional custom fetch function for data retrieval. This enables integrations where data must be loaded through non-GET endpoints, such as POST requests with payloads. If no custom fetch function is defined, the existing default fetch behavior remains unchanged for backward compatibility. For details and an example, see Domain Entities in a Webservice Context.

Prime UI now supports complete API token generation with a one-time token value display after creation. The token tab is shown only to users with the configured token-creation role. The result dialog includes a direct copy action and clearly states that the token value is shown only once. If token generation fails, users now receive immediate visual feedback via the existing notification mechanism.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed a bug where Native Table Copy Tasks failed in Stage 5 (Generic Extract) for Db2 z/OS tables in implicitly created databases. XDM now reads information on implicit tablespaces, uses internal default values when database or tablespace information is missing, allowing CSV writing to complete without a NullPointerException.

Fixed a thread leak in the Core Server that could cause resource exhaustion over time.

The overriding of Docker Memory Settings was ignored. Now it is possible to set the parameter value.

Long object names in the template view are now displayed more clearly without overlapping neighboring entries. Very detailed names are truncated, keeping the layout easy to read.

Attribute Generators with special characters in their names (such as “|”) are now correctly displayed in the selection list. Users can reliably find and select newly created Attribute Generators regardless of the characters used in their display names.

The Spring Framework version used in XDM has been updated to 4.1, which includes important security updates and bug fixes.

It is possible that some properties in your installation will need to be renamed or replaced. The PropertiesMigrationListener program logs the affected properties in the core-server log. The log entries begin with one of the following lines, followed by the affected property.

The login process now includes a throttling mechanism to prevent user enumeration attacks.

Domain entity configuration scripts can now define an optional custom fetch function for data retrieval. This enables integrations where data must be loaded through non-GET endpoints, such as POST requests with payloads. If no custom fetch function is defined, the existing default fetch behavior remains unchanged for backward compatibility. For details and an example, see Domain Entities in a Webservice Context.

It is now possible to configure if XDM should exclude encrypted passwords for credentials in XDM Object Exports. By default, they will be exported as before. More information can be found here.

The Kafka Schema Registry is now supported as a source for Avro schemas in Kafka Topic configurations. This enables XDM to retrieve Avro schemas from a centralized registry instead of requiring them to be defined directly in the Kafka Topic configuration.

The runtime stability of the Data Repository has been hardened as part of the first quality gate. Additional automated tests cover the core repository behavior as well as the Kafka-to-Data Repository and Data Repository-to-Kafka flows.

Typical creation and read edge cases were reviewed, corrected, and where appropriate secured with tests. Complex types such as arrays, lists, and maps are now serialized and deserialized as JSON in Parquet, which improves compatibility and reliability when storing structured values.

This new feature may only become available once the epic XEP-8 - Test Data Repository has been fully completed. Information on the current development of epics can be found at epic overview.

For multiple key selections with exactly one key column, XDM now generates an IN (?, ?, …​) predicate instead of an OR chain. This improves the generated SQL for many databases and can help the optimizer choose a more efficient access strategy.

The previous OR-based behavior remains unchanged for multi-column keys, custom key conditions, and cases where at least one key value is null. If required, the old behavior can also be enforced for single-column keys via the runtime property statementbuilder.forceOrForSingleColumnKeys=true.

In addition, the SQL Server and Azure SQL connection setup was adjusted so Unicode parameters are bound with the correct SQL types. This avoids implicit type conversions for Unicode string parameters and improves performance for affected statements.

Added guided rule creation support for database objects. Users can now pick existing schemas, tables, and columns from selection lists instead of looking up names manually. This reduces manual lookup effort and speeds up setup by presenting the right data options in context.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

When leaving an entity page with unsaved changes, Prime UI now asks whether you want to save or discard your edits. You can save and continue navigation immediately, or discard changes and leave without saving. If no changes were made, navigation continues directly without showing a confirmation dialog.

Users can now control the availability of a Data Shop with an Active status flag. When a Data Shop is marked as active, it is visible and available for order in both the operator and consumer views. When a Data Shop is marked as inactive, it remains available only in the operator view, while appearing disabled with an explanatory tooltip in the consumer view.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Prime UI can now be rolled out gradually to selected users while Classic UI remains available in parallel. Administrators can control per user which interface is used by default and adjust this assignment during operation. Users can switch between Classic UI and Prime UI directly via footer links in both interfaces. When users sign in through Classic UI, they are automatically redirected to Prime UI where applicable.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed a bug where renamed workflow templates and task templates appeared multiple times in "Top Execution Objects" and "Top 10 executions" in Grafana. Grafana now shows renamed workflow templates and task templates only once in those two charts. Execution counts remain accurate after a template has been renamed.

Fixed a bug where the “Cleanup expired execution jobs” process could fail when too many tasks, workflows, or executions were involved, causing the database query to exceed the maximum number of prepared statement parameters. Cleanup of expired executions now runs reliably even in large environments and successfully removes obsolete executions as expected.

Fixed a bug where Generation Tasks failed in Stage 1 when a Groovy library was used. It is now possible to run Generation Tasks without the task stopping early.

Sending emails via Send Email Hooks works again as expected. Workflows that use email hooks now complete successfully in the affected scenarios. The required email libraries have changed, so existing hook implementations may need to be updated accordingly. Imports used in custom hook scripts must be adjusted to match the updated libraries. Further information on the required changes can be found in the Send an e-mail after an execution finished section of the user manual.

The search in the "Delete Selected Objects" dialog is no longer limited to the Name column. Users can now also search by values from other displayed columns, including the Reason column. Search behavior is now consistent across all entries shown in the dialog list.

In Prime UI tables, the action menu now correctly renders all available actions even on very narrow screens or at high zoom levels (250% and above). Spurious empty rows are no longer shown in the menu.

In Prime UI edit dialogs, long descriptions no longer block vertical scrolling. Users can now scroll through the full form content even when description fields contain extensive text. This ensures all fields and actions remain reachable while editing.

Data Shop form parameters based on dynamic number fields are now displayed reliably in both Edit mode and the order view, even when a default value is configured.

Added a new guide that describes how to use a Row Level to Icebox task to generate SQL INSERT statements as a file-based target output. The guide explains how to configure an XDM file, a custom parameter, a row-based Groovy Modification Method, and a POST Stage2 Task Stage Hook to collect selected source rows and write them as SQL statements to an XDM file. This allows preparing data in XDM and execute the resulting SQL script outside XDM, for example when the target database cannot be configured as an XDM target connection.

Entity Copy Task Templates and individual tasks can now define their own Entity Modification Rules directly in the Rules section. This allows modifications to be controlled separately for each task when copying entities. Modification Rules are executed in the order Domain Entity, Task Template, and then Task. The Entity Modification Report was enhanced to show the source of each applied rule, so users can see which rules were applied from which level. An example on how to use the Entity Modification Method in an Entity Copy Task can be found in the configuration examples.

Now that this feature has been completed, the following previously blocked issues can be addressed.

A foundation for Data Repositories has been introduced for persistently storing copied data as reusable standalone objects in XDM.

Stored data can be used as a source for broader repository-based processing patterns in XDM, enabling more efficient data management and reuse. Data Repositories can be selected as both source and target in Entity Copy Tasks.

This feature is currently being developed in the background and will be fully rolled out in future releases.

This new feature may only become available once the epic XEP-8 - Test Data Repository has been fully completed. Information on the current development of epics can be found at epic overview.

In the entity view, long Description texts are now displayed in a compact form with the first two lines visible by default. Users can open the full text on demand via a dedicated "Show full" link whenever they need complete details. Line breaks entered in edit mode are now preserved in view mode, so formatted multi-line descriptions remain readable.

XDM Objects can now be organized in folders and subfolders to create a clear hierarchical structure. Operators can create, rename, move, and delete folders when they are empty, and can move both folders and XDM Objects. In the Consumer view, selecting a folder shows only the Data Shops from that folder and its subfolders, which makes navigation more focused.

Now that this feature has been completed, the following previously blocked issues can be addressed.

This new feature may only become available once the epic XEP-4 - Enhance Data Shop has been fully completed. Information on the current development of epics can be found at epic overview.

Users can now access the Grafana dashboard from the Prime UI by clicking the appropriate link in the footer, which opens the relevant monitoring and analytics view in a new browser tab.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Data shop users can now start a reorder directly from a past execution. Clicking the Reorder button from the execution redirects users to the related shop with values already pre-filled. This shortens repeat ordering and helps recreate successful requests faster.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Prime UI now includes an Apply action in the Default Permissions context. This action can be used to apply Default Permissions to already existing objects afterwards. Users can choose the supported apply modes (MERGE or REPLACE) to control how permissions are updated.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Added a Transfer Ownership action for Permission Recipient objects. Administrators can now open the Transfer Ownership dialog, select a new permission recipient, and transfer created objects to that user.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Credentials that started with a number or special character caused Kafka Topic configurations to fail due to a bug in the Apache Kafka Client. This problem has been resolved, so numbers and special characters can now be used in Kafka Topic Credentials normally.

When an Elasticsearch Container is configured within an XDM environment, it occurred that the core-server failed due to the Elasticsearch container not being up. This problem has now been fixed, as there is a proper optional health check implemented. For more information, see Central Search (Elasticsearch).

Added a new Security & Insights tab next to Overview in the Task Execution view, with a drop-down for Permissions and Events. Selecting either option now correctly displays the corresponding list. Stage tabs now open to the right to keep Overview and Security & Insights fixed, and closing the last stage tab returns the user to Overview. The Permissions and Events actions now also work correctly from the context menu.

In Prime UI, empty integer fields are now preserved as empty instead of being converted to 0. This fixes incorrect default values in Entity Copy Task Kafka settings, including Source Offset and Source Partition. As a result, tasks can be saved without unintended numeric values, matching the behavior already known from Classic UI.

Object reference links clicked inside dialogs now open in a new browser tab instead of replacing the current dialog context. The dialog in the original tab remains open and editable, so already entered unsaved values are preserved. This behavior is now consistent across dialog-based flows, including Property Flow dialogs and related action handlers.

Layout updates saved in Classic UI are now reflected in Prime UI for the same Data Shop. After saving a layout change, both user interfaces now show the same layout state instead of diverging. This synchronized behavior remains consistent when users reopen the same Data Shop.

Number parameters with configured option values are now shown as a selectable list instead of a numeric spinner. This ensures that users can choose from the intended predefined values in Data Shop forms. Number parameters without configured options keep the existing direct numeric input behavior.

The Jenkins plugin has been marked as deprecated and is no longer actively maintained. Existing installations may continue to work, but the plugin should not be used for new task configurations.

Added support for additional LLM providers for AI-related services, including Google, Azure, OpenAI, Anthropic, Mistral, and Ollama. This allows XDM administrators to configure their preferred provider for their organization via both the Helm chart and Docker Compose. The available settings are documented in the user manual to support easier deployment and administration across environments.

Error messages for write interruptions in the FileBridge Server have been improved to make technical root-cause analysis easier. Each accessor now logs the field it is currently processing when an error occurs. The log output now also includes buffer size and additional runtime details, and clearly shows the interruption context for the user.

The save button in the entity edit view is now visually highlighted as soon as a user makes a change, making it much easier to spot among the surrounding tabs. This highlighting clearly indicates that unsaved changes are present and remains active until all edits are saved or discarded, helping prevent accidental loss of work.

Users can now open an internal log directly from an execution using the new Internal Log action. The log is displayed in a readable dialog, making it easier to review the full output of a run without leaving the execution view. This helps users better understand execution behavior and resolve issues more quickly.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Users can now switch list views into edit mode and update supported values directly in table rows. Changes can be saved for edited rows or discarded at any time, including a prompt when leaving with unsaved edits. Validation and save errors are shown in the affected row, so issues can be corrected quickly without losing other updates.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Data Shop work spaces now use the available screen width instead of being constrained to a narrow centered column. Long log lines are easier to read in the default view, reducing the need for horizontal scrolling. Input areas with long lists provide more usable space, making review and editing more reliable across relevant Data Shop views.

Modification Sets now provide an optional modeling connection field. The Connection can be selected directly on the Modification Set and use it when modeling Modification Rules.

The start-condition editor now adapts immediately when the row selection mode changes. For Query mode, users get a prepared query suggestion to speed up configuration. For Number of Rows and Percentage modes, the start condition is shown as numeric input, including the valid percentage range. For File mode, users now get dedicated inputs for source file selection and column mapping.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

The entity action bar is now only shown on the details view of an object and no longer on non-editable subpages such as history. This prevents confusion about editing, deleting or exporting when viewing read-only information, while keeping breadcrumbs and tab navigation unchanged and consistent across all affected pages.

Fixed a bug where exporting Column Property Rules as CSV failed with an error.

Task executions failed randomly in XDM due to authentication errors. With this story, the authentication process has been made more robust.

Creating or editing a connection in XDM no longer triggers an automatic connection attempt to the underlying database. This prevents objects from failing to load when the target database is misconfigured, unreachable, or blocked by firewall rules. Connection details can now be created and edited independently of the database availability.

The Default Value drop-down in the Add and Edit Parameter dialogs now shows the expected selectable values for Form Parameters in Data Shops. When specific Possible Values are defined, only those values are offered as Default options. If no Possible Values are defined, the drop-down now shows all available options, making parameter setup clearer and more reliable.

German user-facing texts in Prime UI now use a consistent and clearer form of address. Wording in key dialogs, actions, and messages has been standardized to avoid mixed tone and improve readability. This ensures a more uniform language experience across the application.

Default values in custom parameters now show the referenced object name directly. Users can identify the selected connection immediately without relying on internal identifiers. Navigation from the displayed default value continues to open the referenced connection as expected.

The Task Execution Report option on a task now opens a fully populated drop-down when added as an override. All other options of type collection on a task now also display their available entries correctly instead of showing an empty list. Users can reliably select any of the listed items for Task Execution Reports and other collection-based options without encountering blank selections when valid entries exist.

Imported row-level task templates now render their expected fields correctly in Prime UI. The affected templates "Restore (Row Level From Icebox)" and "Delete (Row Level Delete)" no longer show only the "Custom Parameters" heading after import. Collection-based values from imported template data are now interpreted reliably, including edge cases with nested bracket formatting. This restores consistent template behavior between Prime UI and Classic UI for the impacted import scenario.

Local authentication using users.txt now completes successfully even when an external identity provider is configured. Users are redirected to the application after signing in without needing to refresh the browser. The misleading “Login failed: Bad credentials” message is no longer shown after a successful login.

The login process for LDAP and the local user management (e.g. my-users.txt) now includes a throttling mechanism to prevent brute-force attacks. If a user exceeds the maximum number of failed login attempts, their account will be locked for 10 minutes. For information on how to configure the maximum number of failed login attempts, see the Optional Parameters - Login Limiting section of the user manual.

Creating or editing a connection in XDM no longer triggers an automatic connection attempt to the underlying database. This prevents objects from failing to load when the target database is misconfigured, unreachable, or blocked by firewall rules. Connection details can now be created and edited independently of the database availability.

Users can now run a built-in configuration check directly on XDM objects to catch setup issues before they cause runtime problems. The check results show which objects were reviewed and what passed or failed, making troubleshooting faster and more transparent. Filterable results help users focus on the most important findings and resolve issues with less manual effort.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Sub-lists in the entity details view now display a badge in the tab header and drop-down menu showing the number of entries in each list. In the consumer view, tabs also feature chips indicating the number of entries, allowing users to see at a glance where configurations exist. This makes it easier to identify which tabs contain rules or other items and reduces the effort needed for troubleshooting and adjustments.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Stage logs are now shown in a dedicated log viewer that replaces the previous generic code editor and provides line numbers and readable formatting. Users can focus on specific log parts by showing only the last lines while still seeing correct line numbering from the backend. The new toolbar lets users toggle line wrapping, search within the log via a magnifier icon, and download the full log content. Warnings and errors are visually highlighted, and logs in the Stage Details view auto-refresh every 8 seconds for running executions so new messages appear without manual reload.

When working with Kafka, you now can set or override properties for the Kafka Consumer, Producer and Admin Client. This can be set either globally for all tasks or for individual task executions. For further information on how to configure the properties, see the Override Kafka Properties section of the user manual.

Previously, the Graph Store process always started with a fixed internal setting of -XX:MaxDirectMemorySize=128M. This value could not be changed by the user.

Starting with this release, the direct memory setting can be configured via the JAVA_TOOL_OPTIONS environment variable in the Graph Store service.

Further information how to configure the Graph Store service can be found in the Graph Store section of the user manual.

Search in the Executions list now returns filtered results instead of failing with a backend validation error. The UI now shows the validation text delivered by the backend in the toast message so you can see the real reason for invalid filter input. Searching values in date and timestamp fields is now supported consistently. Date column filters in lists support equals, not equals, greater, and less operations with expected behavior.

Users who are already logged in are now redirected directly to the dashboard when they navigate to the login page using the browser’s Back button or by typing '/auth/login' into the URL.

Fixed an issue where text entered in certain fields in the Consumer View could partially disappear while typing. Users can now enter information in Consumer View forms without losing characters while typing, even when fields trigger live validation or updates. Input in these fields remains stable during editing, and background updates no longer interrupt or overwrite what is currently being typed. This makes form completion more reliable and reduces the need to retype information.

Call entries in workflow templates can now be created and edited with Type = Task as expected. The TaskTemplate drop-down now reliably shows the task templates returned by revalidation instead of staying empty. Existing call entries can still be opened and edited without regressions in parent or task template selection.

The Neo4j service for Docker and Kubernetes deployments has been updated to version 5.26 LTS. This ensures that users can access Neo4j’s latest security updates. Further information on how to upgrade can be found in the Neo4j Upgrade Guide.

XDM now supports ElasticSearch version 8.19.19, which contains important security updates and bug fixes. Therefore, the docker compose configuration for ElasticSearch must be updated. Further information can be found in the corresponding migration guide. For Kubernetes installations, the ElasticSearch version gets updated automatically.

When working with Kafka, you now can set or override properties for the Kafka Consumer, Producer and Admin Client. This can be set either globally for all tasks or for individual task executions. For further information on how to configure the properties, see the Override Kafka Properties section of the user manual.

The Setup chapter has been completely restructured.

Specifically, the descriptions for installation, updates, and maintenance have been completely revised. Also, the descriptions of the parameters have been restructured and organized into three documents based on their significance.

Furthermore, Kubernetes and Docker are now treated as equals and Examples for Kubernetes have been added for each parameter. The examples for Kubernetes and Docker are now on separate tabs.

See Installation Introduction for an entry to the new Setup chapter.

You can now set an optional Isolation Level in task templates to control how SELECT statements read data during execution. The option is available for all Table Copy Task Templates, Row Level Processor Task Templates, to Icebox-Task Templates, PII Finder Task Templates, Row Level Delete Task Templates, and Data Indexing Task Templates. Selectable values are the four JDBC isolation levels (READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, SERIALIZABLE). If no value is set, XDM will use the database default behavior. The supported isolation levels depend on the database type and driver used.

The Entity Copy Task now supports reading from and writing to Kafka topics in Avro format, including the usage of Modification Methods and Filter Rules. A new file type Avro Schema has been introduced. Avro schemas are defined in JSON format, and Check Configuration validates whether the provided schema is valid. A new infrastructure object Kafka Schema Configuration has been added in which the Avro Schema, the Schema Source and the Data Format properties are defined. The Kafka Topic now has a required Schema Configuration property that must be set to a valid Kafka Schema Configuration object.

For situation where the provisioning and naming of certificates is done outside of the XDM containers, the HELM chart now provides two new entry point scripts to import certificates into the XDM containers. Also, the certificate import process has been improved to allow for more flexible file naming and to support multiple certificates in one file.

The script editor now uses the Tab key for indentation. Pressing the Tab key indents the current line, while pressing Shift+Tab resets the indentation. To move focus out of the code editor, users now press Esc first and then Tab to jump to the next field. The Keyboard Accessibility chapter of the user manual has been updated to document the new code editor shortcuts, providing a more familiar and efficient editing experience.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Execution lists now display the task type for each running task, making active work easier to identify at a glance. Scheduled execution lists now show the task type as well, so planned tasks can be distinguished before execution starts. Task type information is also visible in execution and scheduled execution detail views for consistent context across list and detail pages. Workflow executions are displayed with the type Workflow.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

In workflow templates, developers can now open a dedicated code snippet helper directly from the code editor toolbar while working in edit mode. The dialog lets users choose supported object types such as tasks, task templates, workflows, workflow templates, and hooks, and then select available objects from drop-down lists. Based on the selected object and entered parameters, the helper shows a live preview of the generated snippet before insertion.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

The default columns in the Connection list have been adjusted to improve readability and focus on relevant information. The Description column is no longer shown by default in the Connection list, and the Type column is now included instead. In the Task Template list, the Description column has also been removed from the default column set. Related lists were reviewed for default-column consistency so Description is only shown by default where it provides clear user value.

You can now reorder Modification Rules directly in the list to control execution order according to your business logic. Reordering is available both by drag and drop and by explicit move actions, so rule positions can be adjusted precisely. The selected order is saved persistently and is applied when tasks execute, ensuring consistent processing results. Ordering controls are only shown where list ordering is supported, and list interaction switches into a dedicated ordering mode while changes are prepared.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

The history list now shows who changed an object and when the change was made. You can see the operation type for each history entry, including created, updated, and deleted actions. Operation labels are shown in your language (German or English) to improve readability. This gives you better traceability of object changes directly in the history view.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

In order forms, options that are disabled by Data Shop scripts are now shown but can no longer be selected in Prime UI. This prevents users from accidentally changing values that were intentionally locked by business logic. The behavior is now aligned with the expected handling of disabled collection entries across the supported selection components.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Object lists now load significantly faster, so users can work with a 20-item result set with much less waiting time. The list view is optimized to display the expected 20 objects reliably after loading. This improves day-to-day usability by making navigation and interaction in object lists feel more responsive.

You can now reset your saved user settings to their default values directly in the User Settings view. The reset action clears both backend-stored settings and browser-local settings so your profile returns to a consistent default state. After the reset, default behavior is applied immediately or after a reload, depending on the affected setting.

Fixed a bug where unnecessary updates on the spring_session table caused performance issues. Now only necessary updates are processed, which improves performance and reduces the number of rows being updated.

Fixed a bug where, during workflow execution, a stage could trigger the same workflow to start again. The issue was caused by potential race conditions in core and dataflow. Concurrency handling in these components has been corrected and covered by dedicated tests to prevent duplicate starts. Workflow executions now run only the expected stages once.

Fixed an incorrect processing of start keys in Row Level Processing, Row Level to Icebox and Row Level Delete Tasks, if the number of keys differ between the start condition and the unique row identifier. This led to an error and the task execution was aborted.

Fixed a performance regression that occurred when a large number of Classification Term Entries were processed in a row level task.

Users can now access the existing “Connections” and “Task Templates” lists directly in the Prime UI. All list permissions from the previous UI are preserved, ensuring the same users retain access to their respective lists. Existing permission types (READ, ADMINISTRATION, CREATE) are carried over so that access rights and capabilities remain unchanged for end users.

In the Comparison result report, the Result column now shows only the user-relevant value. Technical prefixes and backend class names are no longer displayed in the table.

When creating a new Default Permission from the Permission Recipient list, the Grantor field now shows the current user as expected. The Grantor field remains read-only in the create dialog to prevent unintended changes. The displayed Grantor value is now consistent with the user stored after saving the Default Permission.

You can now set an optional Isolation Level in task templates to control how SELECT statements read data during execution. The option is available for all Table Copy Task Templates, Row Level Processor Task Templates, to Icebox-Task Templates, PII Finder Task Templates, Row Level Delete Task Templates, and Data Indexing Task Templates. Selectable values are the four JDBC isolation levels (READ_UNCOMMITTED, READ_COMMITTED, REPEATABLE_READ, SERIALIZABLE). If no value is set, XDM will use the database default behavior. The supported isolation levels depend on the database type and driver used.

You can now change the order of selected modification sets directly in entity detail views. You can also reorder selected task execution reports in the same way to match your intended processing sequence. The chosen order is saved and then applied during task execution so results follow the sequence you configured. The reordering interaction is designed for accessible use.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

You can now open a dedicated Browse tab on Mapping Table Container objects to inspect stored data directly in XDM. The Browse view lists available schemas and lets you expand their tables in a tree structure for easier navigation. You can open table contents and run read-only SQL queries in this context to inspect results quickly. Write operations such as INSERT, UPDATE, and DELETE are blocked with a permission error to keep data unchanged.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Data Shop cards in the Consumer view now display a dedicated icon, the responsible user, and assigned tags. Users can now filter the Data Shop list by selecting one or more tags to find relevant offerings faster. When a Data Shop is created, an initial responsible user is set automatically and can be updated later by an administrator. These metadata enhancements improve recognition and make ownership of each Data Shop transparent for consumers.

This new feature may only become available once the epic XEP-4 - Enhance Data Shop has been fully completed. Information on the current development of epics can be found at epic overview.

In reference drop down fields, you can now create required dependent objects directly where you need them. Selecting the create option opens the corresponding details dialog so you can enter the new object values without leaving your current context. After saving, the drop-down is refreshed automatically and the newly created object is immediately available for selection. The create option is shown only when you have permission to create objects of that type.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Navigation elements that open other XDM pages are now provided as links so browser link actions are available. Users can open these targets directly in a new browser tab from the context menu for faster parallel work. This behavior applies to object-related navigation in the main area and head-bar where users navigate to other XDM objects. View toggles that only switch content within the same page keep their existing behavior and are not exposed as open-in-new-tab links.

Entity list values are now rendered through the shared property display component for a more consistent visual presentation. This unifies how field values appear in table rows across supported property types. Users now get clearer and more predictable value rendering in list views, especially for mixed field formats.

Users can now open the User Manual directly from the Prime UI topbar via a dedicated help button that opens the documentation in a new browser tab. From the home page, the help button leads to the main manual, while on entity list and detail views it opens the corresponding object-specific reference. A help button is also available on the login page, giving quick access to the manual’s start page without logging in.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Object lists now support bulk operations so users can update multiple selected items in one step. Bulk updates now follow the same update flow across all object lists for a more predictable editing experience. This reduces repetitive manual edits and speeds up maintenance work on large sets of objects. Users can apply consistent changes faster while keeping control over the selected scope.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

When executing a Compatibility Table Copy Task or Row Level Processor with an MS SQL target table that has an identity column, the task could fail with an error message indicating that the user does not have permission to insert into the identity column.

Missing privileges for the identity column now only lead to a warning message, and the task continues to execute. This is especially useful for scenarios where the identity column is excluded from the source table. In such situations, no data is inserted into the identity column, so the missing privileges do not affect the task execution. However, it is preferred to also exclude the identity column from the target table with an exclude rule to avoid the warning message.

Furthermore, the tailoring report for exclude rules now shows the scope of the exclude rule for identity columns, so users can see whether it applies to the source or target table.

When a Row level processor, row level to icebox or row level delete task was executed from a workflow, and the start condition was set to null as a template parameter, that task was executed with a start condition of WHERE 1=1 instead of the expected null value. This lead to all data being copied or deleted.

The tasks now aborts during the pre execution check with a clear error message.

The connection-type custom parameter drop down in workflow templates now correctly lists all available connection objects. Users can select an existing connection from the drop-down and assign it to the workflow template. The list is populated whenever at least one matching connection exists in the system, ensuring it is no longer displayed as empty in these cases.

Spring Cloud Dataflow is not developed further. Thus, there might be potential security issues which are undesired for a productive environment. Therefore, we recommend to switch to the new Docker runner configuration. Details on how to set up and use the new runner mode can be found in the Configuration section of the user manual. Existing configurations will continue to use Spring Cloud Dataflow until they are switched to the new runner.

Previously, the health endpoint returned a JSON object with detailed information about the system and its components, including version, build date, and other metadata. The health endpoint now only returns the status of the backend service and no longer includes any additional information about the system.

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.

Fixed a bug where, during workflow execution, a stage could trigger the same workflow to start again. The issue was caused by potential race conditions in core and dataflow. Concurrency handling in these components has been corrected and covered by dedicated tests to prevent duplicate starts. Workflow executions now run only the expected stages once.

Fixed an incorrect processing of start keys in Row Level Processing, Row Level to Icebox and Row Level Delete Tasks, if the number of keys differ between the start condition and the unique row identifier. This led to an error and the task execution was aborted.

The configuration property xdm.core.security.seed is now mandatory. In Docker-based deployments, this property must be set in the docker-compose configuration for both core-server and dataflow-server. If the property is missing or blank, core startup is aborted with a clear security error message. If a configured seed does not meet the password-seed security policy (minimum length and character-class mix), core startup continues but logs a warning. The password-seed security policy can be found here.

Introduced a comprehensive set of base and example attribute generators for common data types and business fields that can be used directly in projects. Users can easily import these generators from the XDM Configuration Repository and immediately generate realistic data, including for the Employees sample database and typical Oracle database schemas.

Domain Model details now include a dedicated Relation Overview tab that visualizes all Domain Entities and their relationships in a graph. Each Domain Entity is shown as a node, and edges are derived from mapsTo relations configured on Domain Attributes. From the graph view, users can navigate directly to related Domain Entity details to analyze model structures faster.

Application Model versions now provide a dedicated relation overview that visualizes all configured Data Relation Rules in a graph. The Relation Viewer consolidates repeated table references and combines relevant relation columns per table to reduce visual noise in complex models. This makes it faster to understand dependencies between base and referenced tables directly in the modeling context.

The export dialog now shows a preview of the objects that will be exported before you confirm the action. The preview is automatically loaded when the dialog opens and updates whenever export options are changed. The preview is displayed as a tree, making object hierarchies and included items easier to understand. A loading indicator is shown while the preview is being prepared, so users can clearly see that data is being processed.

Environment details now include a dedicated view that visualizes relations between all Installed Applications in that environment. Applications are shown as nodes and their detected relations are shown as connecting edges for faster structural understanding. Relations that point to application models outside the current environment are displayed in a faded state to make cross-environment dependencies visible. This helps users analyze dependencies and assess modeling impact without switching to multiple detail pages.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

The screen now clearly indicates when the XDM backend is unavailable instead of showing a generic error. If the backend cannot be reached, a dedicated waiting screen displays a status message such as "Backend unavailable". Retry…" while the system continuously retries in the background. As soon as the backend becomes available again, users are automatically redirected either to the login screen (if not authenticated) or directly to the dashboard (if already logged in). The transition between unavailable and available states is smoother and more stable, avoiding flickering or confusing intermediate error messages.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Users can open a Check Permission dialog directly from an object to validate access for a selected user or role. The dialog supports choosing permission options with clear exclusive behavior for execution permission to avoid conflicting selections. After running the check, users get a detailed overview showing access results for the main object and its dependent objects. Users can filter the result list and open listed objects in a new tab, making missing permissions easier to investigate.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Users can now upload YAML or ZIP configuration files and preview all referenced and dependent objects in a hierarchical tree before starting the import. The preview shows each object’s name, type, import status (CREATED, REPLACED, SKIPPED), and reason, with search and keyboard navigation to quickly find relevant entries. Once the import is executed, successfully imported objects can be opened directly in a new browser tab from the result list without losing the import overview. The entire import and preview flow, including status display and search, is fully accessible via keyboard and screen readers.

This new feature may only become available once the epic XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed a bug where scheduled workflows and tasks failed after the user who created the schedule logged out. The scheduler reused a login-bound session token, which became invalid on logout and caused subsequent execution runs to fail. Execution handling has been corrected so scheduled workflows and tasks no longer depend on the initiating user’s active session token.

For a specific, legacy scenario on Db2 for z/Os, in which an index is both partitioned and extended (using a function on a key column), XDM was generating DDL that could not be executed correctly on the target system. This is solved by leaving out the partitioning if the index is extended, as both are not supported in combination for one single index by Db2 for z/OS.

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.

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.

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 XEP-2 - Modern Web Experience 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.

When executing a Compatibility Table Copy Task or Row Level Processor with an MS SQL target table that has an identity column, the task could fail with an error message indicating that the user does not have permission to insert into the identity column.

Missing privileges for the identity column now only lead to a warning message, and the task continues to execute. This is especially useful for scenarios where the identity column is excluded from the source table. In such situations, no data is inserted into the identity column, so the missing privileges do not affect the task execution. However, it is preferred to also exclude the identity column from the target table with an exclude rule to avoid the warning message.

Furthermore, the tailoring report for exclude rules now shows the scope of the exclude rule for identity columns, so users can see whether it applies to the source or target table.

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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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.

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.

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.

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.

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 XEP-2 - Modern Web Experience 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.

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.

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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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.

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.

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.

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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience 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 XEP-2 - Modern Web Experience has been fully completed. Information on the current development of epics can be found at epic overview.

Fixed a bug where an insoluble circular reference in foreign keys caused a StackOverflowError. In this case the task fails now with a message, that shows details to the involved tables instead of running into stack overflow exception.

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.

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.

A new guide has been added that describes a practical two step approach for cloning a complete or almost complete schema. The approach separates structural alignment from data transfer by combining a structure compare task with a native table copy task. It can be found here.

Modification Methods in NTC (Native Table Copy) and CTC (Compatibility Table Copy) tasks were updated to expose all source columns (including dropped ones) and any additional SELECT-only columns, improving flexibility for complex modifications and migrations. A new guide has been added to describe how to utilize this new functionality. It can be found here.

An alpha release of the Prime UI is now available alongside the current web UI. It can be enabled for Docker-based installations or Kubernetes deployments by following the instructions in Prime UI Installation. This allows customers to try the new Prime UI in parallel with the existing interface.

Administrators can configure these permissions in the existing web UI under 'System Settings' > 'Permission Recipients'. Select the appropriate role or individual user, if necessary, and configure the list permissions for 'Connections' and 'Task Templates'. At a minimum, the 'READ' permission must be granted so that users can view the lists. The 'CREATE' permission should also be granted if users are permitted to create new templates or connections.

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.

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.

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 Examples 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.

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.

Implemented two new system properties, xdm.core.accessTokenRolesClaim and xdm.core.idTokenRolesClaim, to control from which claim or ID token the user roles are extracted. See User roles for details.

An issue has been fixed where unquoted columns in CHECK constraints were causing case mismatches when executing generated DDL in a cross-copy from Db2 z/OS to Postgres. DDL generation has been updated to ensure case consistency by quoting columns in CHECK constraints.

A problem has been fixed where the displayed step duration during task execution was misleading when many log lines were written. This was characterized by the fact that the duration of a running step gradually increasing and then suddenly becoming shorter once the execution step was complete. The duration of each task step is now displayed correctly, and the total duration of all steps matches the actual execution time again.

Sensitive information, such as environment variables and database details, is no longer displayed in execution logs.

Enhanced logging for entity copy tasks that copy from or to Kafka topics was implemented, providing users with regular updates on the copy process. The total number of processed messages is displayed every minute.

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.

A problem has been fixed where not all log messages were displayed in the execution log. This occurred with log messages that were output in quick succession. Now all log messages are displayed.

Fixed an issue where data could not be copied with Fill mode INSERT due to the presence of a Generated Always column, causing the task to fail with the error No value specified for parameter 1.

See here. for details how the Generated Always columns are handled during data copying.

Fixed an issue where columns in the schema browser and column picker appeared in an unsorted order.

Fixed an issue where the DDL generation generated wrong DDL for Oracle columns with defaults in some situations. In particularly 'DEFAULT USER' was incorrectly replaced with 'SESSION_USER'.

Fixed an issue where bulk delete option showed no feedback and the delete dialog remained open when delete permissions were missing for one or more selected items. The fix ensured that the permission message is displayed and the delete button is disabled in the delete dialog.

Implemented a filtering feature in the Entity Copy Task for Kafka topics sources to allow users to control the volume of data copied. Users can now specify partition, offset, and timestamp criteria. If only a topic is provided, all messages from all partitions are copied. When a partition is specified, only messages from that partition are copied. Setting an offset or timestamp will only copy messages greater or equal to the given values. The filters are combined using a logical AND to refine the data selection.

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.

Fixed an issue where NULL values in Kafka payloads were not being copied to the target topic. The bug caused the process to fail with a 'NOT_FOUND: Database not found' error when attempting to write empty values. The update ensures that payloads containing NULL values are now accurately copied, preserving the NULL entries in the target topic without triggering errors.

Exporting an environment to a zip file or checking its configuration failed when a Data Relation Rule was used in the Application Model, because the script language was not read correctly.

Fixed an issue where a login error message in German („Login fehlgeschlagen“) was displayed instead of an English error message („Login failed“) on an English installation. Fixing ensured that the English error message will be displayed in the English environment.

Implemented support for Partitioned Tables in DDL generation for PostgreSQL. The DDL generation now accurately reflects the necessary syntax for PostgreSQL, allowing for seamless transfer of Partitioned Tables from Db2 z/OS.

Fixed an issue where ALTER statements were not processed correctly by the File Bridge server, resulting in an error message stating that the value ALTER is not listed as a constant. The code was updated to ensure that the ALTER statement is now successfully executed and applied to the table without any errors. You need to update the File Bridge server and driver to the current version to use this fix.

Fixed a bug where the original data type of form parameter was changed from Collection to String when using scripts in the Data Shop, particularly with Collections. The fix ensured that the original data type remains unchanged, allowing methods like collection.add() to function correctly. Additionally, if no default value is set, an empty list is now passed, preventing errors when adding entries to the Collection.

Implemented the ability to copy message headers, keys, and optional timestamps from incoming Kafka messages to outgoing messages. This change was made to ensure that metadata from the original messages is preserved for further processing. The functionality includes options to enable or disable header copying and timestamp retention, enhancing flexibility in message handling.

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.

Implemented a feature that allowed users to select the authentication method within the Kafka Topic object. Users can now choose between 'None' and 'OAuth Bearer Token'. When 'OAuth Bearer Token' is selected, a mandatory 'TokenEndpoint' field appears. Beside that an option was added to support SSL encryption for Kafka connections.

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.

Analyzed the transaction behavior in the RLP task using FillMode Merge to identify the causes of the Broken PIPE error. This change aimed to ensure stable operation of XDM with the HIT driver and MERGE, addressing transaction handling and commit processes that were causing lock issues during large data transfers. With this change the evaluation of the used merge apply units was improved and additional log messages were added to analyze the selection of the merge apply units.

Fixed an issue where the Application Model names were not displayed in the Source Objects Report. The column for Application Models remained empty for table based tasks, because this information is not available in the runtime environment. Therefore, the column is no longer displayed in reports of table based task executions.

Fixed a bug where NUMERIC columns without length and scale in PostgreSQL caused the CompareEvaluator to throw a NumberFormatException.

Fixed a bug where leading or trailing spaces in usernames during login resulted in the creation of multiple permission recipients for the same user. Existing permissions recipients with leading or training spaces are not merged automatically. This needs to happen via the transfer ownership functionality and a manual delete of the duplicate permission recipients.

Sensitive information, such as environment variables and database details, is no longer displayed in execution logs.

There is a new task template type 'Entity Copy Task Template', which can copy data between the entity based data sources and targets. It is available when either Kafka or Webservice database type or Data generation component is licensed. Depending on your license, direct- and cross-copies are possible with the following data sources and targets:

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.