Releases

The Cloud CMS product suite is available to subscription customers for installation on-premise or within your own virtual private cloud. The product suite is delivered as a series of Docker images along with sample installation scripts to help you get running.

Cloud CMS runs on any Docker host including Amazon AWS (via Cloud Formation templates, Amazon Elastic Container Service, Amazon Elastic Beanstalk or the Docker AWS Engine), IBM BlueMix, RackSpace, Digital Ocean and many others.

The download consists of a ZIP with sample configuration files to launch the complete Cloud CMS stack in variety of configurations including development, standalone and clustered. The sample configuration files are provided using Docker Compose.

To run Cloud CMS on-premise, you need to be a Cloud CMS subscriber.
Contact Cloud CMS to purchase a license or request an on-premise trial.

Subscribe to our Mailing List

We'll send you notifications when new product releases and new features are made available.



Cloud CMS Release 3.2.67

Published on 05/24/2021
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.


Cloud CMS Release 3.2.66

Published on 04/22/2021
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.


Cloud CMS Release 3.2.65

Published on 03/15/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.65 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

Branches / Snapshots
  • Added an API method to support creation of snapshots asynchronously (using job polling). This is now used by the Cloud CMS command line client.
Logging
Transfer
  • Faster transfer exports that are more efficient and use less memory. This is notable for copy, move, publish and deploy operations for a large number of nodes or objects.
Search
  • Inspection of search indexes with REST API now includes ES mappings information.
User Interface
  • Simplified the Project Export wizard so that it performs compressed exports of the master branch. To export multiple branches or run without compression, please use the command line, API or drivers.

Bug Fixes

AWS CloudWatch
  • Fix so that the AWS CloudWatch Appender handles cases where log event messages are filtered out ahead of being invoked (which could result in empty messages).
Branches
  • Fix so that MongoDB branch-level collections are always cleaned up properly for cases where a failure occurs during branch creation.
GraphQL
  • Fix so that GraphQL queries are entirely isolated from node caches so as to prevent issues when querying nodes.
Merge
  • Fix so that merges of branches works as intended when operating within older, legacy repositories.
Node
  • Fix so that nodes read properly by considering case insensitivty when using a projections to tokenize the path.
Search
  • Fix to search type filtering so that the __type property can be search as intended.
Transfer
  • Fix so that imported Node attachments are automatically indexed into Elastic Search upon for all cases.
User Interface
  • Fix so that unlocking the attempted login lock is picked up immediately by the user interface. This allows unlocked users to retry their login right away.
  • Fix so that the Delete Project User action checks permissions against the project, allowing Project Managers to remove users from a project.
  • Fix so that Attachment Pickers validate extensions (if so configured) for existing attachments.
  • Fix so that the “required” property is handled properly for some nested cases.


Cloud CMS Release 3.2.64

Published on 02/11/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.64 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

Multitenancy
  • Improved the multipart resolver so that it supports per-tenant file upload options with global setting fallback.
GraphQL
  • Ensure that both incoming and outgoing property names that flow through the property data fetcher are SDL encoded. This allows property names, such as my:thing, to be queryable using the value my_thing.
User Interface
  • Adjust the pre-delete warning modal to distinguish between nodes that will be deleted and those that will be affected.

Bugs

Deletions
  • Fix so that restoration of deleted nodes preserves original property values for cases when an overlay set of properties are provided.
Actions
  • Fix so that the Move Node action (for both single and multiple sets of nodes) properly calculates the incoming associations, solving for cases where moved nodes wouldn’t appear to move in the content graph.
Search
  • Fix so that older ES Search DSL blocks are parsed and automatically handled, improving on situations where some customers with older ES search blocks might have seen inaccurate results.
Projects
  • Fix so that projects that fail to create can be more easily cleaned up – by allowing the UI to load up even if the project stack is missing.
Tags
  • Fix so that documents created with inline tags are indexed straight away and are discoverable by searches against their tag values.
Transaction
  • Fix so that multi-node transactions now correctly identify their prior value when calculating the diff that informs the ES index. This results in more meaningful and correct deltas being bulk written into the ES index.
SSO
  • Fix so that verification of assertions using a custom digital certificate are picked up immediately upon save.
