Customer Portal

CloverETL 4.3 brings code debugging features known from programming tools to ETL developement – conditional breakpoints, expression watching and, of course, step-by-step tracing. Additionally, we're adding a powerful but simple to configure Salesforce CRM connector.

Code debugging is a productivity feature for everyone who uses code (CTL) to define logic in mappings, Reformat data manipulations, etc. You can now pause execution of your code and trace it step-by-step to easily find a misbehaved line of code or detect unhandled data anomalies that cause trouble during execution and would be otherwise hard to spot.

New Salesforce connector allows you to easily read/search and write data from- and to Salesforce CRM without having to understand or touch the underlying APIs and connection intricacies (the connector supports full range or Bulk API operations).

New features in 4.3

Code Debugging

Tell CloverETL to pause execution of your code on a specific line in any component. You can inspect variables, dive into functions and manually advance the execution step-by-step to instantly find issues in your code.

No more trial & error runs, printing values to console log or even building debug data flows. Simply set breakpoints where CloverETL should stop execution and we'll give you full control over the code.

Milestone 2 adds Conditional Breakpoints – you can set a breakpoint to stop execution only after certain number of passes, when a given expression is true or just watch for changes of a particular value. This greatly speeds up the time it takes to find an error in code that happends only under specific conditions.

CloverETL Designer allows you to debug your code in components, e.g. Transform attributes of Reformat and Joiners, De/Normalizer code, Rollup and so on, anywhere in your transformation. Both CTL (CloverETL Transformation Language) and Java debugging is supported, giving you a unified debugging interface.

Don't worry, we're not talking about debugging some internals of the engine. We're talking about yourcode in your transformation, without exposing you to the intricate internals of CloverETL's own guts.


Salesforce CRM Connector

Read, search and write data from and to Salesforce CRM with simple to use specialized components.

Simply create a connection to Salesforce, click-and-select what you want to read or write and you're done. We're giving you simple Reader and Writer components that handle all the background complexities for you.

You could work with Salesforce before using our generic components for calling APIs and managing workflows. Now, you can forget those nuts and bolts.

CloverETL uses Salesforce Bulk API. This is excellent for working with large (and small) batches. The Standard SOAP API provides additional capabilities for advanced querying and real-time operations. However, it is not currently supported.

Learn more about the new Salesforce connector on our blog.

Execution View Filter

In Designer, you can now easily filter subjobs by status in Execution View.

Usually, you're interested only in failed or otherwise unfinished subgraphs or workers. The new filter option lets you quickly filter out what's not important.

Unsorted input for Dedup

Dedup component (deduplication) now accepts unsorted data on its input.

You need to explicitly enable this behavior by setting Sorted input = false.

In this mode, the component keeps all data in memory so be sure to use it only for data sets small enough to fit into your system's memory.

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

Before You Upgrade

  • Be sure to check "Compatibility" notes for ALL intermediary releases. We mark all changes that can potentially alter the function of your existing transformations by "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 releases that will help you get the information quickly.
  • Upgrade Designer and Server together. We always release Designer and Server together under one version. It's highly recommmend to upgrade Server and Designer at the same time. Although using different version 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 update whatever necessary in your workspaces, sandboxes and databases as needed automatically .
  • 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, no problem. Click here to recover your password or contact our CloverCARE Support.
  • Install 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. We issue new license keys with every major version (i.e. from 4.2 to 4.3). We automatically renew the keys for you. Just go to the download area again and copy/paste the license key from there. If you can't find the latest keys, you will need 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, no problem. Click here to recover your password or contact our CloverCARE Support.
  • Plan for downtime. Upgrading the Server requires downtime, so plan your upgrades in advance. If you're running multiple environments, upgrade 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.2 to 4.3) 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


Update MongoDB driver to version 2.14.2
Improvement CLO-9674 4.3.1


Cannot create runtime context URL in RunGraph in opensource Engine
Fix CLO-9743 4.3.1
Designer-Server synchronization seems to be stuck when client-side files can't be created because of invalid characters in file name
Fix CLO-9658 4.3.1
Issues in Designer with ExecuteGraph running a graph from another sandbox
Fix CLO-9650 4.3.1
CTL Debugging error "Could not list variables: Can't serialize NullRecord"
Fix CLO-9632 4.3.1
Multiple "To" email address doesn't work in Event Listener form
Fix CLO-9498 4.3.1
November 09, 2016 Download CloverETL 4.3 4.3.1

Productivity / Code Debugging

Code debugging for CTL and Java
New Feature 4.3.0-M1
Suspend a running transformation
New Feature CLO-8453 4.3.0-M1
Conditional breakpoints available
New CLO-8346 4.3.0-M2
Hit count condition for conditional breakpoints
New CLO-8983 4.3.0-M2
Inspect actions for evaluating CTL expressions
New CLO-8460 4.3.0-M2
Watch action and expression view in Debug perspective
New CLO-8460 4.3.0-M2


Dedup - added support for unsorted input
New Feature CLO-2588 4.3.0-M1


Positional drag & drop in Filter editor
Fix CLO-7817 4.3.0-M1
New metadata using 'merge' are now assigned to the selected edge
Fix CLO-7183 4.3.0-M1
Fixed: JNDI pool connections get stuck when the job is killed
Fix CLO-8835 4.3.0-M2
Fixed: Cannot start Designer on OS X (developer identity check fails)
Fix CLO-4885 4.3.0-M2
Fixed: SpreadsheetDataReader mapping dialog can't handle large amount of data
Fix CLO-9394 4.3.0
Fixed: NPE when a graph with a null output dictionary value is executed by a launch service
Fix CLO-9336 4.3.0
Fixed: Recursive parameters are not evaluated correctly
Fix CLO-9453 4.3.0
Fixed: Lookup CTL function next() returns records in reverse order
Fix CLO-9386 4.3.0

Salesforce CRM Connector

Introducing Salesforce CRM connector
New CLO-8645 4.3.0-M2
BulkAPI Reader for Salesforce
New CLO-8650 4.3.0-M2
BulkAPI Writer for Salesforce
New CLO-8651 4.3.0-M2
Salesforce connection: Advanced configuration tab for timeouts and polling intervals
New CLO-9381 CLO-9426 4.3.0
SOQL query validation
New CLO-9233 4.3.0
Simplified Salesforce login host
New CLO-9221 4.3.0


JNDI Datasources Browser
New CLO-8271 4.3.0-M2
Designer bundle now uses Eclipse 4.5 (Mars)
New CLO-8974 4.3.0-M2
Improved metadata concatenations
Compatibility New CLO-9269 4.3.0-M2
Improved TLS support
New CLO-9226 4.3.0
Keep parent jobs in filtered Execution Hierarchy
New CLO-9013 4.3.0
Enhance persistent lookup for duplicate keys support
New CLO-9085 4.3.0
September 07, 2016 Download CloverETL 4.3 4.3.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)