Release Notes 3.2.4
Publication Date: August 22nd 2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.4 release.
Cloud CMS API
- Upgraded to Tomcat 9.0.11
- Fixed a bug whereby schema references (using $ref) were not being tracked properly as dependencies during dictionary compilation
- Fixed a bug whereby Tree API path resolution and query could fail for some special characters (non-ASCII or big charset)
- Improved logging for Hazelcast cluster configuration
- Upgraded to latest Hazelcast and ensure Hazelcast SSL disabled by default
- Fixed a branch merge bug wherein a source node merging into an existing, saved target node could cause the target node to lose track of its previous changeset ID
- Improvements to branch merging and release execution
- Fixed support for Zookeeper discovery with clustering
- Merge conflicts are now cleaned up on finalize() and release() so that other release branches that a given release branch had conflicted with (or who had conflicted with us) will automatically purge old merge conflicts that are no longer required given that the given release branch had already executed successfully
Cloud CMS User Interface Server
- Improved support for message bundles and localized text within the UI (extensible via config service)
- Enhanced default message bundle for locale and language text
- Added ability to customize Publishing by content type (customizable workflows per type and also custom HUD buttons on document page per type)
- Fixes and improvements to visual Content Model Builder to support more field types and form configurations
- Visual Content Model Builder supports content types with features and $ref references
- Improved support for custom Media Type and Field Editor implementations within custom UI modules
- Fixed a bug that occurred when Copying a Form on the Project Forms page
Cloud CMS Developer SDK
- Added sample implementation for a custom Content Model Field Editor
- Added sample implementation for a custom Media Type
See Gitana with your own content
Talk with a solutions engineer about your content model, governance requirements and deployment — hosted in our cloud or running in yours.