Release Notes 3.2.60

Publication Date: October 2nd 2020

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

New Features

Command Line Client

• New admin command to recreate filenames for a branch.
• New admin command to run node validation across all content in a branch.
• Added `path` switch support for node read, list and query.
• Added support for local `.rc` files to store switches that should be automatically applied on each invocation (such as `repositoryId` or `branchId`).
• New commands for retrieving node children, relatives and versions.
• For more information on the Cloud CMS Command Line Client, see https://www.cloudcms.com/documentation/cli.html.

Documentation

• Added new REST API Cookbook with examples on how to use the Cloud CMS HTTP REST API - for more information, see https://www.cloudcms.com/documentation/cookbooks/rest.html.
• Added Scripting API documentation to provide guidance and examples on how to build server-side scripts and templates - for more information, see https://www.cloudcms.com/documentation/scripting.html.

Node Validation

• Added new background Job/Worker to support adhoc schema validation of all of the nodes in a branch.

Enhancements

Administrative

• The Recreate Filenames worker is now more efficient and more resilient when generating and updating filenames across a large set of nodes. Nodes that fail to have their updated filename applied are marked on the job.

Authentication Tokens

• Token expiration API call now allows for an `all` parameter to indicate that refresh token should also be expired, resulting in a full expiration of authentication state.

Relator Properties

• When refreshing a node, the associations around the node (both incoming and outgoing) are inspected and repaired if the source or target node of those associations is missing.

Bug Fixes

Command Line Client

• Fix parsing for target changeset ID on branch revert() call.

Content Model Builder

• Fix so that `enum` property is not overwritten when dragging scalar field types into nested array elements.

Email Templates

• Fix so that Script URL Resolvers return the correct URL when configured via properties file (see https://www.cloudcms.com/documentation/docker/configuration/api-server.html#script-resolvers).

Files and Folders

• Fix so that the deletion of a child association (as opposed to either the source or target node) will properly propagate and incur unindexing of all ancestral child elements in the path.

Merges

• Fix to an edge case where highly concurrent merges against the same branch (i.e. many threads competing to merge into a target branch at the same time) could occasionally fail due to an extraneous changeset being introduced.

Relator Properties

• Fix to the ordering of relator property processing to account for a rare transitivity issue that could occur when committing large sets of nodes.

Tree

• Fix for Tree path parsing to support paths with filenames that have a `/` character in them.

Workflow

• Fix so that workflows launched from the user interface naturally track the runtime repository and branch.