Changelog

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

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

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.

Fixed a bug where parsing timestamps in RLP tasks with multiple threads resulted in NumberFormatExceptions due to the non-thread-safe nature of SimpleDateFormat. The implementation was updated to use a thread-safe alternative, ensuring that timestamp parsing now executes without errors across multiple threads, maintaining stable performance regardless of thread count.

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

Disabled reporting in Tempo to prevent the transmission of anonymous usage data to Grafana. This change was made to eliminate excessive warnings in the logs when there is no internet access, indicating failed attempts to connect to Grafana.org. The configuration option reporting_enabled was set to false, ensuring that reporting is consistently disabled.

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.

A guide has been added that describes how to use a stage hook and iterative execution of this hook to check the relationships within an application model and identify missing relationships in order to optimize data selection in the application model.

The guide can be found here.

A valid license key is now required to control the 'Data Generation' option. Consequently, the feature toggle in the Core Server configuration is no longer relevant. The 'Store' option, which enabled users to access the Graph Store, has also been transferred to the license key and removed as a feature toggle.

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

Fixed a bug where the init script removed default values of custom parameters during the order process. The issue occurred when any code or comments were present in the init script, resulting in empty fields instead of displaying default values. The fix ensures that default values remain intact unless explicitly referenced in the init script.

Workflows with overwritten custom parameter caused a problem when they were accessed in a script. The process of overwriting a custom parameter has also changed an internal property of the workflow. With this fix, overwriting custom parameter works as expected. Furthermore, the wrongly changed internal property was corrected for workflows with overwritten parameter.

There was a bug that sets the script language of a modification rule to Groovy when this rule uses a legacy modification method. Now, a modification rule, which uses a legacy modification method, can only be written in JavaScript. Therefore, on all existing such rules, the script language was set to JavaScript. Also, when importing modification sets from older YAML exports, this behavior is enforced.

When exporting a task execution that contains huge data directories (e.g. exporting a compatibility task execution between Stage 5 and Stage 6), the core server could crash and no execution export was possible. Now, the data directory is never restored into a temporary directory inside the core container.

Fixed an issue where exporting more than 100 objects resulted in a 414 error (Request-URI Too Large). A clear error message is now provided for failed exports, and the bulk actions now only include the relative context path in the 'url' parameter to reduce header length.

Added a new object type "Kafka Topic" in XDM to allow users to flexibly add and utilize Kafka topics as sources or targets for copy processes.

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 new system property, xdm.core.execution-report-table-whitelist, to control access to specific tables in the XDM database for TaskExecutionReport SQL statements. This change was made to protect sensitive data from unauthorized access in Task Execution Reports. The property ensures that if not set, only a minimal set of tables is accessible. See configuration of accessible tables for task execution reports for details.

Implemented a new microservice to write Kafka topics. The service uses the data within the Entity Records that was previously collected by the Kafka Source microservice.

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.

Introduced a configuration option (allowMarkdownDescription) that, when set to false, blocks the insertion and rendering of markup/HTML in Announcements, Data Shop Descriptions, and Information Pages. The default remains true, so existing behavior does not change unless explicitly configured. This option is intended for security-hardened environments to reduce attack surface (e.g., XSS, layout manipulation, script injection); when disabled, rendering is bypassed and the HTML parsing library is not used.

Fixed an issue where Grafana statistics displayed incorrect numbers and excessive entries. The Top Executed Objects dashboard now shows accurate execution counts, and the Top 10 Executions dashboard is limited to a maximum of 10 entries. Adjustments were made to ensure statistics align with executed tasks and workflows, and descriptions in the Home dashboard were updated to clarify that all diagrams include deleted executions.

Fixed a bug where users without appropriate permissions could use the REST-API endpoint. All endpoints now correctly check for the required permissions and return a 403 Forbidden status when permissions are lacking.

Fixed a bug where RLP tasks with Performance Supervision would fail at the end of Stage 6 due to an ArrayOutOfBound exception while collecting statistics. The issue occurred after data writing was completed. The code was updated to encapsulate the Performance Supervision process, ensuring that any errors during statistics collection now produce a warning instead of causing a task failure.

