Customer Portal

CloverDX 6.2 marks another major update to the CloverDX platform with regards to usability for business users (domain experts). In this release, we focused on connectivity and collaboration between domain experts and IT team to allow organizations to work with their data more effectively.

We’ve added support for Data targets which allow Wrangler users to write their data to any system instead of just CSV or Excel files. Data targets are managed in Data Catalog just like Data sources allowing domain experts to quickly see all the data they can work with – whether on the input or on the output side.

Data targets also make it possible for Wrangler users to build data mappings in Wrangler’s simple interface and then share the resulting mapping with the IT team. IT can then bundle the Wrangler-created mappings as part of a larger process thus allowing Wrangler users to directly collaborate and contribute to larger solutions for data processing.

CloverDX 6.2 adds five more validation steps in Wrangler to make it easier to verify that your data matches expectations to ensure that only valid records are processed. The new Split column step allows users to easily split data into multiple columns without using complex formulas.

We’ve added support for running CloverDX on Java 17. Java 17 is a newer LTS (Long Term Supported) release of Java with support at least until 2027 (compared to Java 11’s support until 2024). At the same time, Java 17 allowed us to increase performance in many cases as well as enable Job queue in Docker for increased stability when running under heavy load.

New features in 6.2

Write to any target in Wrangler

With CloverDX 6.2 we are introducing another major functionality update – CloverDX Wrangler can now write to any target system. You can create Data targets and publish them in the Data Catalog.

Once a target is available in the Data Catalog, you can write to it from your Wrangler jobs instead of the default CSV or Excel targets.

Data Catalog showing Data Sources and Data Targets

Data targets work just like Data sources. They are built in CloverDX Designer so that you can create targets that implement connectivity to any system – whether it is a cloud application like Salesforce, on-prem or cloud database, or even an API.

To make it easier for you to run your jobs in Wrangler while making sure you do not push incomplete data to your target system, we’ve added Test run functionality. Writing to target is disabled during the Test run so you can focus on getting your data right before enabling the writes to populate your target system.

Visual data mapping in Wrangler

Data targets can request data to match a certain structure by prescribing a set of required or optional columns. When using such a target in your Wrangler job, you will have access to a new Mapping mode which allows you to easily map your data to the layout your target requires.

Animation showing automap and drag & drop in Mapping mode.

Mapping is interactive and validated as you are working on it. This means you are getting immediate feedback about whether your mapping is complete and whether all required columns are mapped or not. At the same time, mapping does not use any code – it is configured using drag & drop which makes it easy to use.

To make mapping of large number of columns easy, we offer an Auto-mapping functionality. Auto-mapping can suggest column mapping automatically leaving only subset of columns for manual mapping.

Collaboration between business and IT

In CloverDX 6.2 we’ve extended the ability to export your Wrangler jobs and import them into your Designer projects. Jobs imported in this way appear as subgraphs in Designer project. These subgraphs can then be used as any other subgraph as part of a more complex process.

A typical use cases for this are data ingestion or customer data onboarding. In both cases you often need to ingest data in many different formats (for example, from different clients). Building ingestion jobs to read all input formats in Designer can be very time consuming and require a lot of effort from the IT team.

A better solution is to use CloverDX Wrangler in which domain experts create mappings from the source data layouts – they know the data well and can often do this faster than IT-led implementation. Once their Wrangler mappings are ready, they can be exported and shared with the IT team who can integrate them into a larger framework built in Designer.

Diagram showing steps Domain experts and IT team must take in order to integrate Wrangler mappings into Designer-built project.

In this way, it is possible for non-technical domain experts to directly design transformations that are part of a larger process that is implemented in Designer and automated on a Server. This can save significant amount of time during processes such customer onboarding.

New Wrangler steps

We are continuing to expand the functionality that allows you to manipulate your data in CloverDX Wrangler. In this release we added several new steps:

At the same time, we’ve improved usability of many other Wrangler steps. In particular, we’ve added support for content assist and real-time validation of formula into all formula steps (Calculate formula, Filter rows based on formula, Validate with formula).

Screenshot of content assist popup in formula editor showing list of columns in the data set.


Health check for CloverDX libraries

CloverDX libraries can now designate a special Health Check job in their configuration. The health check job is used by the CloverDX Server to verify connectivity and status of the library – the Server runs the job periodically and depending on its status can mark the library “unhealthy”.

