Cloud CMS Release 3.2.67

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

Update Recommendations (On-Premise Only)

With this version of Cloud CMS, we have disabled the deprecated Elastic Search Transport Client and have switched to using our Condor HTTP client. As such, connectivity between the api and elasticsearch services are no longer using port 9300 by default. They are now using port 9200 by default.

Please check your configuration to make sure that the API can connect to Elastic Search’s HTTP Endpoint.

For information on configuring Elastic Search for Cloud CMS, please see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#using-the-condor-http-client

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

Indexing
Logging
  • Improved logging for indexing operations (for platform and project tenant logs as well as container-level logs).
  • More detail now offered for server-side script exceptions so as to indicate script node IDs and other runtime information.
Transfer
  • Faster performance of export and import due to improvements in the performance of reference resolution.

Bug Fixes

Branches
  • Fix so that failed node assembly won’t get stuck in a loop for edge cases where interdependencies were not being sorted properly ahead of call.
  • Fix so that reading a branch works consistently for both _doc and alias values.
Domain Users
  • Fix so that shared assignment of an existing identity policy to a new user works as intended for cases where the source user does not have an assigned password.
GraphQL
  • Fix so that nested collections resolve properly for cases where related nodes exist on a parental or ancestral branch.
Transfer
  • Fix so that exports of multiple nodes complete as intended for edge case where export is performed in tip mode and includes one or more nodes that resolve from same changeset ID as final source item.
workflow
  • Fix to resolve permissions issue when launching workflows for certain users/roles within projects.









Get Started with Cloud CMS

It's Free to Sign Up. No Credit Card Required.