Fixed a bug where renaming a connection that is used in a To Icebox Task caused the corresponding From Icebox Task to fail during the Extract Reports step due to the connection not being found. The step will now display a warning message that the connection is missing, and the task will continue executing.

Fixed an issue where a text field was displayed instead of a drop-down list when adding a new form parameter. The drop-down list for possible values is now correctly shown during the creation process, allowing users to select from predefined values. This change ensures that the functionality remains consistent after saving the data shop.

Fixed an issue where parameters with identical names could be added to a modification method without triggering an error. Now, when attempting to add parameters with duplicate names, an error message is displayed immediately, preventing the saving of the modification method. This change ensures that users cannot save modifications with duplicate parameter names, enhancing data integrity.

Fixed a bug where the log view would jump to the beginning upon reloading when the Follow-Log mode was disabled. The log now retains its current position during data refreshes in Non-Follow-Log mode, ensuring a stable user experience. The Follow-Log mode automatically activates when the user scrolls to the end of the log, allowing for seamless data loading.

Implemented a new AI assistance feature in the code editor to provide automated code suggestions. The current code and prompt are sent to a microservice that interacts with a language model, returning suggestions.

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

Fixed a NullPointer Exception that occurred during column name mapping in GENERIC mode. The issue arose when attempting to map columns between source and target. The code has been updated to ensure the correct processing and mapping of column names, enabling correct column mapping and error-free copying of data.

Fixed a bug where the filter fields did not match the scheduled task list. All relevant fields, except the option for 'Output' are now available in the filter. The filter options now correctly correspond to the columns in the scheduled task list. Additionally, users can now filter the list by 'Executable'.

Fixed an issue where the default value for date parameters in data shops was not being saved, resulting in the field remaining empty after saving. The change ensured that the default value can now be successfully set, remains visible in both the template and order views, and is correctly displayed in the order form after saving. Setting a data type value is now only possible using the calendar.

A guide has been added to the manual that shows how to best create an anonymization project with XDM. The guide shows which steps need to be taken, what needs to be considered, and which mistakes should be avoided.

The guide can be found here.

A new service has been implemented to read Kafka topics. The service provides functions for specifying the data to be selected.

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

The categories in the Purchaser view were reorganized to display hierarchically. This change was made to enhance the visibility of the data shop structure, allowing buyers to easily identify which data shops belong to which categories. Subcategories were clearly positioned beneath their parent categories, improving navigation and selection for users.

Fixed an issue where data could not be loaded into columns defined as GENERATED ALWAYS on Db2 LUW, resulting in an error. This happens because the overwrite of a value by a generated value was treated as data truncation, giving an error with toleration mode Prevent Truncation. This behavior was changed and a better error message was implemented.

Fixed an issue where, under certain circumstances, the execution files were not completely deleted after a task execution, preventing the resume process. The deletion process is now made more robust, by adding a retry mechanism that attempts to delete the files every 30 seconds for three minutes. If the deletion was still not successful the exception is thrown, which then leads to an erroneous task execution.

Fixed a bug where parsing timestamps in RLP tasks with multiple threads resulted in NumberFormatExceptions due to the non-thread-safe nature of SimpleDateFormat. The implementation was updated to use a thread-safe alternative, ensuring that timestamp parsing now executes without errors across multiple threads, maintaining stable performance regardless of thread count.

Fixed a bug where the task continued running despite an exception being thrown in the init() method. The task now correctly aborts when a ModificationException or RuntimeException occurs. The exception is logged as a SEVERE message, and no warning is displayed on the interface when the task is aborted, ensuring proper error handling and user experience.

Fixed an issue where importing an old 'Structure Compare Task' or 'Structure Compare with IceBox' failed due to missing Comparable Fields that had been renamed. The import process was updated to successfully ignore non-existent Comparable Fields, preventing error messages related to these fields from appearing. This change ensures that imports can proceed smoothly even when outdated field references are present.

The problem was that NULL values in nullable indexes were always treated as the same value. This resulted in rows being discarded from the process. NULL values will now be treated as different in the processing, so reflecting the rules given by the underlying index.

