Cloud CMS Release 3.2.54

Published on 05/27/2020

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

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 (https://gitana.io/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.

Logs now include additional stack trace information if available
Improved formatting of downloaded log files to include additional stack information, more detail and a greater default length

Improved performance throughout due to optimizations to DB layer and service event handlers.

Release finalization now performs a dry commit merge to allow for early detection and resolution of schema-related merge issues.
Release finalization errors are now reported on the Release overview page. Previously, these were detected during release execution (instead of finalization) and could only be inspected via logs.
Releases now include additional flags to track finalization results as well as execution stage errors.
Release and Workspace Content and Activities pages now show more information about content changes including property level differences

Fix so that deleting a workspace or a release redirects away to the listing page for the case that the user currently has that workspace or release selected

Fix to principal memberships caching so that principal memberships reflect updated values when members are updated separately.

Fix so that Picker Upload button preserves the selected entries when populating the list of selected nodes after upload

Property mappings now execute much faster and in linear time (impact cases where a large number of mapping associations exist in the graph). This impacts customers who might have otherwise seen occasional 504 timeouts on update.

Fix so that stream handling to S3 is more efficient and populates range headers properly

Fix so that snapshots are built properly for cases where snapshots are auto-generated and the changeset history is excessively large. This addresses performance as well as a bug with Releases being created and reflecting incorrect content.

Ready to Get Started?