Release Notes 3.1.414
Publication Date: December 9th 2017
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.414 release.
Cloud CMS API
- Added Favorites Service to support tagging of favorites per user across all object and data store instances with Cloud CMS
- Added activity tracking for favorited items, commented nodes and tagged nodes
- Updates and enhancements to Dashlet controllers for user interface to allow for better retrieval of favorites, recently edited items and activities per user, per project and per data instance
- Improvements to how configuration documents are managed for data stores
- Improved performance when running in a cluster
- Better indexing for collection to back faster page rendition invalidation
- Caching improvements and better key management for caching throughout service layer
- When deleting parents of owned associations, child objects are now only cleaned up if they have zero owned associations to other parent nodes - allowing for target objects to properly maintain more than one owned relationship
- Stream handling is now more efficient, improvements to memory management with less object churn
Cloud CMS User Interface Server
- Platform and Project Dashboards now include Dashlets for Activities, Favorites and Most Recently Edited content items - improved, more informative and multi-project.
- Added "Add as Favorite" and "Remove as Favorite" actions to the the document page
- Added "Manage Favorites" so that users can quickly manage their favorites across projects
- Added "Activities" pages for both platform and project level so that users can inspect editorial activities across either scope
- Fixed a bug where deeply nested forms could hang on when adding a new element interactively
- Improvements for Trial experience so that download of cloudcms-sdk.zip sets disposition header
Cloud CMS JavaScript Driver
- The readNode() method now lets you specify HTTP parameters via a third argument
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.