The job can be used, for example, for testing whether APIs that the library needs to work are still accessible etc. It is possible to create Monitors in Operations Dashboard to track the status of library health. In this way you can easily monitor the overall health of the connectors that are deployed on your CloverDX Server instance.

Screenshot of CloverDX Console showing health check configuration of a library.

CloverDX on Java 17

We are continuing updates of CloverDX stack and with CloverDX 6.2 you can now run CloverDX Server on Eclipse Temurin JDK 17 when using Apache Tomcat 9 application server.

Java 17 is an LTS (Long Term Support) version with Eclipse Foundation providing support at least until October 2027 compared to Java 11 with support ending in October 2024.

At the same time, you can expect better performance when running CloverDX Server on Java 17. Based on our tests, you should see lower overall memory consumption and 5% to 20% improvements in processing time depending on the use case.

We’ve updated our Docker configuration so that it will now use Java 17 by default. This has one huge benefit – Java 17 properly reports performance metrics when running inside the container which allows us to enable the Job queue by default. This will increase the overall stability of CloverDX Server, especially under heavy load.

Smaller updates

Snowflake driver update

We’ve updated bundled Snowflake driver to the latest version. This update allows us to use a newer and simpler layout for JDBC URL when creating Snowflake connections.

SMB (Samba) access change

We’ve updated the smbj library which provides SMB connectivity in CloverDX. The new version introduces stricter controls for anonymous and guest user access to comply with SMB specification. These changes mean that it is no longer possible to use anonymous access to log-in to SMB. As a workaround, SMB administrators can create user “guest” without a password.

Support package and logs

We’ve added the ability for Server Console users to download support packages from all nodes of a cluster with a single click. This can save a lot of time when working on larger cluster deployments.

Additionally, it is now also possible to download logs for complete execution tree from Executions History in Server Console. Again, this can help when solving issues when running more complex job hierarchies.


We’ve introduced several new API endpoints:

  • To abort a running job: /executions/abort and /executions/{runId}/abort
  • To download a support package from a single Server node: /server/support-package
  • To download a combined support package from all currently connected cluster nodes: /cluster/support-package

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


Redirect users to login page after session timeout or is invalid
CLO-26703 Security
Invalidate session of modified users after account change in Configuration
CLO-26699 Security
November 07, 2023 Documentation Download CloverDX 6.2 6.2.1

Data Targets in Wrangler

Visualization of the target connectors in the catalog
CLO-26987 Improvement
Create target from the Data Catalog
CLO-26979 Improvement
My Targets page
CLO-26912 Improvement
Add My Targets page into job module
CLO-26918 Improvement
Add target structure table into target detail
CLO-26919 Improvement
Create file target action
CLO-26917 Improvement
Empty target screen
CLO-26916 Improvement
When file source/target is deleted, delete the data file too
CLO-27039 Improvement
Better UI for configuration section in My sources/targets
CLO-27321 Improvement
Change settings for the default CSV target
CLO-27363 Improvement
My Targets and My Sources should not look like a file manager
CLO-27176 Improvement

Mapping in Wrangler

Mapping mode
CLO-26983 Improvement
Mapping actions in the editor
CLO-26984 Improvement
Automap functionality
CLO-26985 Improvement
Advanced search in the mapping mode (filters)
CLO-27000 Improvement
The badge for the mapping status
CLO-27042 Improvement
Undo/redo for mapping
CLO-27071 Improvement
Mapping panel improvements
CLO-27043 Improvement
Use of Wrangler "mapping" jobs in Designer projects
CLO-27208 Improvement

New Steps in Wrangler

New step: Split column step
CLO-26289 Improvement
New step: Validate against list
CLO-26966 Improvement
New step: Validate text length
CLO-26965 Improvement
New step: Validate pattern match
CLO-26963 Improvement
New step: Validate value range
CLO-26960 Improvement
New step: Validate if not empty
CLO-26959 Improvement

Wrangler Improvements