Fixed an issue where the SELECT statement did not update when switching to a different table, causing a mismatch between displayed data and the SQL statement. The update now ensures that both the data and SQL statement refresh upon table change. Additionally, a warning prompt appears for changed statements, requiring user confirmation to proceed with loading new data, while retaining the old data and statement if canceled.

Fixed a NullPointer Exception that occurred during column name mapping in GENERIC mode. The issue arose when attempting to map columns between source and target. The code has been updated to ensure the correct processing and mapping of column names, enabling correct column mapping and error-free copying of data.

A guide has been added that describes how Selection Rules and Exclude Rules can be set dynamically in Table Copy Tasks.

Updated the H2 database version to 2.3.232 to incorporate the latest bug fixes and security patches. This change ensures that Batch, Dataflow, and Core components function seamlessly with the new version. All delivered Lookup Tables are now converted and provided in the new H2 version. Due to the structural changes in H2 files in newer versions, a new workflow for migrating existing Mapping Table Containers and H2 files named Convert Mapping Table Container has been provided. This workflow iterates over the Mapping Table Container list and calls the migration hook for each container. The hook will download the database from the Mapping Table Container, migrate the database and upload it again. To execute this workflow correctly, read and write permissions for the Mapping Table Containers are required by the executing user.

Implemented keyboard navigation for sorting elements to enhance accessibility. Each movable element now features a visible drag area that displays directional arrows on hover or focus, facilitating user interaction. Additionally, the user manual has been updated to clearly explain the operation of the drag area. This change was made to ensure that users can efficiently and accessibly adjust the order of elements.

Implemented CodeMirror for text fields in the DataShop’s Place Order mask to enhance user experience when entering long lists. This change allows string-type parameters to be displayed in a multi-line format, accommodating approximately 20 lines of code with scroll functionality. The layout editor now enables this display option for all string parameters, facilitating easier data entry and editing for users.

Enhanced the execution dialog by adding a drop down menu for task stage selection to prevent users from accidentally creating non-executable configurations. The drop down menu now dynamically lists stages indicating up to which step the task execution can proceed. This improvement is also reflected in the resume dialog for ongoing executions, ensuring users do not skip critical stages that could lead to execution errors.

Fixed a bug where Icebox generations with a set expire date were not being deleted at the designated time. The deletion process was updated to ensure that these generations are removed as expected.

Fixed a bug that caused the report generation to fail at the end of a workflow due to an "Unable to deserialize the execution context" error. The issue arose during the execution of the main job step, where the script evaluation encountered an IllegalArgumentException. The serialization process was corrected, not allowing values to be stored that would fail during serialization.

Fixed an issue where script libraries in legacy modification methods were sometimes not loading completely in tasks with multiple threads. The loading mechanism was fixed while maintaining performance of the legacy modification methods.

Fixed an issue where a content was not fully displayed in the object history compare bottom sheet, affecting user experience. The Bottom Sheet now correctly shows all compared properties responsively, adapting to screen sizes without overlaps or cut-off elements. Additionally, the vertical bottom sheet scrollbar is now displayed on small screens.

Fixed an issue in the Browse Schema & Tables dialog where elements were not fully visible on small screens. Adjustments were made to ensure all dialog elements are displayed correctly at screen widths below 875px, including the filter text, checkboxes, and paginator layout.

Fixed a bug where the content of an execution was not loading when opened in a new background tab. The fix ensures that an execution loads completely when opened in the foreground and loads once when opened in the background. Additionally, content is now refreshed regularly when returning to the foreground, while background tabs remain unchanged.

Fixed a bug where parsing timestamps in RLP tasks with multiple threads resulted in NumberFormatExceptions due to the non-thread-safe nature of SimpleDateFormat. The implementation was updated to use a thread-safe alternative, ensuring that timestamp parsing now executes without errors across multiple threads, maintaining stable performance regardless of thread count.

Fixed an issue where script libraries in legacy modification methods were sometimes not loading completely in tasks with multiple threads. The loading mechanism was fixed while maintaining performance of the legacy modification methods.

Fixed an issue where script libraries in legacy modification methods were sometimes not loading completely in tasks with multiple threads. The loading mechanism was fixed while maintaining performance of the legacy modification methods.

