Customer Portal

CloverETL 4.6 simplifies job development by introducing "auto debugging," an implicit collection of data samples on all edges. You no longer need to manually control debugging on and off on individual edges.

Additionally, new UI controls in Event Listeners in the Server Console make monitoring of events easier. We've also developed a new interactive tutorial to help beginners grasp the basics quickly and without consulting boring manuals. Finally, we're adding a new option to SalesforceBulkReader to read deleted/archived records.

New features in 4.6

All edges now automatically collect sample data

You no longer have to turn "debugging" mode on to collect sample data on edges during development—it's on by default now.

All edges now collect a sample (up to the first 1,000 records/1MB) of data whenever the transformation is running in Designer. When you deploy the transformation to Server, no edge data is collected (this was the case in previous versions too). Additional debug modes (debug all records/custom sampling and filtering/turn off completely) are available.

In existing graphs, edges with debug mode enabled in earlier versions will be automatically converted to "Debug all records" mode, retaining functionality as expected.

Event Listeners monitoring details

In Event Listeners, you can now view monitoring details (last execution time, number of successful and failed executions) for all your listeners.

Performance increase in Executions History view

Filtering and browsing Execution History with lots of records (hundreds of thousands) is now much faster.

Salesforce bulk read deleted records

You can now read deleted records using SalesforceBulkReader component.

SalesforceBulkReader has a new advanced configuration option called "Read mode" that allows you to retrieve all records, including deleted and archived ones.

Filter dialog shows Dictionary entries

In Filter dialog, you now can use drag&drop with Dictionary entries.

Edit Component dialog cleanup

We have simplified the Edit Component dialog, removing the Ports tab (see component tooltip for these details) and hiding rarely used options under the "Runtime" category.

Quick tutorial for new users

We're making it easier for new users to get familiar with the core concepts of CloverETL in a guided tutorial that's available directly from the welcome page (Help > Welcome, if you want to try it yourself). We hope the addition of this tutorial will help newcomers learn the basics quickly without having to leave the Designer environment for a (rather boring) study before being able to design their own data transformations.


We've made some minor changes that might affect backwards compatibility.

Newly created projects and sandboxes now have default encoding set to UTF-8 (previously it was system dependent).

Also, we've updated the bundled Java in Designer to JDK 8u121.

To help you install or upgrade to this version, we've prepared a simple checklist:

Before You Upgrade

  • Be sure to check the "Compatibility" notes for ALL intermediary releases. We mark all changes that can potentially alter the function of your existing transformations with a "Compatibility" label to make it easier for you. You can safely ignore most of them, as we try hard to keep as much backwards compatibility as we can. There's a comprehensive list of all releasesthat will help you get the information quickly.
  • Upgrade Designer and Server together. We always release Designer and Server together under a single version. It's highly recommended to upgrade Server and Designer at the same time. Although using different versions of Designer to connect to Server might work, it is not generally supported.
  • There are no incremental patches. We don't release incremental patches. Every upgrade is in fact a full installation that, if installed over older version, will automatically update whatever is necessary in your workspaces, sandboxes, and Server databases as needed.
  • Don't forget to backup. Although none of the above upgrade steps requires explicit backup, we recommend you always back up your work. The upgrade will keep all your transformations, jobflows, and configurations safe. However, as a good word of advice, it never hurts to have a backup.

Designer Upgrade

  • Download the latest version by logging into your customer account. If you no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Install the new version of Designer. You can install Designer over your existing installation. The process will automatically clean up the old version. Don't worry, you will NOT lose your workspaces, graphs, and transformations. However, if you installed some additional plugins to Designer (Eclipse plugins) you might need to reinstall them. Eclipse should automatically help you do that. When you start the application, point it to your existing workspace directory. With some major releases, we may notify you about upgrading the workspace to the latest version. In such cases, you won't be able to use the workspace with previous versions. Thus, be sure to upgrade all Designers if you're sharing the workspace.
  • Activate the product on first start. You will need a new key as we issue new license keys for every new major version (i.e. from 4.5 to 4.6). However, if you're on our maintenance program, we automatically renew the keys for you. Just go to the download area again and copy/paste the license keys from there. If you can't find the latest keys, please contact us to renew your product maintenance.

Server Upgrade

  • Download the latest version by logging into your customer account. You'll find Server in the same list as Designer downloads. If you no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Plan for downtime. Upgrading Server requires downtime, so plan your upgrades in advance. If you're running multiple environments, upgrade the non-production installation first and run all your checks there first.
  • Follow step-by-step Server Upgrade Guide. We've prepared detailed instructions on how to properly shut down Server and install a new one. Server will upgrade its database and sandboxes from any previous version automatically.
  • Activate the product on the login screen of Server Console. The license key changes with every major version (i.e. from 4.5 to 4.6) and we automatically renew the keys for you. Just go to the download area again and copy/paste the license key from there.
Release Compatibility/Upgrade notes, Features & Fixes Published Download

Server Improvements

Thread dump in Server Console now prints all stack frames instead of just a few, helping to diagnose problems.
Improvement CLO-11103 4.6.1


You now get a warning when using "dynamic metadata" based on a SQL query that returns lots of records. Such queries significiantly slow down Designer. If you don't want to modify your query by using TOP, LIMIT or ROWNUM, you can add sqlOptimization=true attribute to the dynamic metadata declaration to fix the issue.
Improvement CLO-11167 4.6.1


