Customer Portal

In CloverDX 5.14 we are introducing a new concept – CloverDX Library – which will allow you to easily share ready-made solutions composed out of subgraphs. Libraries offer significant improvements to code reusability and sharing in CloverDX. Any Library known to Server is automatically recognized by Designer and added to component Palette to leverage its features.

We are further enhancing the ability to deploy secure solutions by adding support for AWS Secrets Manager. Native support for Azure KeyVault and AWS Secrets Manager allows CloverDX jobs to seamlessly use managed passwords in any context – whether to authenticate a database connection, API, file protocol or any other place where use of secrets is needed.

Besides new features, CloverDX 5.14 brings several platform updates – Eclipse IDE update for CloverDX Designer, DB2 11.5 is newly supported version as Server backend database, bundled Vertica driver got updated to latest available version, and support for WebLogic was added to keep our customers on supported version of WebLogic server.

As with previous releases, we worked on general platform security and CloverDX 5.14 is the most secure version of CloverDX so far.


New features in 5.14

CloverDX Libraries

We are introducing a new entity to CloverDX platform – CloverDX Library. Each library is a self-contained redistributable package that can contain reusable subgraphs and other resources.

Libraries can be created in CloverDX Designer and then deployed to CloverDX Server. When Designer connects to a Server with libraries installed, it will automatically detect content of libraries on the Server and display them in Component Palette for easy access.

This allows much faster reuse of ready-made solutions compared to previous approaches.

Each library exposes a public interface – a set of subgraphs designated by library author. These subgraphs are automatically shown in Component Palette when Designer connects to the Server. Other resources within the library are hidden (but accessible if needed). This helps library users to focus on the important parts rather than having to navigate in potentially large, shared projects.

Libraries are best used for sharing various artefacts inside your organization. For example, you can use them to share custom connectors, validation rules, various helper processes, use them to enforce data standards and more.

Libraries ensure all your code uses common utilities and prevent copy-paste development. This in turn avoids various copy-paste errors and makes project maintenance easier and more effective.


AWS Secrets Manager support

We are continuing effort to onboard new secrets managers. In CloverDX 5.14, we added support for AWS Secrets Manager.

When creating your Secrets Manager in CloverDX Server Console you can now pick either AWS Secrets Manager or Azure Key Vault. While each secret manager lives in only one cloud (AWS or Azure), CloverDX is not restricting their usage and you can use any secret manager regardless of your deployment model – even on premise if needed.

Secrets stored in a secret manager configured on Server can be used in any context where you can use CloverDX parameters. Secrets can be access using a special syntax ${secret:<manager-name>/<secret id>} (for example, ${secret:aws_prod/dwh-pass}).

Smaller updates

Reformat component renamed to Map

We renamed Reformat component to Map. The change does not have any impact on the component functionality – only label of newly created components will be different. Since this is only cosmetic change, you won’t need to change your existing jobs in any way, and they will work exactly as before.


EmailSender and EmailReader support OAuth2 on Azure

Both components have been extended to allow usage of OAuth2 connection for authorization when using Microsoft Exchange Online via IMAP. This change was implemented as a response to Microsoft’s plan to remove support for basic authentication for Exchange Online in October 2022. Same mechanism can be used with other OAuth2-compatible mailing services (e.g., Yahoo).


Eclipse update

We updated Eclipse IDE, a platform CloverDX Designer is built on top of, to version 2021-09. This should not have any impact on regular users of CloverDX Designer, but you may notice some small user interface changes.



We now support newer version of WebLogic for your Server deployments. WebLogic previously supported by CloverDX is no longer supported by Oracle (its “grace period” ended in December 2021) and we recommend all users to migrate to which does not yet have any end of support date announced.


DB2 update

CloverDX now supports DB2 11.5 for its backend database. Previously supported version (DB2 10.5) is end-of-life since 30th April 2020. We urge all customers to upgrade to more recent version of DB2 to ensure their platform fully supported from IBM.


Profiler Console Deprecated

CloverDX Profiler Console is no longer actively developed and was removed from All-in-one installer for CloverDX. This does not affect ProfilerProbe component which remains part of CloverDX and its functionality remains unchanged.

Profiler Console remains available for download as separate package for each supported application server and can be installed as needed.



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


EmailReader Error when Reading Email Body - NullPointerException
CLO-24542 Fix


CVE FIX - Upgrade commons-text to v1.10.0
CLO-24743 Security
November 15, 2022 Documentation Download CloverDX 5.14 5.14.3

Security Fixes

CVE FIX - Upgrade Jetty to v9.4.46
CLO-23427 Security
CVE FIX - Upgrade Spring to v5.3.19
CLO-23390 Security