Implemented an option for automatic deletion of old Loki logs to optimize disk space usage. The system now automatically removes logs that exceed a specified age. The age for logs to be deleted automatically can be set by the user. The parameter to set the age can also be used to deactivate the option. The option is disabled by default.

Further information’s can be found in loki configuration chapter.

Added logging functionality to the configuration as code job to include start, end and abort messages with timestamps. This change was implemented to enhance job status tracking for users, allowing them to efficiently monitor the progress of import jobs. The output now clearly indicates when an import starts, finishes or is aborted, along with the reason for any aborts, improving overall transparency and user experience.

Updated the Angular version to 19 and all other dependencies to their latest versions to ensure the project maintains clean and supported dependencies for future development. The application functionality remained unchanged, while unnecessary dependencies were identified and removed to streamline the project.

Implemented a fixed-size Code Mirror in the editor to ensure that the edit field remains visible while scrolling through long code. This change allows users to enter edit mode and save changes without needing to scroll back to the top of the page. Additionally, the find-bar is now displayed without requiring page scrolling, enhancing the overall user experience when making code edits.

A visual indicator was added to signal the presence of additional columns, and the action bar was elevated with a shadow effect. This change aimed to improve the visibility of table headers and scrollbars, allowing users to easily navigate long lists without losing context, especially when dealing with lengthy object names.

Fixed a NullPointerException that occurred during the deserialization of the ObjectContainer when mapping rules were applied to columns with constraints. The changes ensured that mapping rules now function correctly in the object selection process for columns with constraints.

Fixed an issue where a failed Generation Task in a task workflow was incorrectly marking the entire execution as successful. This happened because Generation Tasks do not raise an exception when they fail, but only set their status to failed. This status was not correctly propagated to the workflow execution status. The workflow now correctly identifies the execution as failed when any task fails.

Fixed a bug where the restore default settings option for custom list settings did not function as intended. Previously, clicking the option did not remove additional custom columns, resulting in an incorrect display. The functionality was updated to ensure that only the default columns are shown after restoration, and it was tested across various lists to confirm consistent behavior.

Fixed a bug where 1-2 characters were lost during input in the Data Shop, particularly after multiple attempts. The issue was caused by improper handling of input buffers. The input processing logic was updated to ensure that all characters are correctly captured and retained, eliminating the character loss issue after 5-10 attempts.

Fixed an issue where reports in Workflow Templates could not be arranged in the desired order. Users were previously limited to adding reports sequentially, with automatic sorting by the system. The update now allows users to set and adjust the order of reports during both the creation and editing of Workflow Templates, ensuring reports display in the specified order after execution.

Fixed an issue where the error message was not displayed for ScriptValidationException when thrown for Collection parameters. The input field now correctly turns red, and the associated error message is visible, aligning the behavior with that of String parameters. This ensures users receive appropriate feedback when validation fails.

Fixed a bug in the Purchaser-Layout where four unwanted control buttons appeared during the reorder process. The buttons 'Save', 'Discard', 'Place Order', and 'Configure Data-Shop Layout' were made invisible to ensure a cleaner interface. This change aligns the actual behavior with the expected behavior, enhancing user experience by removing unnecessary elements.

Fixed an issue where the Play button in the Schema Browser did not refresh results on subsequent clicks. The button now correctly executes the statement with each click, ensuring that the latest results are displayed regardless of changes to the statement text or row count. The user interface updates appropriately after each execution.

Fixed an issue where the name of the first list item was only visible on hover. The display logic was updated to ensure that the name is always shown, regardless of mouse position. All values in the List Permissions are now consistently visible across all supported browsers.

Fixed a bug that allowed users to edit the variable name after changing the display name. The Variable Name input field is now disabled once the display name is edited, preventing any modifications. This change ensures that no errors occur when attempting to save the parameter after the display name has been altered, aligning the behavior with the expected functionality.

Updated the user management functionality to allow administrators to edit the names and email addresses of inactive users. This change was implemented to ensure compliance with GDPR regulations regarding the anonymization of data for former employees.

Implemented a license check for the "Cloud Option" in the XDM core when running in a Kubernetes environment. This change ensures that only authorized users can access the cloud functionality. The system now verifies if the license includes the "Cloud Option" or the Premium Package is used. A new entry was added to the HELM installation chapter of the manual, mentioning that the cloud functionality is required.

