Cloud CMS Release 3.2.66

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

Attachments
  • Attachment policies now support binding to a specific attachment ID. If an attachment ID isn’t specified, attachment policies continue to work as before and will trigger for all attachments.
  • Preview attachments are now filtered out and do not trigger attachment policy events.
Branches / Merge

Command Line Client

  • Added commands for working with domains and principals. These include list-domains, list-group-members, list-memberships, list-principals, query-principals and read-principal.
  • Added a flag to allow for the configuration of repair-branch operations (--operations).
Distributed Job Queue
  • Adjusted the default job configuration for a few core jobs (including export and import) to improve durability of those jobs during transfer, copy, publishing and deployment. This allows those jobs to retry automatically without any additional configuration.
  • Improvements to performance and state management.
GraphQL
  • Broader support for thirdparty GraphQL client libraries with improved and lenient handling of non-standard Content-Type headers.
Logging
  • The user interface now shows project information alongside log entries rows when viewed at the Platform level.
Transfer
  • Improved performance and resource management resulting in faster and more efficient exports, imports and any dependent operations (copy, deploy and publish).

Bug Fixes

Distributed Job Queue
  • Fix so that a job kill operation will more accurately locate and interrupt a running thread anywhere in the cluster.
File Folders
  • Fix so that path lookups use encoded paths to account for cases where paths with special characters were not being found.
  • Fix so that the file folder index refreshes properly whenever the f:container feature is added or removed.
GraphQL
  • Fix so that top-level GraphQL relator data returns in the correct order.
  • Fix so that multilevel deep relator attachment metadata fetches correctly.
  • Fix so that querying of attachment metadata works as intended.
Logging
  • Fix so that all jobs executing for resources on a stack will properly track the stack ID, allowing tenant log entries to be viewed within the Project Log viewer. This addresses a regression that was introduced when using asynchronous loggers.
Schema
  • Fix so that automatic migration of required boolean properties only runs for legacy JSON Schema v3.
Temporary Files
  • Fix so that temporary files on disk are more actively cleaned up on background thread.
Transactions
  • Fix so that nested transactions broadly support independent, inner transactions against different branches, allowing both pause and propagation transaction behaviors. This both enhances performance and fixes a few subtle bugs for cases such as a merge, where a source branch transaction may trigger events that spawn new transactions on the target branch. Customers had observed inconsistencies with target branch behaviors (such as rules) on the target branch – these should now be resolved.
Transfer
  • Fix so that project exports with optional team members exports will properly import into a target platform without any duplication of principals.
  • Fix so that file path index is properly refreshed after a project or branch import for all cases.
User Interface
  • Fix so that modal pickers work for some cases where the context was being improperly initialized.
  • Fix so that content types always appear on left-hand menu after an import.









Get Started with Cloud CMS

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