CloverETL 4.3.0 (Milestone 2)

For the latest production release, please go to CloverETL 4.2 release notes

In the second milestone of CloverETL 4.3 we improved Code Debugging (new in M1) and we've added Salesforce Reader/Writer (supports Bulk API).

We're adding a bunch of improvements to the new code debugging feature. You can now set up conditional breakpoints – such as stop-on-counter or when expression becomes true or false. This is extremely useful when you're trying to stop on a needle while running through a huge haystack.

Salesforce connectivity is a brand new addition in this milestone. It allows you to easily read/search and write data from- and to Salesforce without having to touch the underlying technology.

About this release: This is a milestone release that we make public as a preview of the upcoming 4.3 version. You can expect production-ready release in late August/early September 2016. We don't recommend this as a production upgrade, even though some clients successfully enjoy running our newest releases without trouble.

Released Aug 9, 2016
  • Milestone
Recent Releases
4.9.1 Aug 14, 2018
4.9.0 Jul 23, 2018
4.8.3 Jul 17, 2018
4.7.1 Nov 28, 2017
4.6.1 July 19, 2017
4.5.0 Mar 14, 2017

See all releases

Try it yourself


New features coming to 4.3

Salesforce Connectivity

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

You could work with Salesforce before using our generic components for calling APIs and managing workflows. Now, you can forget those nuts and bolts. We're giving you simple Reader and Writer components that handle all the background complexities for you.

Simply create a connection to Salesforce, click-and-select what you want to read or write and you're done.

We currently support 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 inner workings of Salesforce connectivity on our blog.

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 find issues in your code instantly.

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 brings debugging of code you put into 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 your code in your transformation, without exposing you to the intricate internals of CloverETL's own guts.

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.

CloverETL - Designer execution view filter by status

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.

Installation/Upgrade Instructions for CloverETL 4.3 Milestone

To help you with installation or upgrading to this version, we've prepared a simple checklist for you:

Before You Upgrade

  • This is a milestone release. We recommend you install this version on a test Server first and use it as a preview of upcoming features and for development. Milestone releases are not support for production use.

  • 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 actually a full installation that will update whatever necessary in your workspaces, sandboxes and databases automatically as needed.
  • Don't forget to backup. Although none of the upgrade steps requires it, we recommend you 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 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. 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. 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 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 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.

Detailed list of improvements and fixes in 4.3.0 M2

ETL Developers (This item is most useful for developers; it either brings new functionality for transforming data or brings optimizations)

Administrators (This item is an improvement or feature that will help setup, install, administer and manage the application)

Support (This item helps staff supporting the production operation to identify potential problems or avoid such)

Code Debugging [ See All | Hide All ]

CTL contidion for conditional breakpoints New Feature CLO-8346 4.3.0-M2
Hit count condition for conditional breakpoints New Feature CLO-8983 4.3.0-M2
Inspect actions for evaluating CTL expressions New Feature CLO-8460 4.3.0-M2
Watch action and expression view in debug perspective New Feature CLO-8460 4.3.0-M2

Salesforce [ See All | Hide All ]

Salesforce connection New Feature CLO-8645 4.3.0-M2
Bulk reader for Salesforce New Feature CLO-8650 4.3.0-M2
Bulk writer for Salesforce New Feature CLO-8651 4.3.0-M2

Others [ See All | Hide All ]

JNDI Datasources Browser New Feature CLO-8271 4.3.0-M2
Designer bundle uses Eclipse 4.5 (Mars) New Feature CLO-8974 4.3.0-M2
Improved metadata concatenations New Feature CLO-9269 4.3.0-M2

Fixes [ See All | Hide All ]

JNDI pool connections get stuck when the job is killed Fix CLO-8835 4.3.0-M2
Cannot start designer on OS X (developer identity check fails) Fix CLO-4885 4.3.0-M2