Server Console - navigation pane display issues
CLO-23363 Fix
EOF Exception when accessing Persistent Lookup with multiple jobs simultaneously
CLO-23364 Fix
SnowflakeBulkWriter fails when no record is received by the component
CLO-23258 Fix
May 12, 2022 Documentation Download CloverDX 5.14 5.14.2

Security Fixes

CVE FIX - Spring: CVE-2022-22965
CLO-23227 Security
April 07, 2022 Documentation Download CloverDX 5.14 5.14.1


Library deployment
CLO-22889 Improvement
Show Library subgraphs in Palette
CLO-22890 Improvement
Show Library subgraphs in Add Component dialog
CLO-22891 Improvement
Export Server project as a Library
CLO-22920 Improvement
Libraries configuration export/import
CLO-22949 Improvement
Management UI for Libraries
CLO-22950 Improvement

Sercret Managers

Secret Managers: AWS Secrets Manager
CLO-22025 Improvement

OAuth2 Connection

Authorize OAuth2 connection without Designer
CLO-21698 Improvement
Add option for EmailSender and EmailReader to accept OAuth2 connection
CLO-22915 Improvement

Deployment Stack

Support WebLogic
CLO-20003 Improvement
Upgrade supported version of DB2 server database
CLO-22346 Improvement
Upgrade bundled Eclipse to 2021-09
CLO-22347 Improvement
Docker Image: Update base OS image, Java and Tomcat
CLO-22597 Improvement
Deprecate Profiler Console
CLO-22749 Improvement
AWS and Azure Marketplace offer: update JDK, Tomcat and JDBC driver
CLO-23008 Improvement
AWS Marketplace offer: upgrade used Postgres DB
CLO-23009 Improvement


Upgrade Vertica driver to v11.1.0
CLO-13027 Improvement
HashJoin is not reliable on decimal fields
CLO-21795 Improvement
Subgraph color and icon in Job Inspector
CLO-22213 Improvement
Extend REST API to allow manipulation with server worker
CLO-22341 Improvement
Monitors - improve counting the number of working and failing triggers
CLO-22601 Improvement
Server Data Inspector - add button to load all available records at once (1000 by default)
CLO-22768 Improvement
Worker Startup Retry Delay Property
CLO-17855 Improvement


CVE FIX - Upgrade avro to v1.11.0
CLO-21467 Security
CVE FIX - Upgrade commons-io to v 2.11.0
CLO-22592 Security
CVE FIX - Upgrade guava to v31.0.1
CLO-22593 Security
CVE FIX - Upgrade httpclient to v4.5.13
CLO-22594 Security
CVE FIX - Upgrade jakarta.el-api to v4.0.0
CLO-22595 Security
CVE FIX - Upgrade kafka-clients to v2.8.1
CLO-22596 Security
CVE FIX - Upgrade apache-mime4j to v0.8.6
CLO-22652 Security
CVE FIX - Upgrade Tomcat to 9.0.58
CLO-22818 Security
CVE FIX - Upgrade jackson-databind to v2.13.2
CLO-23126 Security
Change password after first-time login (Server)
CLO-18597 Security
User should be notified after a new Server account is created
CLO-18598 Security
Long Password DOS Attack
CLO-21776 Security
HTTP only cookie attribute not set
CLO-21777 Security
Secure HTTP Headers Missing
CLO-21778 Security
Enforce strong password policy Improvement
CLO-22763 Security
Enable account lock-out policy by default
CLO-22764 Security


Corrupted characters in SQL Query dialog
CLO-23054 Fix
FastSort ArrayIndexOutOfBoundsException
CLO-22822 Fix
Graph parameter actions do not work with enum attributes
CLO-22725 Fix
Assigning an output value to itself in CTL doesn't work anymore
CLO-22623 Fix
"java.lang.Error: SWT Resource was not properly disposed" in console log
CLO-22571 Fix
Server web UI: IllegalArgumentException on sort, select item & reload
CLO-22427 Fix
Server UI - restart job dialog allows to execute a job on suspended node without confirmation
CLO-22384 Fix
Data Apps - cannot set custom response message
CLO-22318 Fix
Mapping in ExecuteGraph cannot be opened when Parquet is used
CLO-22309 Fix
Input Mapping to Dictionary of Type Variant
CLO-22170 Fix
Oracle JDBC specific reports warning 'Unsupported holdability value'
CLO-22162 Fix
Backward incompatible changes in graph parameters evaluation introduced in 5.12
CLO-22140 Fix
Salesforce Connection with Empty Security Token Does not Work Properly
CLO-20506 Fix
Runtime does not start if log level is set to DEBUG
CLO-22057 Fix


Remove Profiler Console from Designer + Server installer
CLO-22468 Compatibility
March 29, 2022 Documentation Download CloverDX 5.14 5.14.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)