User Interface
  • Fix so that the Related Content button works as intended when used in an array (with an index as a portion of the label).


Cloud CMS Release 3.2.63

Published on 01/14/2021
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.63 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

Branches / Releases
  • Faster merges with improved transaction ordering for more accuracy when working with complex graph structures.

Bug Fixes

Search
  • Fix so that pagination sorting works as intended when using some _system inner fields.
Branch Merge
  • Fix so that merges work properly for cases where owned associations are being merged with automatic conflict resolution enabled.


Cloud CMS Release 3.2.61a

Published on 12/21/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.61a 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.

New Features

The following features have been backported from 3.2.62 to 3.2.61a:

Command Line Interface
  • The CLI now supports transfer commands to enable developers or administrators to script the import and export of projects, repositories, branches, nodes and more.
  • Now supports Node 15.x and beyond.
Supported Stacks
  • Added support for MongoDB 4.0.21
  • Added support for Elastic Search 6.8 and 7.9
  • Added support for AWS ElasticSearch 6.8 and 7.9


Cloud CMS Release 3.2.62

Published on 12/17/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.62 release.

Update Recommendations (On-Premise Only)

With version 3.2.61 and beyond, 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.

New Features

Command Line Interface
  • The CLI now supports transfer commands to enable developers or administrators to script the import and export of projects, repositories, branches, nodes and more.
  • Now supports Node 15.x and beyond.
Supported Stacks
  • Added support for MongoDB 4.0.21
  • Added support for Elastic Search 6.8 and 7.9
  • Added support for AWS ElasticSearch 6.8 and 7.9

Enhancements

Headers
  • Added a x-cloudcms-api-execution-branch-lock-wait-time-ms response header that records the amount of time (in milliseconds) that the request waited for a branch-scope write lock (if applicable). This value is useful when measuring net throughput of concurrent write API calls.
GraphQL
  • Improved performance of GraphQL collection queries by optimizing traversal of relator properties.
Path indexing
  • Newly created repositories now have URI encoding enabled by default so that any branch-level path indexes with use URI encoding right away.
Publishing
  • When running a resync of published nodes, a background job is now launched allowing long running publications to execute and be polled for completion.

Bug Fixes

AWS CloudWatch
  • Fix so that the AWS CloudWatch Log4j2 Appender submits entries in the proper atomic order when running in a cluster.
Forms
  • Fix so that circular references are detected more quickly and more accurately for certain conditions.
  • Fix so that $ref properties are no longer traversed for cases where they are empty or have null data.
  • Fix so that form options optimization allows for soft failures for cases where form references are missing.
GraphQL
  • Fix so that a recursive condition is avoided which could cause the retrieval of associated nodes to time out.
Merge
  • Fix so that merges work properly in cases where one or more node’s changeset histories may offer circularly recursive lineages back to the ancestral node.
Publishing
  • Fix so that imported content items with relator properties correctly refreshes in the completion phase of the import.
Relator Properties
  • Fix so that updates to relator properties of type array will make the correct set of delta adjustments so as not to leave stray or excess associations in the graph.
Rules
  • Fix so that property conditions properly check for nested path keys (as opposed to just top level property names)
  • Fix so that compound conditions render and are editable within the UI as expected.
Search
  • Fix so that bulk indexing exceptions are parsed with greater leniency so as to inform parent job of error messages.
Transfer
  • Fix so that imported content will properly have its attachments populated for specific cases where relator properties are refreshed after import.
  • Fix so that an export of node list items will additionally include any a:has-item associations as optional.


Cloud CMS Release 3.2.61

Published on 11/11/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.61 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

Branches
  • All Branch maintenance commands have been enhanced and improved to work more seamlessly with the user interface and command line tools. These include jobs and workers to manage search indexes, path indexes, rebuild views and recreate filenames.
  • Improved the resiliency and runtime performance of the recreate filenames worker.
Cluster Management
  • Added services and API methods to let administrators retrieve cluster-wide configuration settings, diagnostics and properties settings as well as monitor job queue and report on job statistics.