Implemented support for Groovy scripts in the File Operator to enable advanced data manipulations. Users can now generate INSERT statements for direct database execution and configure JDBC connections via custom parameters. Additionally, users can access JDBC connections within Groovy scripts and include external libraries. This change aimed to enhance efficiency by allowing users to automate data generation and insertion processes.

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

Performance has been improved in the following areas:

Further performance improvements are planned for the future.

Implemented scheduling functionality for Tasks, Workflows, TaskTemplates, and WorkflowTemplates. Users can now set a flag in the Statement Helper to schedule execution. A checkbox labeled 'Schedule Execution' appears upon selection, allowing users to input a time period in 'P2DT3H' format. The input is stored in the scheduleExpression field, which resets to null when unchecked. This change enhances workflow efficiency by enabling future task execution.

Fixed a bug that caused a syntax error when disabling foreign keys due to missing delimiters in the database name for a SQL Server database connection. The ALTER DATABASE statement was updated to include quotes around the database name, ensuring it is executed correctly.

Fixed a bug that prevented users without a membership from being deactivated, which resulted in an error message stating 'Property 'authorities': Value must not be empty'. The deactivation process was updated to allow users without membership to be successfully deactivated without triggering any error messages.

Fixed a bug that caused a 500 error message to appear during login in XDM when the maximum user limit was exceeded. Implemented a clear error message indicating that the maximum number of users has been reached, along with a specific error cause. The HTTP status code is no longer 500, when the maximum number of users has been reached.

Fixed a bug where lines were missing during the Close & Reopen strategy for NFS shares. The issue occurred when processing over 100,000 lines, resulting in one line being omitted for every 100,000 processed. The extraction logic was updated to ensure that all lines are correctly extracted and written to the file, addressing both NFS shares and local files.

The execution times were up to 10 times longer than expected. Optimized the Mapping Utils implementation to ensure that the runtime of the Modification methods is now comparable to that of the previous Mapping tables, meeting the acceptance criteria.

Fixed an issue in the Comparable Fields tab of the Structure Compare Template where database types and categories were not sorted in a recognizable order. The database types and categories are now displayed in alphabetical order, improving clarity and ease of selection. This sorting remains consistent across different database objects.

Fixed an issue where users did not receive a warning about unsaved changes when exiting edit mode. A dialog now appears if there are unsaved changes after modifications made after saving with Ctrl + S. This ensures that users are alerted before navigating away, preventing potential loss of changes.

Fixed an issue where the Active button remained disabled after editing an embedded list item in line. The button is now correctly activated in edit mode and remains enabled after exiting edit mode. This change ensures that users can always interact with this toggle, improving the overall user experience.

Fixed an issue where input fields in Create Version dialog were displayed too small on small screens, making data entry difficult. Now the input fields support a normal size and remain user-friendly and accessible. Verified that there are no overlaps or reductions in input fields size, ensuring a consistent experience across different screen sizes.

Fixed an issue where the last column of the table was not fully visible in sort mode, causing content to be cut off. Adjusted the table’s layout to ensure all columns are displayed correctly, maintaining the overall functionality. This change ensures that users can view the entire table without any content being obscured.

Improved the performance of the SubsetApply phase for PostgreSQL by at least 50% to enhance data loading efficiency. Implemented the COPY utility for INSERT operations, falling back to Multi-Values-INSERT when necessary due to data type constraints or existing data. For blocks where Multi-Value-INSERT could not insert all rows, individual INSERTs were processed in BatchMode, resulting in reduced wait times for internal customers.

For more details compare the description of the SubsetApply.

Implemented a toggle button that allows users to switch the side menu to an 'Icon Only' view, providing more space for content display. This change was made to enhance user experience by allowing users to customize their interface according to their needs. The selected menu view is now saved in user settings, ensuring it persists after page reloads, and users can revert to the default view at any time.

Fixed a bug where strings were incorrectly truncated to 255 characters during data extraction. This issue occurred when a column property rule which enables the transportCharacterDataAsBinary option on a Db2 z/OS VARCHAR column exceeded 255 characters.

