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

  • 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

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


Cloud CMS Release 3.2.58

Published on 08/06/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.58 release.

Update Recommendations (On-Premise Only)

  • 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

Authorities and Permissions
  • Faster invalidation of authority cache and permission cache when Grants and Revokes are performed.
Dictionary
  • Added safety checks to help ensure that definitions can only be created with correct JSON schema properties. Also added some permissive code to automatically migrate existing schemas during compilation for cases where definitions have illegal values.
Indexing
  • Faster indexing of MongoDB collections with optional background execution.
Logs
  • Simplified the Platform Logs and Project Logs pages to make them easier to use with fewer fields and faster results.
Notifications / Message Queue
  • You can now configure the host for UI Notification messages so as to support custom URLs and custom multi-tenancy deployments. For more information, see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#notifications-ui-server.
User Interface
  • Cleaned up the UI to make Vaults List and Jobs List pages simpler by removing checkboxes and Selected actions.
  • Node Picker now removes duplicate paths for cases where the r:root path is included in the result set.

Bug Fixes

Activities
  • Fix so that, by default, the Project and Platform Activities lists sort by Most Recent first.
Attachments
  • Fix so that bulk uploads performed with the UI work as intended and reflect their uploaded content thumbnails right away.
  • Fix so that the user interface refresh right away after attachments are Added and Removed.
Image Transformation
  • Fix for preview generation and image transformation of some Mime Types into image/jpeg where the alpha channel wasn't being properly converted and size 0 images were being produced.
Propagated Authorities
  • Fix so that propagated authorities work as intended for certain cases where custom association types (bearing the f:propagates-authority feature) are being used within chained relators across multiple levels.
  • Fix so that propagated authorities invalidate more efficiently.
Releases
  • Fix so that archiving an active Releases will automatically take you back to the Releases page.
Relator Properties
  • Fix so that relator property mappings are retained in cases where an update occurs and a value is concurrently removed and re-added such that mappings are preserved.
Tags
  • Fix so that tags shown on the Document Tags page or in the Document List now link to the Tag Overview page.
Web Hooks
  • Fix so that the web hook invocations bound to the "before node create" policy will invoke as intended (with null changeset ID and revision since those have not yet been assigned).


Cloud CMS Release 3.2.57

Published on 07/30/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.57 release.

Update Recommendations (On-Premise Only)

  • 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

Drivers

Enhancements

Node Policies and Events
  • Faster execution of the Node Policy system for faster event handler processing.
  • Optimized the specific execution of property-binding policies for significant performance boost.
Node API
  • Added asynchronous support for node updates for cases where long-running transactions might otherwise exceed a CDN or Proxy timeout. This allows Node updates to run via the distributed job queue (in the background). A job ID is handed back so that the client can poll for completion.
Property Mappings / Relator Properties
  • Optimize the execution of property mappings for updates of nodes by checking for false equivalencies in the JSON structures.
  • Added a traversal cache to reduce the number of mappings per sync.

Bug Fixes

Attachments
  • Fix so that Add Attachment modal works more intuitively, cleaning up a number of bugs and improving the flow.
Content Model Builder
  • Fix so that the array field preserves its items when the array ID is changed.
Inline Links
  • Fix so that some of the exception trapping and logging is relaxed for cases where relative URIs cannot resolve correctly during link generation.
References
  • Fix so that property definitions in a schema that utilize $ref bindings will represent properly within the UI for editing purposes.
Roles
  • Fix so that that Properties and Permissions pages are removed when navigating to a system-defined role.
Schema and Validation
  • Fix so that the JSON Schema Validator manages memory better by improving the way cache is managed.
  • Fix so that JSON Schema streaming manages memory better and runs faster with less logging.
Transactions
  • Fixed a bug whereby creating a child association in the same transaction as child object could misdetect the presence of an existing owned association.
Workflow
  • Fix so that the ability to show/hide only the tip workflow models is restored within the user interface.
  • Fix so that the workflow model's head flag is unset when a workflow model is undeployed.


Cloud CMS Release 3.2.56

Published on 07/20/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.56 release.

Update Recommendations (On-Premise Only)

  • 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

