This release contains the following new features:
When creating a custom transformation using the add-on's API, the following information can now be included on inputs and outputs: name, description, and data type. This input can be used to help business users understand the transformation's purpose and its usage.
It is now possible to choose whether dataspace snapshots are included when exporting related data using the new Export data from snapshots option.
When exporting related data, it is now possible to select the individual related tables to export.
The manner in which the add-on handles permissions was updated. The changes mainly impact behavior related to records that are hidden due to permission settings. The add-on no longer blocks data integration processes when encountering an exception related to permissions. Instead, only invalid records are rejected and valid records are still processed. Additionally, the general behavior was made more consistent between datasets and tables.
Version 3.3.1 of the Apache Kafka client library was removed.
This release contains the following closed issues:
[DINT-4251] Related data from a child dataspace is exported when it should not be.
[DINT-4657] An error displays when importing a CSV file using a template where the default value of Concatenate String transformation is an empty string.
[DINT-4716] The dataspace is locked when transferring data to multiple target tables.
This release contains the following known issues:
[DINT-4339] A JNDI data source cannot be configured when EBX® is deployed on a WebLogic, or JBoss server.
Fonts are no longer shipped with the JDK 11. Font rendering in Java 11 JVMs now uses pre-installed operating system fonts. This can cause issues in Linux environments when exporting Excel files. As a workaround, you can install the fontconfig package.
When exporting to SQL with TDV, if any error occurs, the operation is cancelled.
Due to a limitation in Excel, long fields with the number data type display all numbers past the 16th place as a 0.
Importing and exporting SQL: Read and write is not possible with the Timestamp data type with MS SQL Server.
Configuring a schema using the JNDI configuration in your web server is not supported.
When creating a custom transformation function, you must use a predefined data type for its input and output fields.