All Release Notes

Release Notes 3.2.28

Publication Date: March 6th 2019

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.28 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the [Cloud CMS 3.2 Migration Documentation](https://www.cloudcms.com/documentation/docker/maintenance/upgrades.html).

Cloud CMS API

  • Support for MongoDB 3.6.10
  • Significant improvements to performance and scalability through benchmark testing of standalone and clustered environments - additional caching for tenant and client services, faster API methods
  • Improved support for bulk node creation via multipart POST to allow for individual property specification using file parts
  • Enhanced S3 storage provider to support improved chunking on large file multipart uploads
  • Improved rule execution so that some critical paths execute as system user, making things faster and also reducing potential of permission check problems

Cloud CMS User Interface Server

  • Updates to workspace and release conflict resolutions screens to tighten them up and improve usability
  • Fixed a bug in the forms engine to improve support for multi-value strings, allowing for custom join and split functions and improved parsing of delimited values
  • Added Markdown field to the Content Model builder
  • Fixed a bug in the Content Model builder that had prevented the Preview button from working for some Related Node fields
  • Improved display rendering on Overview page for some control types including Related Content
  • Fix for responsive layout of workspace bar for smaller screens

Cloud CMS Java Driver

  • Added `ref()` method to all driver objects letting folks quickly construct a reference (these are commonly used for permission checks, exports and many other aspects of the API)
  • Updated AutoClientMapping properties and methods
  • Removed Warehouse datastore and interaction objects




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.