Allow users to see exact full value of cell
CLO-25580 Improvement
Context menu action 'Sort' should sort on the selected column
CLO-25638 Improvement
Move My sources into a separate item in the menu
CLO-26257 Improvement
Test Run action
CLO-27272 Improvement
Prevent new Wrangler users from logging in if the user limit is reached
CLO-27274 Improvement
My jobs table - Open context menu anywhere
CLO-26286 Improvement
Format dialog should validate the data formatting string
CLO-26323 Improvement
Inform user better when job import completes
CLO-26774 Improvement
Improve default name for copy of Wrangler job
CLO-27182 Improvement
Add icon to the Step panel when there is an error
CLO-27322 Improvement
Hints / examples for formulas
CLO-27357 Improvement
Search in preview columns
CLO-27358 Improvement
Formula - linter and autocomplete
CLO-27361 Improvement


Library health check
CLO-26923 Improvement
Data Target Connectors for Libraries
CLO-26769 Improvement
Permissions for Data Targets in Libraries UI
CLO-26772 Improvement
Improve validation in library connection form
CLO-26722 Improvement
Library Init Job - add description to server UI
CLO-26605 Improvement

Java 17

Server support for Tomcat on Java 17
CLO-22146 Improvement
Update docker image to use Java 17
CLO-27219 Improvement
Re-enable job queue in containers with Java 17
CLO-22145 Improvement
Update bundled jdbc drivers for java 17
CLO-27124 Improvement


Update bundled Snowflake driver to v3.13.33
CLO-25930 Improvement
Update our Snowflake JDBC URL template
CLO-25929 Improvement


REST API - abort job
CLO-24390 Improvement
REST API - Support package download
CLO-20663 Improvement
REST API - Download support package from all connected cluster nodes
CLO-20662 Improvement


Allow using empty password in smb/smb2 protocol
CLO-27266 Improvement
The port field in the Event Listener in the Server GUI accepts numbers only
CLO-27127 Improvement
Prefer locale without script or variant
CLO-27099 Improvement
Add HEAD request method to Data Service REST Job Configuration
CLO-26560 Improvement
Improve export of execution logs package content
CLO-26852 Improvement
Download support package from all cluster nodes in server UI
CLO-26827 Improvement
Execution log export for entire execution tree
CLO-24679 Improvement
Configure port for Designer runtime
CLO-21699 Improvement


Add component dialog logs warnings
CLO-27557 Fix
Cannot use already installed java when installing Designer on Windows
CLO-27313 Fix
Links to documentation in Wrangler should open a new tab
CLO-27264 Fix
CloverDX Cluster Displays False Positive Errors
CLO-27179 Fix
Wrangler lookup with non-existing source fails with NPE
CLO-27165 Fix
NPE when exporting library from designer
CLO-27149 Fix
Spreadsheet mapping performance regression caused by SWT
CLO-27033 Fix
Library version and author should be mandatory
CLO-26925 Fix
WebServiceClient - no timeout for WSDL file download
CLO-26921 Fix
Clustered job can get stuck between phases
CLO-26920 Fix
NPE when linking non-existing lookup in designer
CLO-26781 Fix
Improve errors in check config - Unexpected null value
CLO-26483 Fix
Cell hover tooltip is cut off by window/monitor bounds
CLO-26203 Fix
Server Tutorial - dialog for the first step sometimes doesn't pop up
CLO-26140 Fix
Filter step breaks previews when it fails at runtime
CLO-26062 Fix
Cannot download input/output file if its name contains URL special characters
CLO-26022 Fix
Target dialog file extension is optional
CLO-26001 Fix
Loading icon in data preview appears over the config dialog
CLO-25901 Fix
Job inspector does not display non-utf-8 characters correctly
CLO-25222 Fix
Link parameter file creating new files when used with ${paramName}
CLO-24448 Fix
Cannot Edit Secure Dynamic Parameters
CLO-23955 Fix


CVE FIX - upgrade hsqldb to 2.7.1
CLO-27065 Security
CVE FIX - Upgrade guava to v32.1.1.jre
CLO-26728 Security
CVE FIX - Upgrade io netty
CLO-25309 Security
Update smbj to version 0.10.0
CLO-27195 Security
OAuth2 provider with PKCE
CLO-25658 Security
Require users to enter previous password on password change
CLO-26700 Security
Implement Cache-Control header in Server's GUI
CLO-26702 Security
Broken user profile for LDAP (and SAML) managed users
CLO-27228 Security


Ban specific sandbox location
CLO-27114 Compatibility
Ban specific sandbox name (e.g. Libraries)
CLO-24020 Compatibility
Update smbj to version 0.10.0
CLO-27195 Compatibility
October 03, 2023 Documentation Download CloverDX 6.2 6.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)