Fixed a bug that caused the connection to Loki to terminate after 60 minutes due to a timeout, resulting in the loss of logs and error messages. The connection stability was improved, ensuring that logs are continuously written without interruption, even after the timeout period.

Fixed a bug where an unnecessary confirmation dialog appeared after confirming the migration. The dialog 'Changing content' was removed, allowing the migration code to be applied directly without interruption.

Fixed an issue where no feedback was provided after executing SQL statements. A popup notification now appears within 5 seconds to indicate success or failure. In cases of errors, a detailed error dialog is displayed, ensuring users are informed about the execution status.

Fixed an issue where error messages for the Number field were only displayed for letter inputs. The error handling was updated to ensure that error messages are shown for all invalid inputs, including numbers. Additionally, the system was modified to prevent a Core Error 500 from occurring when invalid number entries are made, allowing the Data Shop to start successfully even with set error messages.

Fixed a bug where the icons for the 'Place Order' and 'Place Order and view' buttons displayed a phone symbol instead of the intended hand symbol. This change ensured that the icons accurately represented the functionality of the Data Shop Order, eliminating user confusion and improving the overall interface consistency.

Fixed a bug where the Object Permissions list did not display the associated objects for granted permissions. The update ensured that all objects with assigned permissions are now visible in the list, allowing users to correctly view and adjust permissions as intended.

Fixed an issue where tabs in embedded blocks did not display content after collapsing and expanding of the blocks. Now tabs correctly display a filter bar and an embedded list upon expansion.

Fixed an issue where the Schema Browser did not display the reference table for Foreign Keys. The 'Reference Table' column was added and correctly populated for all Foreign Keys. This change ensures that the reference table is consistently shown across different database connections, improving the visibility and usability of the Schema Browser.

The execution times were up to 10 times longer than expected. Optimized the Mapping Utils implementation to ensure that the runtime of the Modification methods is now comparable to that of the previous Mapping tables, meeting the acceptance criteria.

Fixed a bug where lines were missing during the Close & Reopen strategy for NFS shares. The issue occurred when processing over 100,000 lines, resulting in one line being omitted for every 100,000 processed. The extraction logic was updated to ensure that all lines are correctly extracted and written to the file, addressing both NFS shares and local files.

Fixed a bug that triggered a NullPointerException during a hook execution. The exception occurred when the Data Preview was enabled and the installed applications differed. Now, the task does not crash anymore.

Fixed an issue where the library list did not automatically update when the script language was changed in data shop. The library list now refreshes immediately to reflect the selected script language without requiring manual saving or reloading. This change ensures that users consistently see the correct libraries corresponding to their chosen script language.

Improved the performance of the SubsetApply phase for PostgreSQL by at least 50% to enhance data loading efficiency. Implemented the COPY utility for INSERT operations, falling back to Multi-Values-INSERT when necessary due to data type constraints or existing data. For blocks where Multi-Value-INSERT could not insert all rows, individual INSERTs were processed in BatchMode, resulting in reduced wait times for internal customers.

For more details compare the description of the SubsetApply.

In new releases of XDM, the PostgreSQL driver is not separately included in the drivers directory anymore. XDM provides an up-to-date PostgreSQL driver by default. It is recommended to remove the old PostgreSQL driver jar from the JDBC drivers directory. Further information’s can be found here.

Replaced existing Grafana panels with redesigned versions to enhance visual appeal and structure. Updated the Welcome panel to include meaningful content instead of placeholder text. Ensured all panels are technically functional and maintain a consistent design. The evaluation of the panels is based on the history-data. Ensured all panels deliver correct information on change or deletion.

Exclude rules can now be applied to columns of tables. To removes a column from all processing, set the object type to COLUMN and define the column name pattern in the new corresponding field of the rule. No data is selected from that column and no DDL is generated for it.

This option can be used if a source column should not be transferred to the target, but also as a workaround if a column cannot be copied for some reason, and is not necessarily required in the target.

However, this can lead to errors if the column is used by other objects, for example an index.

It is now possible to view the internal log of a task execution by selecting the corresponding action in the context menu. The log is displayed in a separate dialog, showing up to 1,000 lines. However, users can download the complete internal log if needed.