Release Notes 3.2.12
Publication Date: January 2nd 2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.12 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
- Fixed a bug whereby projects containing legacy datastore types (such as "warehouse") could fail to export
- Ensure that historic password policy is bypassed when adjusting special principal passwords via Spring bean configuration
- Speed up API startup time by reducing the number of classes scanned for annotation processing
- Deployment publishing between branches now increments path and search indexes much faster
- Fixed a bug where two repositories with the same branch ID could result in incorrectly bound rules and behaviors for certain cases
- Added chunking for file/folder system when querying node paths recursively, allowing for much larger sets of recursion to be processed more efficiently
Cloud CMS User Interface Server
- Fixed "Move To" and "Copy To" actions so that they now allow default to picking folder targets exclusively
- Several improvements to visual Content Model Builder
- Project list page now shows additional information (creation date, modification date, etc)
- Fix so that creating a new version of a workflow model preserves the "email" and "emails" properties
- Fix to the default Set Local and Remove Locale action configs so they show up when expected
- Fix a bug where the search term would "stick" between clicks which could cause a seemingly empty set of items to show up on the new page (since filter was being errantly applied)
- Removed "tip view only" form Workflow Models screen
- Added "Deploy Workflow Model" and "Undeploy Workflow Model" buttons to the Workflow Model overview page
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.