Fixed Data Inspector not showing debug records while a job was running if there was too little data (less than 100 records). This caused trouble in jobflows or other slow running/low counts transformations.
Fix CLO-11146 4.6.1
Data Inspector no longer indicates incomplete record sets.
Reverted CLO-10648 4.6.1
Fixed File Event Listener on SMB not working with special characters.
Fix CLO-11085 4.6.1
Fixed a NullPointerException while extracting metadata from DBInputTable when JNDI database connection was used.
Fix CLO-11049 4.6.1
July 18, 2017 Download CloverETL 4.6 4.6.1

Designer Improvements

Automatic debugging on edges during development in Designer. All edges are now set to collect samples of data (1,000 records or up to 1MB) during execution. You can still turn full debugging on (all records) or turn it off completely per individual edge.
New feature CLO-10569 4.6.0-M1
Improved "Find component" widget in the Palette.
Improvement CLO-10562 4.6.0-M1
Designer installer no longer hangs during the final "initialization" phase.
Fix CLO-10548 4.6.0-M1
License activation now accepts license keys without BEGIN and END lines.
Improvement CLO-10559 4.6.0-M1
Data Inspector now indicates whether the data shown is complete or just a truncated sample (given that only the first 1,000 records are sampled with the implicit debugging behavior)
New features CLO-10648 4.6.0

Server Improvements

Event Listeners now show overview counts for successful/failed executions.
New Feature CLO-10134 4.6.0-M1
The performance of Executions History view has been improved for large amounts of records (hundreds of thousands).
Improvement CLO-10596 4.6.0-M1
Task History now shows the number of occurences of a repeating failure.
New Feature CLO-10239 4.6.0-M1
Exported archivator task now preserves the sandbox ID, so importing the task back makes it link to the originally specified sandbox as expected.
Fix CLO-10759 4.6.0


ListFiles has a new parameter "List directory contents" (true—default) / false). Setting it to "false" works as an equivalent to "ls -d", i.e. listing the directory itself (e.g. when you want to check its existence) instead of listing the entries.
New Feature CLO-7082 4.6.0-M1
FlatFileReader behavior changed when encoding-related errors occur with Controlled policy in effect. Now, even with Controlled policy, an encoding error causes FlatFileReader to fail.
Compatibility Improvement CLO-10930 4.6.0

Salesforce connector

SalesforceBulkReader now supports reading of deleted or archived records—check out its new "Read mode" option.
New feature CLO-10398 4.6.0-M2

Designer improvements

Filter expression dialog now shows Dictionary category.
Improvement CLO-7735 4.6.0-M2
Edit Component dialog has been cleaned up. We removed the Ports tab (replaced by a component tooltip information dialog) and collapsed some of the rarely used options under Runtime category.
Improvement CLO-10797 4.6.0-M2
License activation dialog now hints what the license key should look like to avoid confusion.
Improvement CLO-10695 4.6.0-M2


Fixed autoresume of cluster nodes after database loss.
Fix CLO-10825 4.6.0-M2
Fixed ListFiles component throwing a NullPointerException for root directory on FTP.
Fix CLO-10745 4.6.0-M2
Fixed: WLS proxy plug-in for apache causes "HttpException: Expected HTTP code 200, got 405: Method Not Allowed".
Fix CLO-10646 4.6.0-M2
Fixed EmailFilter not accepting empty strings even if 'AcceptEmpty' was true.
Fix CLO-10048 4.6.0-M2
Fixed Cluster nodes occasionally switching each other to SUSPENDED mode if under heavy load.
Fix CLO-10991 4.6.0
Fixed an error thrown in XMLExtract inside a Subgraph when using a wildcard.
Fix CLO-10949 4.6.0
Fixed metadata autofilling not working properly (manifesting as an XMLExtract bug)
Fix CLO-10943 4.6.0
Fixed: ClassCastException when working with Secure parameters
Fix CLO-10824 4.6.0
Fixed WebServiceClient: Can't import XSD file into WSDL file using relative path on WebLogic.
Fix CLO-10680 4.6.0
Fixed inconsistent behavior of "Join Key" attribute of a component when exported as a parameter and used alongside dynamic parameters.
Fix CLO-10587 4.6.0
Fixed occasional NullPointerException in Server Console GUI
Fix CLO-11026 4.6.0


New projects in Designer are set to UTF-8 encoding by default.
Compatibility New Feature CLO-10539 4.6.0-M1
Designer installation package updated to JDK 8u121
Compatibility New Feature CLO-10539 4.6.0-M1
FlatFileReader behavior changed for encoding-related errors with Controlled policy in effect. Now, even with Controlled policy, an encoding error causes FlatFileReader to fail.
Compatibility Improvement CLO-10930 4.6.0
June 12, 2017 Download CloverETL 4.6 4.6.0
  • For Developers (Improvements most useful for developers bringing new functionality or optimizations in data transformation and orchestration)
  • For Administrators (Improvements or features that will help setup, install, administer and manage the platform)
  • For Support (Helps staff supporting the production environment to identify and escalate potential problems or avoid such)
  • For Security (Improvements and changes relevant to security focused staff – sys admins and developers alike)