Version 2.7.24

Last published : Aug 10, 2026

Related information

Release Notes

New features

The Servlet version was updated to 3.1.

This release contains no changes in functionality.

This release contains no changes to third-party libraries.

This release contains no closed issues.

This release contains the following known issues:

Import of larger Excel files (more than 100,000 records) can fail.

Workaround: Refresh the browser window where the import was initiated and the process will resume. Additionally, you can increase the allotted JVM memory up to 35GB.
Due to a limitation in Excel, long fields with the number data type display all numbers past the 16th place as a 0.
When importing using XLSM and the Download file of invalid data option is enabled, the file containing invalid data will be in XLSX format.
Association object and selection node are not supported.
Data lineage.
Graphical view of the data mapping configurations.
Split of string transformation function is not supported for a multi-valued string field.
Data transfer between complex terminal nodes is possible only if they use the same Java Bean.
You can not export data from multiple complex nodes in EBX® that when there is at least one complex node with multiple occurrences.
You can not import data from multiple complex nodes in an XML file when there is at least one complex node with multiple occurrences.
Split of data works for terminal nodes only.

You can only export data from EBX® to the selected columns in the same tables of a view which is joined by multiple tables.
The add-on doesn't support exporting SQL with the Replace all content mode to a view which is joined by multiple tables.
Checking mandatory fields of a view in SQL database is not supported.
The export still executes normally and shows an error message from database when no privilege granted.
Exporting data from multi-valued fields and multi-valued groups is not supported.
You can not export data from EBX® to a view in PostgreSQL database.
Exporting data from EBX® to an auto-increment column in SQL Server is not supported because the IDENTITY\_INSERT property is always set to OFF.