Cloud CMS Release 3.2.68

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.68 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://gitana.io/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 (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.

Enhancements

Application Server

• Added support for the GITANA_PROXY_PATH environment variable. This can be used to fine tune the proxied routing of API requests through an endpoint at a specific path. This also enables integration with API monitoring and optimization tools such as IBM API Connect.

Binary Storage Providers

• Binary Storage Providers now automatically cap file store caches to 64GB. They are now also configurable to allow for custom TTLs and cleanup configuration. This provides administrators with more tools to help manage disk space. This particularly helps when running in Kubernetes where the amount of ephemeral or local disk often needs to be more finely tuned. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#managing-disk-space.
• Improved the file binary storage provider so that it cleanly separates files into data and metadata directories for better performance and consistency.

Branch Views

• Improved the speed of building branch tip views by introducing a new index and faster, less frequent DB queries.

Command Line Client

• Added the import-platform-datastore command to assist with migrating datastores between on-premise Docker installations.
• Added support for optional vaults when working with archives.
• Improved support for start/end dates when specifying content export ranges.

GraphQL

• Improved GraphQL support for the Cloud CMS Java Driver. For more information, see: https://gitana.io/java.html.
• Added GraphQL support to the Cloud CMS Python Driver. For more information, see: https://gitana.io/python.html.
• Added GraphQL support to the Cloud CMS C# Driver. For more information, see: https://gitana.io/csharp.html.

Merges / Differencing

• Improved speed, efficiency and accuracy of branch merges by optimizing the algorithm responsible for computing the graph edge length between merge points of nodes from the tip back to a common ancestor across two branches.

Transfer (Import/Export)

• Improved the speed of the transfer imports by using less DB queries and less memory.

User Interface

• When copying a node between branches, all node associations are automatically considered allowing for more accurate copy results.

Web Hooks

• Standardized the way that Web Hooks are invoked so that Web Hooks invoked from within Workflow Handlers support all the same features including specification of headers, digital signature and more.
• Added projectId field to capture the ID of the project against whose content the web hook was invoked.

Bug Fixes

Attachments

• Fix so that deleting nodes with attachments doesn’t errantly cause additional or unexpected downstream propagated update events.

Branch Changes

• Fix so that Branch Changes more accurately keep up with branch deletion events.

Branch Views

• Fix so that branches whose views failed to build cannot be written to or transacted against.

Content Range HTTP Headers

• Fix so that Content Range support works for ranges that exceed the maximum length by auto-restricting the length to the resource length (improving conformance with RFC-7233). This improves support for Amazon CloudFront and other CDNs that deliberately push the length header out on a first call so as to remove the need for an initial call to retrieve full length.

GraphQL

• Fix so that GraphQL properly reflects required and nullable attributes for content properties that are marked required in their schema.

Localization

• Fix so that the default localization strategy considers the locale of the master node in its search algorithm. This allows the master node to play a part (along with any translation nodes) when localizing content.

Logging

• Fix so that the log system does a better job of capturing and reporting project, tenant and user context

Projects

• Fix so that project title uniqueness is enforced properly across all entry points (including some API methods that were incorrectly allowing this).
• Fix so that project titles (and other properties) are applied to projects at create time (instead of updated after create) to prevent duplicate project titles from appearing.

Relator Properties

• Fix so that a refresh() operation against a node with Relator Properties will correctly rebuild any relator properties and associations that originate on different node property (and which point either to or from the node being refreshed, depending on the mapping direction).

Releases

• Fix so that failures on Release Creation now log with project context
• Fix so that Releases are no longer exported when exporting a branch or project in tip mode.

Sync Nodes / Copy Nodes

• Fix so that the Sync Nodes action blocks on a frozen target branch (such as a locked master branch). Use the allowWriteToFrozenBranches setting to indicate that you want the Sync Node action to write regardless onto a frozen target branch.
• Fix so that translations of a master node are considered as candidates for reconnection when a master node is copied or synced between branches.

Transfer (Import/Export)

• Fix so that the product works around a bug in the JVM to allow for more efficient extraction from and storage within ZIP files.
• Fix so that the Store close() method isn’t errantly called twice for cases where you have nested archives.
• Fix so that exports of branches with ancestral branches that are archived will work as intended.
• Fix so that recursively referenced node properties are not traversed twice during compile phase.

Tree

• Fix so that changing node container states more accurately reflects in the tree (by updating file/folder indexes)

User Interface

• Fix so that the document image editor properly centers when cropping.
• Fix so that attachment markers are correctly removed from an attachment property when the property is cleared.
• Fix so that required fields work properly between builder and JSON views.

Workflow

• Fix so that adding or removing resources from a payload container works for general users as expected.