Command Line Client
  • Added support for multiple profiles to let you execute commands against multiple Cloud CMS environments more easily. Use the --profile <profile> switch to select and manage your profiles.
  • New command to find deployment records for a given node.
  • New commands to retrieve platform and project level log files.
  • New commands to inspect the job queue and query/read individual jobs.
  • New command to re-sync publishing state to let you republish a bulk set of nodes to a deployment target.
  • New commands for on-premise administrators to retrieve and inspect cluster health and state.
  • Improved support for multi-factor authentication code usage when initializing and executing administrative commands.
  • Added support for --ids switch to allow any result map response to hand back an array of row IDs.
  • New commands to manage and administer branches including dropping and recreating search indexes with zero downtime, dropping and creating path indexes, rebuilding views and recreating filenames.
  • New commands for working with projects and file systems.
Forms
  • Improvements to support for $ref bearing definitions and forms for validation and rendering.
  • When Forms render, schema and form options have references expanded on the fly for faster performance.
Jobs / Workers
  • Improvements to scheduling and error capture of jobs in the job queue.
  • Enabled the Job Reaper by run by default and to be more aggressive in cleaning up old jobs.
Mail
  • Support for TLS 1.2 when sending and receiving mail via an Email Provider.
Performance
  • Optimized code paths throughout the API to make better use of streaming and transaction handling.
  • Faster and leaner execution with a much lower memory footprint.
  • Improved performance with smaller transaction sizes when moving nodes within the same branch or between branches.
  • Improved performance of /find API calls for cases where a query or a search are not provided
Publishing
  • Added a /publishing/resync API call that allows developers to modify lifecycle state and bulk publish nodes in one fell swoop.
Scripts
Search / Indexing
  • Faster and more efficient indexing and searching using optimized HTTP driver.
  • Elastic Search branch indexes now recreate much more efficiently and with zero downtime. The new index is prepared in the background and then swapped in with no downtime for live searches.
  • Better error handling so that indexing errors propagate up to parent job and are immediately available from the Branch Administration page. This helps you to discover nodes that failed to index due to schema issues or other factors.
  • Improved support for diacritic characters with automatic ASCII folding (so that a search for, say, Z├╝rich and Zurich will come back with the same results). For more information, see https://www.cloudcms.com/documentation/search.html#diacritic-characters.
  • Improved support for escaping of special characters (as defined by Elastic Search). For more details, please see: https://www.cloudcms.com/documentation/search.html#special--escapable-characters.
  • Initial support for custom analyzers to allow for variations in how text is analyzed and returned at both index and search time.
Transfer / Export
  • Additional support for new export options (optionalAssociationsExcludeTypes and optionalAssociationsMaxDepth) that allow callers to limit and control how the crawl of optional associations is performed.
User Interface
  • Module Deployment is now faster and more resilent and allows for full configuration of an S3 backup store for replicated faulting to new UI server pods as they come online. This works consistently for module code, configuration and templates.
  • The user interface now shows more information about rules configured globally or for a single document. This information now includes greater detail regarding the policy binding and more detailed summary of the conditions and actions configured for the rule.
  • All branch-level maintenance commands have now been moved from the Tools page to the Branch Administration page. This includes recreating branch search indexes, recreating path indexes, rebuilding branch views and recreating filenames.
  • The Branch Administration page now shows indicators to reflect the state of search and path indexes. That way, managers can quickly tell the state of an index and manage it more effectively.

Bug Fixes

AWS / Cloud Watch
  • Fix to the AWS CloudWatch Appender to make sure that items are ordered as expected for all cases.
AWS / S3 Storage
  • Fix so that writes into S3 utilized predefined chunk sizes so that very large files can write without issue.
Content Streaming
  • Fix to a off-by-one issue that could occur for some binary storage implementations when streaming partial content using the content-range header.
Node Service
  • Fix so that transfer service and other services that retrieve nodes by changeset are guaranteed not to get results for the wrong changeset.
Paths
  • Fix to the encoding of paths when producing concatenated child paths.
Projects
  • Fix so that projects automatically clean up for additional cases where an error may occur during Project Import.
Property Mappings
  • Fix so that deleted nodes in the same transaction are taken into account when asserting no duplicate property mapping associations.
Search/Indexing
  • Fix so that content encoding variances on incoming request are handled correctly and UTF-8 character conversion is guaranteed ahead of indexing and search calls into ES.
