1. Refreshed UI/UX
Affected areas: Etlworks UI.
Once again we updated the Etlworks UI/UX to further improve user experience.
1.1 The tags and filters are now sticky and take less space on the screen
1.2 The tag view and expandable tags are now enabled by default.
2. Added the ability to send emails in HTML format
Previously it was only possible to send emails in plain text or as an attachment.
In this update, we introduced the ability to send emails in HTML format.
3. Added the ability to configure an Excel worksheet name or index at the transformation level
In Etlworks the name or index of the Excel worksheet is configured in the Excel format.
In this update, we introduced the ability to use the same connection and format to read from or write into different Excel worksheets.
When creating the source-to-destination transformation use the
filename|worksheet notation in the FROM or TO. Example:
matrix.xlsx|income tells the system to read data from the worksheet
income in the file
4. Added the ability to connect to MongoDB over the SSH tunnel
In this update, we introduced the ability to connect to the MongoDB over the SSH tunnel.
5. Added the ability to enforce case sensitive table matching for MySQL CDC connector
Prior to this update, the MySQL CDC connector was whitelisting the tables to extract data from based solely on their names. For example, if there is a database
test and the tables
Abc the stream would include records from
In this update, we introduced the ability to enforce the case sensitive matching of the
db.table defined for the source.
1. Changes to how system handles user-defined response in the PUSH APIs
Affected areas: user-defined PUSH API.
Prior to this update, the system was retaining the files created as a user-defined response for the PUSH API.
Starting with this update the system automatically deletes the response files after API returns the call back to the caller.
Changes under the hood
We are now one step closer to introducing the versioning in Etlworks.
Starting with this update the system automatically captures all the changes in the flows, formats, and listeners and stores them as versions in the database.
In the next update, we will introduce the UI which will allow end-users to revert the specific flow, format or listener to any of the previous versions.
The versioning UI will also allow users to visually compare versions, just like in any modern version control, such as Git.
Please stay tuned!