Released: January 2023
Instructions were added to the documentation that describe how to prevent library conflicts when deploying on WebLogic. See the Preventing library conflicts on WebLogic heading in the index.html file that is located in the following folder in the 4.5.16 Add-on Bundle: documentation > adix_<xxx>.
This release contains no changes in functionality.
This release contains no changes to third-party libraries.
[ADIX-3703] Excel import and export services do not work correctly due to a library conflict.
This release contains the following known issues:
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.
Checking privileges for a view in PostgreSQL is not supported.
Foreign key statements in the DDL file are not managed.