Customer Portal

CloverDX 5.2 brings Server single sign-on using SAML 2.0.

Additionally, we’ve added support for OpenJDK 11 plus a handful of smaller improvements.


New features in 5.2

Single sign-on using SAML 2.0

CloverDX now supports single sign-on using SAML 2.0. You can use it to authenticate user sessions on CloverDX Server as well as in Designer to connect to Server projects. Look for SAML domain in CloverDX Server configuration to set it up.

Supported JDK changes

CloverDX 5.2.0 supports OpenJDK11. We perform tests with AdoptOpenJDK11 distribution. For more information about supported Java versions see this article on our knowledge base.

Other changes

  • We have started to support JBoss AEP 7.2

  • We have updated bundled JDBC driver for MySQL to version 5.1.46 to better support MySQL version 8.

  • CloverDX now uses SalesForce API version 45.

  • There are performance improvements in the CloverDX Designer related to metadata propagation so it allows to easily manipulate significantly larger CloverDX jobs.

  • Parallel reader component allows to skip lines at the start of a file

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. Typically, you can safely ignore most of them, as we try hard to keep as much backwards compatibility as possible. 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 all Designers 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 the older version, will automatically update whatever is necessary in your workspaces, sandboxes, and Server databases as needed, no user data will get overwritten.
  • 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 lost your credentials or 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—be sure to upgrade ALL Designers at once 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 (e.g. from 4.9 to 5.0). If you're on our maintenance program, we automatically renew the keys for you. Just go to the License Keys 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 tests there first.
  • Follow our 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. Server requires new license keys with every major version (e.g. from 4.9 to 5.0) and we automatically renew the keys for you. Just go to the License Keys again and copy/paste the license key from there.


Release Compatibility/Upgrade notes, Features & Fixes Published Download

Features & Improvements

SAML 2.0 support in Server console - basic login and authentication
LO-15644 Improvement
SAML2.0 - authentication in Designer-Server integration
CLO-15869 Improvement
OpenJDK 11 Support
CLO-15667 Improvement
Update bundled MySQL driver to 5.1.46
CLO-13666 Improvement
Ability to change Server Password stored in Designer
CLO-10893 Improvement
ParallelReader: add 'Number of skipped records' property
CLO-3686 Improvement
Salesforce API Upgrade (to version 45.0)
CLO-15720 Improvement
Stop support of Cloudera 4
CLO-16042 Compatibility
Inherit file.encoding property for worker
CLO-15544 Improvement
Upgrade log4j library
CLO-15543 Compatibility


Thread leak when using non-default Mongo driver
CLO-16003 Fix
Limit Execution History API call to 1000 records by default
CLO-15974 Compatibility
Unable to set property "Pass parameters from the checked jobflow"
CLO-16312 Fix
NPE on WebSphere
CLO-16180 Fix
Remove support for Lotus Domino
CLO-16104 Compatibility
Remove support for AddressDoctor
CLO-16103 Compatibility
Do not use launcher.GTK_version parameter in ini file in Designer bundle for Linux
CLO-16006 Compatibility
Fixed: Task remains running forever
CLO-15975 Fix
NullPointerException when Creating DB Connection
CLO-15811 Fix
Leaking graph instances in JMX notifications
CLO-15638 Fix
Limit number of elements in an IN predicate
CLO-15451 Fix
Obsolete config properties of graph in sandbox
CLO-15384 Fix
Invocation of Data Service fails if the request contains session token
CLO-15301 Fix
ExecuteScript - cannot pass path with space to powershell
CLO-14658 Fix
WebServiceClient - The URL could not be reached Error
CLO-13638 Fix
Data service creates invalid JSON or XML when no records are produced
CLO-13106 Fix Compatibility
April 02, 2019 Documentation Download CloverDX 5.2 5.2.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)