Release Notes 3.2.46

Publication Date: December 1st 2019

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

Update Recommendations (On-Premise Only)

• For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the `reindex-datastore` command via the Cloud CMS Command Line Client (http://www.cloudcms.com/documentation/cli.html#reindex-datastore).

You can execute it like this:

``` cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password> ```

Where the `username` and `password` are the credentials for your administrator account.

Enhancements

Transfer

• Transfer exports now execute more quickly with more efficient use of iterators and lookup maps\

Branches

• Branch Changes now hand back more information and compute more quickly, making it easier for editors to cherry pick for content from other branches

Bug Fixes

Transactions

• Fix to correct for an occasional path by which nodes could be committed to the master collection without the required `_system._op` and related tracking information. The result of this bug was that items could be missing on a Branch Changes calculation and editors might not see the items they expect on the Copy or Compare branch actions. The should obviate the prior workaround which involved running the command line tool to reapply those properties.

Favorites

• Fix so that Favorites are pulled back on the Project and Platform dashboards as intended for users with minimal permissions

Transfer

• Fix so that memory is managed more efficiently allowing for exports of much larger sets of content to properly paginate on query and store to disk with less heap growth
• Fix so that transfer exports execute more quickly

Behaviors

• Fix so that behavior bindings are correctly remounted after a branch merge operation for some cases

Principals

• Fix to assert that principals can neither be created nor updated with missing or incorrect `type` information in the JSON payload

Tree

• Fix so that the order of the flattened results computed in the tree controller sorts with the `master` branch at the top

Attachments

• Fix so that nested `_attachment` properties and Attachment form fields are supported within content types as expected