Localizers

  • Adjust the localization strategy that is used to resolve a localized piece of content for a requested master node and locale (example: en_UK). This allows customers to either select or implement the localization strategy that their business requires, allowing for desired fallback or graceful degradation selection. On-premise customers can build their own Localizers using custom Spring beans. For more information, see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#locale-resolution

Script URL Resolvers

  • You can now configure the base URL to be used by templates and the scripting engine when building incoming links that externally resolved. By default, this will fall back to https://{subdomain}.cloudcms.net. For more information, see: https://www.cloudcms.com/documentation/docker/configuration/api-server.html#script-resolvers

Enhancements

Attachments

  • Attachment information returned from the API now includes an ext field that indicates the filename extension that will be used if the file is ever written to disk or deployed to a deployment endpoint. For more information, see: https://www.cloudcms.com/documentation/attachments.html

Localization

  • The default localization strategy now gives preference to direct and wildcard matches for language over country (which is now considered last).

Login

  • Added UI Server configuration properties to more effectively manage limits around attempted logins. For more information, see: https://www.cloudcms.com/documentation/docker/configuration/ui-server.html#login-attempts

Property Mappings

  • Property Mappings now run within a single transaction so that any associated nodes with mapped properties commit along with the original node in one fell swoop, resulting in faster execution and smaller changeset counts.

Relator Properties

  • Relator properties execute their mappings within a single transaction, resulting in much faster performance and updates to all related nodes within a single transaction.

Translations

  • Translation Nodes now preserve attachments when auto-generated from master node via the API or user interface.
  • Refreshing a Translation Node will copy forward any Master Node attachments if no attachments are currently present on the Translation Node.

Bug Fixes

Branches

  • Fix so that processing of merge conflicts of type definitions work as intended for complex cases where inherited types may have been deleted or modified within the same transaction.

Cluster

  • Fix so that cluster initialization performs some additional safeguard checks to protect against concurrency issues that may occur when multiple servers haven't yet joined the cluster (known as a the "Split Brain" problem). A database journal is now maintained to track non-joined servers on startup and fail early.
  • Fix so that a force kill of a server in a cluster (that happens to be holding a branch lock on a committing transaction) cannot result in multiple tips being recorded (one active and one inactive). This yielded cases where some nodes might not write to the correct tip for a duration of time until the remaining server rebalance. A database journal now guards against this and inactive tips are cleaned up immediately.

Content Model

  • Fix for Content Model Form Builder so that Attachment Field and Content Field render as expected for nested cases.
  • Fix so that click handling within the Content Tree works properly and displays as produces consistent results between the tree and list views.

HTTP Range Header Support

  • Fix so that single range requests come back as non-multipart.
  • Fix so that range parsing supports open-ended start and finish markers (i.e. Range: bytes=-999 or Range: bytes=1000-).

Permissions

  • Fix so that node updates that fail due to insufficient permissions won't leave an intermittent cache in an incorrect state. This cache could leave the perception that the node had been updated so long as subsequent requests arrived to the same API server (via sticky session).