Transfer
  • Fix so that the partial import of branches automatically resolves any missing parental changesets on write.
  • Fix so that JSON Schema array items schemas that use $ref will be properly detected and have those definitions included in the export set.
  • Fix so that any discovered $ref QName loaders will properly parse for string formats that may include an improperly formatted hash suffix.
Tree
  • Fix so that paths are properly constructed when building out the tree response for cases involving some special characters.
User Interface
  • Fix so that UI gracefully handles the recovery of improperly formatted or munged session cookies.
  • Fix so that the cloudcms-link and cloudcms-image plugins for CKEditor will properly hide the upload button and allow you to disable the uploading of new nodes.
  • Fix so that the Delete Workspace button doesn’t appear for the master branch (it was always blocked within the API but the UI left the impression it could be deleted).
  • Fix so that real-time UI cache invalidation works for some on-premise cases where the incorrect hostname was being placed into the notification message.
Web Hooks
  • Fix so that the proper response payload MIME type is captured and retained on completion.


Cloud CMS Release 3.2.60

Published on 10/02/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.60 release.

Update Recommendations (On-Premise Only)

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
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
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.


Cloud CMS Release 3.2.59

Published on 09/13/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.59 release.

Update Recommendations (On-Premise Only)

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

Branch Merge
  • Improvements to performance for branch merging and merge conflict resolution/commit.
Elastic Search
  • Improvements to the efficiency and performance of indexing and search for documents when using the ‘condor’ HTTP client.
Email
  • Improvements to the Send Email Action to make it a bit easier to use. For more information, see https://www.cloudcms.com/documentation/actions/send-email.html.
  • Email Providers now allow for attachments to be accessed using both the attachments and _attachments model variables (to be consistent with Send Email action).
File, Folders and Paths
  • Improved support for default URI-encoding of paths including better handling of special characters and complex character sets.
Logging
  • Reduced the amount of logging incurred when a write is attempted against a Branch that is either frozen or blocked for write (such as when Releases block writes to Master).
Module Deployment
  • The deployment of custom UI components to the UI cluster now supports pre-emptive S3 fallback. This allows for new UI servers to be brought online dynamically with automatic pull-down of deployed customizations. This simplifies deployment of UI servers within frameworks like Kubernets and eliminates the need to use persistent volume claims. Administrators can now opt to use straight up EBS volumes or shared volumes (such as NFS or EFS).
Node Comments
  • The Delete Comments action now shows the date/time the comment was last edited and who last edited it.
  • The Comments List now only shows changes made explicitly by editorial users.
Permissions
  • Faster performance of invalidation logic for Authority and Permission caches, greatly speeding up the time it takes to grants or revokes for cases where the Principal involved has a large set of memberships.
Relator Properties
  • A “Refresh Node” action will now clean up and repair nodes with relator properties for cases where those nodes may have relator associations whose target node does not exist.
User Interface
  • The Document Overview page now hides attachments whose ID’s start with _original_ since those are considered internally-managed attachments.
  • The Document Attachments page now shows formatted file sizes instead of the length in bytes.
  • Removed the ability to configure the default sort field across an entire project (within Manage Project).
  • Added support for specifying Alt Text and image Width and Height settings via the cloudcms-image CKEditor plugin.

Bug Fixes

Copy
  • Fix so that relator associations are only auto-traversed for branch-to-branch copies or deployments. The copying of a node within the same branch will leave relator association auto-traversal off.
Elastic Search
  • Fixes for a few cases where UTF-8 encoding wasn’t being handled properly when indexing documents using the ‘condor’ HTTP client.
Node Locks
  • Fix so that the f:locked feature is removed on export of Nodes when using tip mode.
  • Fix so that Unlocking a Node now cleans up any stray a:has_lock associations that might be in place.
Transactions
  • Fix so that changeset creation provides some better guards against failed changeset creation to cover a rare case where a cluster’s distributed cache eventing could get out-of-sync.
  • Fix so as to protect against nodes being created with system-managed and unallowed QNames.
User Interface
  • Fix so that Project Titles now HTML escape properly on the Dashboard page.
  • Fix so that the Delete Documents Action only shows deleted Nodes (and not associations) when asking for confirmation.
  • Fix so that password regex allows for valid - character.
  • Fix to Form radio button support for boolean schema type.









Get Started with Cloud CMS

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