Cleo Clarify 6 is a major platform release that expands your integration capabilities, strengthens security across the platform, and delivers a more stable and performant runtime. This document covers what's new, what's improved, and what you need to know to upgrade from Clarify 5.x.
| Version | Availability | Release Type | Release Date |
| 6.0 | General | Major | May 11, 2026 |
What's New
Shopify GraphQL
The Shopify connector now supports GraphQL, giving you access to Shopify's modern API for richer data queries and more efficient integrations.
Business Central REST
Custom REST endpoints are now supported for Microsoft Dynamics 365 Business Central, enabling integration with BC extensions and custom APIs.
Bring Your Own PostgreSQL Database
Clarify 6 supports connecting to an externally managed PostgreSQL instance, giving you full control over your database infrastructure. This enables you to use your organization's existing database standards, backup policies, high-availability configurations, and monitoring tools rather than relying on the bundled embedded database. See Guidelines for using your PostgreSQL Database with Clarify for recommended best practices for configuration.
TLS Certificate Management
Clarify 6 introduces Trust On First Use (TOFU) certificate verification for Clarify Studio. On first connection to a Clarify Server, Studio prompts you to verify and trust the server's certificate, then caches your decision for the session. CA-signed certificates are trusted automatically. Each server instance now generates a unique TLS certificate at provisioning, and keystore management has been modernized with an integrated key manager that replaces external command-line tooling. For more details, refer to Connecting to a Server - Secure Authentication.
Redesigned GUI
- New editor enablement steps.
- Task editing and display options.
- Realignment of editor sections.
Windows Server 2025
Clarify 6 adds full support for Windows Server 2025. The installer has been rebuilt on InstallAnywhere 2025R2 with updated JDK 11 runtime components, and Consul has been upgraded to version 1.22.3 with the configuration changes needed for Windows Server 2025 compatibility.
EDI Processing
- Repeating component elements are now supported, expanding transformation capabilities for complex EDI structures that use repetition separators.
- Daylight Saving Time is now properly supported for process schedules, with corrected timezone storage and UTC as the default.
- Improved enveloping behavior: sample EDI is automatically stripped of enveloping when present, and enveloping is no longer applied when a transformation step fails, preventing malformed outbound documents.
- ISA/GS segment handling now correctly persists ISA version
What's Improved
Connectors & Adapters
- Salesforce: Resolved a bindings issue that caused failures when element names collided across objects.
- OData: Fixed an endpoint type failure and corrected inline count handling for SAP OData V2 entities.
- Acumatica: Credentials containing spaces no longer cause connection failures.
- Business Central: Connector updates no longer fail during back-and-forth navigation in the configuration wizard.
- OAuth: Resolved authentication issues related to recent provider changes from Microsoft.
Cluster Architecture
The Consul-based clustering infrastructure has been modernized. The legacy third-party Consul client library has been replaced with a purpose-built HTTP client, ACL token management now uses strongly-typed enums with secure file permissions, and Conductor service discovery endpoints are secured with HTTPS and token authentication. These changes result in more reliable cluster formation and faster recovery from node failures.
For single-server deployments, Consul token generation is now disabled when not operating in cluster mode, eliminating unnecessary errors during startup.
Performance
Server startup has been optimized with reduced VM startup delay and enhanced synced folder caching for Windows environments. Internal task throughput has been increased, and memory settings for loader and database containers have been tuned for improved stability under load.
Security
Clarify 6 includes comprehensive security hardening. XML parsing has been strengthened to prevent entity injection attacks across multiple components, password generation now uses cryptographically secure random number generation, and multiple classes of input validation vulnerabilities have been remediated. Third-party dependencies have been upgraded to their latest secure versions.
Database
- Updated PostgreSQL driver for broader compatibility across versions and hosting environments.
- Oracle RAC retry logic has been isolated so it no longer applies unintentionally to non-RAC connections.
- The internal log sequence now automatically cycles when the maximum value is reached, preventing log insertion failures in long-running environments.
- Improved Liquibase/PostgreSQL logging for better visibility during schema migrations.
Studio
- Auditor queries now automatically limit results to a configurable time window, reducing load in large environments.
- Duplicate auditor calls from listeners have been removed.
- Custom Filter Dialogs in the EDI Schema and Ruleset editors have been corrected.
- EDI Schema UI behavior and CSV normalization issues have been resolved.
- Vault error messages now clearly indicate when an incompatible vault is selected.
- Improved handling of no-data-found conditions in CIM report use cases in the Ruleset Editor.
- Added logging for user cancellation of reference processes for improved traceability.
Upgrading from Clarify 5.x
Clarify 6 is available as a new installation. There is no in-place upgrade from Clarify 5.x. However, existing projects and runtime data can be migrated to preserve your production configuration.
The Clarify 6 Upgrade and Migration Guides provide essential information to plan your Clarify upgrade, including transitioning to Cleo Integration Cloud (CIC). Refer to these guides for details steps.
Before You Begin
- Both Clarify Studio and Server must be at version 6 for full functionality. Do not mix 5.x and 6.x components.
- Back up your existing Studio installation directory, share, and database before proceeding.
- Allow all active processes to complete and suspend the workspace before taking your backup.
- Commit all projects and related resources to your SVN repository.
- Temporarily stop external notifications (including Clarify/Harmony messaging) during the migration.
Comments
0 comments
Please sign in to leave a comment.