Release Notes 3.2.5

Publication Date: August 25th 2018

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.5 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

• Improved handling for post-release case where a snapshot may fail to generate and the release still appears unreleased (even though it had successfully released)
• Cleaned up and improved the logging of release process into stdout logs
• Handle an error case where concurrent publishing and unpublishing under high load could cause a deployment package to bypass its reporting of failed deployment records
• Enhanced node merge resolver to automatically work out what to do for cases where multiple nodes with the same QName or the same ID in a release target branch could exist and collide
• Improvements to branch fork, merge and merge conflict management to align with release service adjustments

Cloud CMS User Interface Server

• Added Handlebars processing of action config to allow for full I18N localization capabilities within the UI (using message bundle string replacement)
• Fixed a bug into Data View query builder so that views can be dynamically constructed as intended
• Data View now supports paginated scrolling of record sets
• Data View export now lets your properly specify the number of records to export (fixing bug where this would default to 25)
• Back by Popular Demand! Re-introduced the Manage Project > Forms page to allow folks to see all of their forms in place (instead of viewing within definition)
• Updated icon for document associations
• Fixed a bug where the Create Form action could fail when creating forms for associations or features
• Project Branch Picker now shows branch title when it can (instead of just Branch ID) - helpful when configuring Deployments
• Fixed a form bug whereby Number fields had null min and max by default

Cloud CMS JavaScript Driver

• Added ability to paginate executeReport() call