CloverETL 4.6.0 (Milestone 2)

This milestone version is no longer supported/available.
For the corresponding production release, please go to CloverETL 4.6 Release Notes.

CloverETL 4.6 Milestone 2 brings minor UI enhancements and fixes.

This release completes the preparation for the 4.6 release planned for June 2017. It extends SalesforceBulkReader with the ability to read deleted records, cleans up some issues in Designer UI, and brings important fixes.


About this release: This is a milestone release that we publish as a preview of the upcoming CloverETL 4.6 version. You can expect the production-ready release in summer 2017.

Milestone versions are not recommended as a production upgrade. However, some clients successfully run applications using the milestone releases without trouble.


Released May 16, 2017
  • Milestone
Recent Releases
4.7.0 Oct 10, 2017
4.6.1 July 19, 2017
4.5.0 Mar 14, 2017
4.4.1 Feb 14, 2016
4.3.1 Nov 10, 2016
4.2.1 Aug 18, 2016
4.1.4 Jun 1, 2016

See all releases


New features in 4.6 Milestone 2


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.

CloverETL - Filter Dictionary

Filter dialog shows Dictionary entries

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

CloverETL - Filter Dictionary

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.


Installation/Upgrade Instructions for CloverETL 4.6 (Milestone)

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

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 supported for production use.

  • 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 releases that 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.2 to 4.3). 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.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.6 (Milestone 2)

Salesforce connector

SalesforceBulkReader now supports the reading of deleted or archived records—see "Read mode" option.
New feature CLO-10398 4.6.0-M2

Designer improvements

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

Fixes

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


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)