CloverDX 5.5 introduces Data Apps, a new simple interface for business users to interact with data jobs on the CloverDX Server. Additionally, we’ve added a new “support package” to simplify your interactions with CloverCARE support team, and we’ve significantly improved deployment automation.
Data Apps is a new front-end for interacting with data jobs aimed at empowering non-technical users. You can publish and share multiple Data Apps without forcing your users into the Server Console or into understanding the underlying implementation. Instead, they access the Server via a new Data Apps Catalog, and each app represents a task they need to accomplish - upload a new file for processing, get an updated report, execute a query, etc.
Having standalone login page and appealing catalog of available Data Apps, the end users don’t need to know about the existence of backing CloverDX Server at all and they can focus on what matters the most. Custom report generators, analyzers and validators providing on demand data and analysis when they are needed, alongside with reprocessing applications triggering you custom data processing and much more can be available on a single click.
The Support Package is a collection of information packed as a ZIP file useful when troubleshooting and investigating production incidents. It’s especially helpful for CloverCARE Support.
Attaching the archive to support tickets can help expedite the resolution process by providing the support team with all the information typically needed in most support tickets at once. It is recommended to attach it to all tickets related to stability, connectivity or performance of the server.
The Support Package ZIP can be created fairly easy - by a single click at CloverDX Server UI.
Configuration XML file exported from CloverDX server can be used as a full backup of particular server because, from now on, it’s possible to override the configuration of the server by Import operation so that the server does not contain anything else but entities from imported configuration XML. In addition, sandbox properties can be exported and imported.
Bundling of configuration with jobs was introduced in 5.5. One can put XML configuration file at sandbox root. Such a configuration file is automatically imported when new sandbox is being created. This is especially helpful when the sandboxes are auto-discovered and auto-created during first start of server but, of course, can be beneficial when creating new sandbox on existing location.
Recursive S3 listing in ListFiles component was optimized so that it’s much faster than before. In order to decrease memory requirements, the listing is done in a streaming fashion.
It’s easier than ever before to open a project at CloverDX Designer. The projects can be easily imported from URL. Just copy & paste or drag & drop the URL to CloverDX Designer and that’s it.
In order to improve security, salted hashes are used to store CloverDX user password in database.
In addition, passwords in JMS listeners and Send JMS message tasks are now encrypted using a master password and plain text passwords in imported configuration are encrypted using the master password.
To help you install or upgrade to this version, we've prepared a simple checklist:
Before You Upgrade
|Release||Compatibility/Upgrade notes, Features & Fixes||Published||Download|
|March 17, 2020||Documentation Download CloverDX 5.5 5.5.2|
Features & Improvements
|February 13, 2020||Documentation Download CloverDX 5.5 5.5.1|
Features & Improvements
|December 17, 2019||Documentation Download CloverDX 5.5 5.5.0|