Transfer

  • Fix so that exporting a definition now automatically exports all parent definitions as well.
  • Fix so that relator properties are detected at export time and any nodeType or associationType definitions of those relator properties are exported as well.
  • Fix so that properties are scanned at export time and any schema-level referenced definitions (via $ref using the qname:// loader) are exported as well.

User Interface

  • Fix so that Deploy Nodes Strategy action shows the title in the form.
  • Fix so that the Add Publication State modal lets you select based on configured States.
  • Fix so that the Create Policy action will show association definitions in the definitions list when working with Association or Associated Node Policies.
  • Fix so that Jobs List search term produces more accurate results.
  • Fix so that the Attachment Picker maxFileSize setting excludes values less than zero.


Cloud CMS Release 3.2.55

Published on 07/01/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.55 release.

Update Recommendations (On-Premise Only)

  • 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

Data Export Wizard
  • When exporting ZIPs of content using the Export Wizard, any exported JSON is now prettified by default.
Indexing
  • Indexing of nodes for full-text search now always runs as a background job as opposed to running in-transaction. This speeds up write operations for the vast majority of cases. The makes full-text search indexing consistent across the board.
  • Indexing now optimized to run faster by delaying the indexing calls to the very end of multi-stage transactions. This results in fewer indexing calls and lower CPU usage for the system.
  • Improved usage of Elastic Search Bulk API so as to have fewer indexing background jobs and faster overall completion.
Login
  • The error messages and feedback provided to the user upon a failed login has been limited so as to be more secure and less descriptive of the underlying reasons why the login did not succeed.
MongoDB
  • Improved support for conversion of BSON V2 Types in MongoDB for cases where existing MongoDB 2.x or 3.x databases are migrated to newer versions of MongoDB.
Node Statistics
  • The accumulation and tracking of association type counters is now disabled by default. This provides a significant performance improvement for the vast majority of use cases where those counters are not required. This general association-type counter accumulation can be enabled using either a feature or a repository-level configuration option. For more information, see https://www.cloudcms.com/documentation/api/statistics.html.
Permissions
  • Added permissions for DEPLOY and UNDEPLOY that can be used to control the availability of those functions within the API and the user interface.
  • The Deploy Node Action now requires the current user to have the DEPLOY permission against the targeted content instance.
System
  • The metrics collections thread now includes disk usage information along with other healthcheck information in the periodic log.
  • Added a background thread that periodically cleans temp file space to facilitate the management of long-running pods or containers that may have otherwise relied on JVM shutdown hooks to clean up disk space.
Transfer
  • Tip-mode imports will now automatically execute any property mappings for any property mapping associations during the import. This makes sure that property mappings are established when the import completes.
  • Faster performance due to improved management of caches
Translation
  • The Azure Translator integration now supports very large text arrays by chunking text translations into multiple calls.
User Interface
  • The Content Instances page now has more actions available on it to make it consistent with the Document Library page.
  • Various improvements across the user interface to establish consistency between the number of selected items (0, 1, more than 1) and the available action set that can execute against that selection.
  • The Change Type Action modal now offers a checkbox to let you decide whether to show system content types.
  • The Attachment Picker now supports maxFileSize and fileTypes. For more information, see https://www.cloudcms.com/documentation/forms/fields/attachment-picker.html.
  • Added a success message that displays when a lock is successfully released.
Workflow
  • The Web Hook workflow handler now supports additional HTTP methods (GET, PUT, DELETE) along with POST which was already supported. For more information, see https://www.cloudcms.com/documentation/workflow/workflow-handlers/webhook.html.

Bug Fixes

Actions
  • Fix so that the Change Type renders properly for some cases where actions had missing properties.
Associations
  • Fix so that the proper error HTTP response is provided for cases where a failed attempt is made to manually associate a source and target node via the API.
Content Model Builder
  • Fix so that drag/drop works consistently across a wider variety of browsers along with improvements to Field Editor selection, support for nested fields within Array and Object containers and updated inspectors for editing field properties.
Dashboards
  • Fix so that drag/drop works consistently across a wider variety of browsers.
Email
  • Fix so that the case for email addresses is ignored when creating password reset requests.
  • Fix so that lower case email addresses are enforced more consistently within forms.
GraphQL
  • Fix so that GraphQL results no longer strip off null values for cases where they are regarded as legal values in GraphQL Schema.
  • Fix so that the UI display of HTML from within GraphQL results renders properly.
Indexing
  • Fix so that bulk indexing will complete successfully for cases where an encrypted PDF document might be inserted into the middle of a indexing chunk, causing that document's text transformation to fail and causing the remainder of the chunk to fail.
PDF Generation
  • Fix so that PDFs with embedded images generate properly when using a PDF generation template and referenced images from within Cloud CMS.
Print
  • Fix to Print and Print Preview within the user interface so that print dialog is compatible with a wider variety of browsers.
Releases / Branches
  • Fix so that Release or Branch creation and merging works properly for cases where a branch had a large number of changesets and no snapshot to support incremental diffs. In this case, a faulty snapshot was being generated and consistently had to be re-created.
  • Fix so that branch to branch copies work properly using MongoDB 3.6 and beyond bulk index calls.
  • Fix so that the Retry Merge button no longer appears while resolving merge conflicts between Releases.
Teams
  • Fix a bug so that team identifiers cannot overwrite when custom team properties are overwritten via API call.
  • Fix a security hole that, in some cases, permitted users without the UPDATE authority against a Team's underlying Domain Group to add or remove users from a team.
User Interface
  • Fix so that user default projects are automatically cleaned up when any kind of project is deleted (not just projects in the oneteam family).
  • Fix so that versioning diffs (JSON RFC 6902) are computed in the correct direction when visually selected for some cases.
  • Fix so that Dashlet default maximums are enforced.
  • Fix so that thumbnail and preview icons show up properly on the Attachments screen for cases where you have multiple attachments.
  • Fix so that Node Picker, File Picker and Upload controls support null or false for the uploadPath setting to indicate that uploaded nodes will not be linked to a folder.
  • Fix so that Release Finalization results don't show on the Release Overview page after a successful Release execution.
  • Fix so that the Project Publishing configuration pages show the correct listing of content types for cases where the content types had one or more missing values.
  • Fix so that PDF Preview works consistently across a wider variety of browsers.
  • Fix so that the Grant Authority action's "Unselect All" option work as intended.
  • Fix so that the Add Permission to Role action shows each permission's description.
  • Fix so that the Rule Actions editor's "Action Type" field is required.
  • Fix so that links to incorrect (or no longer valid) Project IDs or Branch IDs redirects as appropriate.
  • Fix so that username is forced to be lowercase on field entry.


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.

Update Recommendations (On-Premise Only)

  • 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

Logs
  • 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
Performance
  • Improved performance throughout due to optimizations to DB layer and service event handlers.
Releases / Branches
  • 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

Bug Fixes

  • 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
Logs
  • Fix so that project-level logs scope properly to just project-level exceptions
Memberships
  • Fix to principal memberships caching so that principal memberships reflect updated values when members are updated separately.
Pickers
  • Fix so that Picker Upload button preserves the selected entries when populating the list of selected nodes after upload
Property Mappings
  • 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.
Stream Handling
  • Fix so that stream handling to S3 is more efficient and populates range headers properly
Snapshots
  • 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.


Cloud CMS Release 3.2.53

Published on 05/21/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.53 release.

Update Recommendations (On-Premise Only)

  • 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

HTTP Range Headers
  • Added support for HTTP range headers to allow for multi-range, multipart downloads of partial content. This improves the ability of Cloud CMS to support large content and media formats (such as video and audio files) with improved operability with streaming services, players and edge caching facilities.

Enhancements

HTTP
  • Improvements to HTTP header management to incorporate more end-user friendly assumptions of header values
Localization
  • Improved the graceful degradation of locales when multilingual content is being localized using internationalization (I18N) translations. This makes the localization of content on the fly more accurate for cases where master nodes manage their locale codes individually.

Bug Fixes

Merge
  • Fix so that branch merge is more accurate for cases where large collections of node deletions are marged at once and there are interdependent owned relationships within the merge set
PDF Export Wizard
  • Fix so that selected PDF template validates upon submit properly
Permissions
  • Fix so that permissions cache invalidates immediately for propagated group memberships when a team is deleted
Transfer
  • Fix so that nodes collection markers are maintained properly after the transfer import of a node


Cloud CMS Release 3.2.52

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

Update Recommendations (On-Premise Only)

  • 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

Multi-Factor Authentication
  • Added new Docker-configurable Multi-Factor authenticators for Trusted Tokens (HTOP and TOTP). These are available for on-premise installations and allow for use for Google Authenticator and other 2FA token authenticators.

Enhancements

Administration Console
  • Unify the Administration Console login with that of the main UI so that they both use the same login screen and extensibility patterns (for whitelabeling logos and more). This further enables Multi-Factor authenticated access to the Administration Console.
Host Detection
  • Improved parsing of request headers to detect and handle some short-form hosts and IPV6 addresses more accurately
Performance
  • Improved performance and scalability due to faster and more efficiently invalidation of distributed Hazelcast caches

Bug Fixes

Associations
  • Fix so that Child and Owned associations are processed correctly on deletion to ensure that child associations clean up properly for cases where a node has an owned relationship from an owner node
  • Fix so that a:child and a:owned inherited association types are detected and handled correctly on deletion for additional cases
Content Types
  • Fix so that Content Types customized lists properly appear in certain places within the Manage Project > Publishing interface and other places within the user interface
Multi-Factor Authentication
  • Fix so that MFA challenges are disabled for some cases where they were errantly appearing due to a cache invalidation glitch
Tree
  • Fix so that duplicate tree entries do not appear on some refreshes


Cloud CMS Release 3.2.51

Published on 04/25/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.51 release.

Update Recommendations (On-Premise Only)

  • 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

Kubernetes
  • Added native support for Kubernetes API discovery. This allows Cloud CMS API servers running in a Kubernetes cluster to discover each other without any additional network configuration.
Multi Factor Authentication
  • Added support for second factor authentication using TOTP and HOTP codes with support for SHA, SHA256 and SHA512
  • Added support for trusted auth code issuances for protection of priviledged accounts (on-premise only) with pluggable notifiers for Email, Web Hooks and more

Enhancements

Auto Translation
  • Added the excludePaths setting to the f:auto-translate feature to allow content modelers to skip certain fields during automatic translation
Caching
  • Distributed caches now invalidate much more efficiently by using predicates for key discovery and removal
Graph QL
  • Added the ability for the nested relator content to be exposed via the GraphQL API
Teams
  • Teams now support custom properties when being created or updated via the Teams API
Tenant Invalidation
  • Added separate tenant invalidation messages to notify user interface tier of pre-emptive cache invalidation ahead of tenant creation
Versions
  • Faster query and pagination through versions including introduction of from based pagination via the API
  • Versions API now optionally hands back differences information on the API call for each row in the result set
Views
  • Added progress tracking for Branch Tip View rebuilding

Bug Fixes

Attachments
  • Fix so that the attachment event handler methods always process correctly after the first create or update invocation for all cases. This resulted in situations for the end users where _attachment properties might only end up having their id field filled out on document create
Branches
  • Fix so that the Branch API's Tree list method (which delivers a flat representation of the branch tree) always come back in a consistent and correct order
Identities
  • Fix so that deletion of a domain or a principal will always result in the association of a principal's identity to a directory identity policy. There were cases discovered where this did not occur
Releases
  • Fix so that release limits are calculated only against active releases (and not all releases)
User Interface
  • Fix so that the Locale Filter works correctly for the Add Translation action via the UI
  • Fix so that the Content Type Picker correcftly shows system content types when nothing in configured on the UI Content Types page
Workflows
  • Fix so that project-scoped workflow elements (workflow instances, tasks, etc) are always cleaned up from the global context when a project is deleted.


Cloud CMS Release 3.2.50

Published on 03/16/2020
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.50 release.

Update Recommendations (On-Premise Only)

  • 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

API Keys
  • For on-premise installations, the org.gitana.platform.services.apikeys.defaultBaseURL property can be configured for API containers to configure the baseURL that API Keys will use (the default is https://api.cloudcms.com)
Relators
  • Improved performance of relators properties and relator associations on save including optimizations to remapping logic
Transfer
  • Improved performance with more efficient use of paginated iterators
  • Inline Link associations (a:links-to) and Linked Resources (n:linked-resource) are now traversed and included when exporting nodes
Undeletes
  • When undeleting nodes, the child associations that once related that node into the folder hierarchy are also restored provided that the parent node exists
User Interface
  • Remove limit on the number of Project templates made available for selection
Versions
  • Faster list and query retrieval of node version history using less memory and optimized indexes

Bug Fixes

Transfer
  • Fix so that domain users transfer correctly for cases where the domain itself may not be included and may be optional
  • Fix for an error that could occur when a user was being added to a team on import (and the user was already a member of the team)
  • Fix for a concurrent modification exception that could occur when optional dependencies were removed in partial imports
  • Fix for a case the f:inline-links feature prevented nodes from auto-publishing when f:publishable lifecycle state was set upon creation
User Interface
  • Fix so that Content Type dropdown used in the Create Document wizard only shows enabled types
  • The "Rules" folder now hides along with other system folders when the Hide System Folders option is selected
  • Dashlets now only show branch information is either Workspaces or Releases are enabled within a Project









Get Started with Cloud CMS

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