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

Published on 01/20/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.22 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Added support for Attachment Properties (using the "_attachment" setting on schema properties) which automatically sync with node attachments to store attachment properties into the JSON (such as content length, content type and more). This makes it much easier for content editors to upload and manage attachments directly from the content entry form, reducing steps and the number of clicks.
  • Added the ability to create projects from archives located at URL addresses, allowing customers to maintain their own registries of project archives (templates). Use the "projectType" attribute of a project to point to the desired URL.
  • Added the ability to create projects from named templates (these reference a Cloud CMS maintained registry of project archives). Use the "projectType" attribute of a project to indicate the template.
  • Optimized the packaging of deployments on deployment, reducing the record collection size for faster packaging and better throughput.
  • Fixed a bug so that File Folder Service tree results come back with consistent default sorting (alphanumerical).
  • Fixed a bug that cause some project create calls to fail due to incorrectly wired teamable hierarchies (referencing legacy data store types).
  • Better handling for preview generation of large TIFF files.

Cloud CMS User Interface Server

  • Added support for Attachment Properties which render as Attachment Pickers in forms -- letting editors upload attachments directly from within the form. Use the "_attachment" setting on a property to control how uploaded binaries bind to attachments.
  • Added drag-and-drop support for Attachments to the Content Model builder so that you designers can easily bind and configure Attachment fields.
  • Fixed a bug where the Document Tree wouldn't always refresh after content in a folder was created, updated or deleted.
  • Adjusted the default transport polling configuration for awareness service so that "websocket" connections are attempted first (ahead of long-polling) to allow compatibility with Amazon ALB.

Cloud CMS Command Line Client

  • Added the ability to create projects from the command line with support for project archive URLs and templates, letting you instantiate projects for testing, deployment and other purposes from within scripts and tooling.


Cloud CMS Release 3.2.21

Published on 01/14/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.21 release.

Cloud CMS API

  • Fixed a bug in the Tree and File Folder API where some sub-objects were not being prefixed properly on lookup and could appear in the wrong place.
  • Faster performance due to improvements in how branch collections are managed during nested transactions.
  • Improvements to clustering support for highly concurrent jobs (such as during publishing) - job queue is now more efficient and uses some improved locking to result in optimized performance across the cluster
  • Reduced the size of the transaction payload during node transfer, resulting in faster export and import times when deployment content between branches
  • Updates to copyrights, splash screens and other visual elements for notices and year

Cloud CMS User Interface Server

  • Improvement to the "Create New Folder" action so that optional selection of a folder type is hidden unless selected + drop down shows all content types by default
  • Allow for customization of content types for "Create New Folder" action via configuration service
  • Forms engine now makes automatic use of DataLoader pattern for more cases, resulting in faster rendering times. DataLoader bulks the reads for items into a single API query.
  • Faster performance for common picker fields (such as Related Content, Node Picker and File Picker) for cases where those fields are bound to Arrays or long lists of selected items.
  • Fixed a bug with the Related Content field so that it behaves properly when an upload fails. The "Select from Existing Files" button now properly tracks its selection state in accordance with the "maxNumberOfFiles" setting.

Cloud CMS Application Server

  • Fixed a bug that had prevented proxying to HTTPS from a non-secure incoming request for some cases


Cloud CMS Release 3.2.20

Published on 12/31/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.20 release.

Happy New Year! We present you with the 3.2.20 release just in time to close out the old year and bring in the new. Stay tuned for many more exciting features in 2019! We wish you and your loved ones a safe and happy holiday.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Improvements to OAuth 2.0 Authorization Code flow - now supports custom login URL and customizable Authorize and Access Confirmation pages, improvements to token management
  • Removed legacy support for OAuth 2.0 Implicit and Credentials Grant Types due to evolving OAuth 2.0 specification and security analysis. Going forward, the focus will be on Resource Password and Authorization Code flows with an emphasis on the strong security concepts they promote.
  • Fix to ensure that the optional Refresh Token can optionally be included in JWT payload
  • Fix to support locale strings that have a dash separator ("-") in them and the dash follows lower case characters. These can now be added as a translation.

Cloud CMS User Interface Server

  • Optimized the build process to produce smaller minified files and a faster user interface
  • Updated the Administration Console pages for Clients and Authentication Grants to emphasize the Authorization Code and Resource Password Grant Types for OAuth 2.0
  • Added support to Service Descriptor wizard for AWS Elastic Transcoder, AWS Polly, AWS Transcribe and AWS Comprehend
  • The "Cloud CMS Link" plugin for CKEditor now allows for selection of text from underlying DOM that is malformed or otherwise unparseable
  • Improved error message handling so that it relays Job log entries back to the user on the modal popup
  • Uploading a document through the UI now allows you to optionally delete an existing file if one is found
  • Improvements to Create Content wizard for cases where there is only one registered form so that the wizard flow is simplified and easier to use
  • Documents now retain form information allowing for the same form to be selected and re-used on subsequent edits
  • Enhanced the error messages displayed when sign on attempts fail with the wrong username or password
  • Updates to third party libraries


Cloud CMS Release 3.2.19

Published on 12/20/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.19 release.

Happy Holidays! We've pushed an early 3.2.19 release with a few important updates just in time for Santa's arrival. A big thank you and a warm Feliz Navidad to everyone in the Cloud CMS family!

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Upgraded PDF Box to latest version
  • Fixed a bug in the distributed job queue that allows cluster-wide, high concurrency jobs to process more efficiently
  • Reduced logging and improved error handling throughout the deployment code
  • Ensure that all deployment records for a deployment package fail if even a single record fails
  • Added a configurable job "reaper" thread that runs in background and truncates the total number of completed jobs retained in the jobs collection to help reduce DB size for large environments (disabled by default)

Cloud CMS User Interface Server

  • The Create Content wizard now skips the form selection step if there is only 1 form available (or if a default, system-generated form is being used). This fixes a "back-button" issue within the wizard.


Cloud CMS Release 3.2.18

Published on 12/18/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.18 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Enhanced support for Amazon Comprehend - natural language processing (NLP) service that uses machine learning to find insights and relationships in text. New features include f:aws-entities and f:aws-keyphrases to automatically support the detection of textual entities and key phrases when content is edited within Cloud CMS.
  • Added support for Amazon Polly - a text-to-speech service that turns text into lifelike speech, allowing editorial content to automatically translate into audio files (as attachments within content). The f:aws-polly feature empowers content to generate audio files in multiple languages and dialects, including English, Chinese, Spanish and many more.
  • Improved support for Amazon Transcode - a cloud-based service for automatically transcoding attachments or URL-described resources to target formats for playback on devices like smartphones, tablets and PCs. This has been refactored to be more efficient and to utilize the benefits of our distributed job queue. The f:aws-transcode feature can be tagged onto a content type to have transcoding automatically occur in the background.
  • Improvement to thumbnail generation so that generation is skipped if a suitable transformer between a source attachment and target mimetype cannot be determined. The previous behavior was such that generation continued but used the JSON of the node as the source which could lead to thumbnails being generated but with the wrong source (and no means for detecting the anomaly).
  • GraphQL now has improved support for nested arrays with scalar (non-object, non-relational) elements
  • Fixed a bug with the Rendition Service where connected renditions could introduce a lock state and cause a transaction to time out
  • Fixed a bug in the Distributed Job Queue's dispatcher thread so that awaiting jobs are processed more accurately by accounting for cases where stopped times are not yet recorded
  • Improvements to relator synchronization logic so that updates to nodes that have a large number of relators will be noticeably quicker
  • Improvements to Deployment Engine and efficiencies for high concurrency and accurate book keeping of concurrent jobs back to deployment records and supporting transfer archives
  • Some internal improvements to thread handling for high concurrency when using cluster-wide distributed job queue and deployment/publishing
  • Cleaned up default logging to make things a bit less chatty and improved log message collection during commit of transactions

Cloud CMS User Interface Server

  • Moved branch-sensitive pages (rules, forms, definitions) back to the main Project view such that they will be accessible to Project Managers
  • Moved Activities and Members pages up to the Project bar, freeing up space on the left-hand side menu
  • Added a Project "Developers" section accessible to Project Managers and moved GraphQL and Query into that section (since they are also branch-sensitive)
  • Fixed a bug in the edit forms for Deployment Strategy and Deployment Target
  • Fixed a bug where preview renderers for some mimetypes could fail on older versions of some browsers (here's looking at you, IE)
  • Simplified the modal dialog for New Application to keep things simpler
  • Fixed a bug whereby some API keys might fail to render on Developers > API Keys for older applications

Cloud CMS Application Server

  • Added /graphql as a middleware route that proxies through to API using the current application's repository and branch - allows for multiplexing of GraphQL operations against different branches and supports Instant Preview of development branches by a single app
  • Improvements to proxy efficiency, enhanced use of LRU caches and improved locking for higher concurrency
  • Update to latest third-party dependencies


Cloud CMS Release 3.2.17

Published on 12/11/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.17 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Tree API now handles multiple leaf paths and logs invalid leaf paths instead of throwing an exception that had previously failed the entire operation
  • Improved branch auto-maintenance methods to handle automatic cleanup of dangling graph associations between content instances
  • Allow the OAuth 2.0 refresh token race condition window to be customized via properties file
  • Updates to MongoDB collection indexes for faster performance
  • Improvements to the internal management of access tokens, refresh tokens and virtual hosting to make things more efficient and automatic for developers, including new properties file settings to finely control access token and refresh token expiry periods at a Docker config level
  • Added a Spring-config driven way of enforcing the deletion of older access tokens on server restart.
  • Adjusted controller method that reports activities to UI so that activities are always scoped to the projects that a user is a member of.
  • Improvements to Job Queue to more effectively use timestamp ordering of queue elements.
  • Transfer Export job is now phased to allow for AWAIT state while child export jobs execute.
  • Improvements to SSO user sync profile so that everything now occurs server side within a cluster-wide lock, removing the need for app server to establish and maintain this lock.
  • SSO user sync now automatically adjusts user name based on SAML Assertion or JWT profile derived user name.
  • ACL checks on Application datastores now check Project stack if Application belongs to a Project
  • Fixed a bug wherein failed deployment packages could leave deployment records in a processing state.
  • Update to latest Gitana Commons library

Cloud CMS Application Server

  • SSO user synchronization now uses a server-side method, reducing the overhead inside of the app server and removing the need for an app-server scoped lock
  • Improved handling of access token renewal and refresh token management within SSO layer
  • Reduced SSO logging (use environment variable CLOUDCMS_AUTH_FILTER_LOGGER_ENABLED = "true" to enable)
  • Proxy passthrough now supports automatic refresh token processing
  • Added some performance optimizations within caching layer (null sentinel values)

Cloud CMS User Interface Server

  • Fixed a bug whereby some UI extension overrides for custom whitelabel logos might not apply for login screens (including SSO and Multifactor Authentication screens). These branding elements are now consistently restored throughout.
  • Fix sop that Related Content field supports empty {} objects by interpreting as null for relator pickers
  • Improvements to Administration Console management pages for Web Hosts, Auto Client Mappings and Applications
  • Project Search Selected... actions are now configurable via config service
  • Fixed a breadcrumb link within the Content Model Builder
  • Project Listing pagination controls now automatically hide for editorial users (non owner/manager)
  • Fixes and Improvements to CSS

Cloud CMS JavaScript / Node.js Driver

  • Consolidated releases so that NPM distribution supports browser environments (including React.js) without any further work making dependency management easier
  • Better handling of HTTP State on Refresh Token timeout
  • Updates to Auto Client Mapping methods
  • Added GraphQL Query execution and Schema retrieval methods

Cloud CMS Command Line Client

  • Added an administrative command to rebuild MongoDB indexes for a given data store (optional recursing into child data stores)


Cloud CMS Release 3.2.16

Published on 12/04/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.16 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Added support for Amazon Comprehend - natural language processing (NLP) service that uses machine learning to find insights and relationships in text. Included are two new content features (f:aws-sentiment and f:aws-dominant-language) that support automatic detection of content sentiment and language/locale.
  • Added support for Amazon Transcribe - an automatic speech recognition (ASR) service that adds speech-to-text capabilities to your content. Included is a new feature (f:aws-transcribe) that supports automatic speech-to-text for audio attachments.
  • Enhancements to distributed job queue to support externally executing processes with both polling and queue-based callback for signaling of job completion. Job queue now utilizes more multi-phase jobs to allow for better concurrency and await state management.
  • Added support for multiple MongoDB environments and support for no downtime migration of MongoDB database from one environment to another while serving live read/write requests. Includes oplog (operations log), request tracking, replay of oplog onto new environment and activation. Multiple MongoDB environments provides an elegant way to migrate DBs from older versions of MongoDB to newer versions without incurring any downtime. It also provides a way to offer a high performance DB for some databases or applications if desired.
  • Added command line tool support to script MongoDB database migration.
  • Audit records are now written to Log4j-based logging service and stored on disk. This reduces the size requirements on the DB and makes it easier for customers to integrate to third-party BI tools. Customers can also control the log format, rollover scheduling and replication of log files to S3 (among many other things).
  • Improved GraphQL to support deeply nested objects and nested arrays for non-relator properties
  • The max number of concurrent jobs per tenant platform has been increased to match the max per installation by default. Customers who use platform multi-tenancy may calibrate this setting as they desire.
  • When performing a touch document action against a node, relator properties that point to non-existent nodes are now cleaned up
  • Archives are now automatically cleaned up by default when deployment packages complete execution of all of their handlers
  • Fixed a user creation bug whereby failed password validation didn't always clean up the user properly
  • Upgraded versions of some third-party dependencies including iText to make PDF and other textual document extraction a bit better and more reliable
  • Improvements to error handling and logging throughout the product, including jobs and job log entry capture

Cloud CMS User Interface Server

  • Improvements to drag-and-drop support within the Content Model Builder such that you can now drag fields out of an object and into container entities on multiple levels. Support for dragging fields from the template panel into objects within the builder.
  • Forms now support drag-and-drop for arrays, making it easier to adjust the order of entries in a long list. Works for scalar values as well as complex sub-types (nested objects, sub-properties).
  • Updated helper text and messages in several places. Password policy is now displayed for the user when creating a new account.
  • Fixed a bug to make the UI compatible with some legacy data (which doesn't have edited_on or edited_by properties stored on the Node's system data).

Cloud CMS Developer SDK

  • Added a sample ReactJS web application using the Cloud CMS app server and the Cloud CMS GraphQL API
  • Added a sample Angular web application using the Cloud CMS app server as an API gateway and Cloud CMS as a backend
  • Added a new Java sample to demonstrate node operations on all project content repository branches

Cloud CMS Command Line Client

  • Added command to support automatic MongoDB database migration


Cloud CMS Release 3.2.15

Published on 11/17/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.15 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Fixed a bug that prevented some preflight CORS requests from working properly
  • Added support for {{initiator.name}} in workflow email templates
  • Fixed a bug that prevented the Administration Console from persisting a cookie, requiring users to log in more than once
  • Web Hooks fired when a release goes live now correctly preserve HTTP headers from JSON config
  • New Projects created via the UI now enable the Content Model Builder and the left-hand Folders tree by default
  • Improved automatic QName generation for new Content Type definitions

Cloud CMS User Interface Server

  • Document header now shows modification date, modified by, creation date and created by underneath title of the document
  • Removed the Document Properties panel from the Document Overview page
  • The "Edit Content" action on the Content page is now hidden when multiple items are selected
  • The "Edit Document" action on the Folders page is now hidden when multiple items are selected
  • Edit Actions now redirect to document Edit Properties page (instead of using a modal for content entry)
  • Fixed a bug whereby the Document Viewer page would not render for documents viewed either via document library, via workflow or via a workflow task
  • Added back missing GraphQL icon
  • Changed the sample GraphQL query to be based around n:node
  • Improvements to Content Model Builder to provide better validation, some more defaults and smooth out usability a bit more
  • Pickers now support the optional use of a DataLoader to reduce network traffic and bulk load picked items (DataLoader class is provided out of the box for use in custom pickers)
  • Improvement to automatic QName generation when creating definitions
  • Fixed a rendering issue within Administration Console's when viewing Client objects
  • Fixed a bug in the login page so that original URL is properly retained and redirected to after login

Cloud CMS Command Line Client

  • Added command to List Projects (with pagination)
  • Added command to Query Projects (with query + pagination)
  • Added command to List Applications (with pagination)
  • Added command to Query Applications (with query + pagination)
  • Added command to Download API Keys (gitana.json)
  • Added commands to Get, Set and Remove DataStore configuration key/value pairs
  • Fixed a bug ensuring that the embedded Cloud CMS application server always mounts to the current directory


Cloud CMS Release 3.2.14

Published on 11/12/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.14 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • Support for Multifactor Authentication (MFA - external SMS, Voice or App verification code for sign in) configurable globally as well as per-tenant via service configurations. Initial out-of-the-box providers for Authy and Duo Security. For more information, see https://www.cloudcms.com/documentation/mfa.html.
  • Added formal support for encrypted properties within API configuration properties files using pub/private keys. This allows passwords, secrets and other credentials to be safe guarded so that they are only read by the API server. For more information, see https://www.cloudcms.com/documentation/docker/configuration/encrypting-properties.html.
  • Ensure node service invalidates for branch when branches are archived
  • Added a check to make sure that archived branches are not included in dashlet controllers recent content queries
  • Added command line tool to help customers generate pub/private keys and manually encrypt and validate encrypted values within properties files
  • Updated third party dependency versions

Cloud CMS User Interface Server

  • Added support for Multifactor Authentication (MFA) - services and user settings screens and a new wizard that helps users set up MFA and register their mobile devices. For more information, see [https://www.cloudcms.com/documentation/mfa.html]
  • Fixed a bug whereby admin console wouldn't render in some browsers due to a CSS glitch
  • Fixed a bug that prevented the Authentication Grant Edit page from working for some grant values
  • A message is now shown when an attempt to undeploy a workflow fails
  • Fixed a bug that prevented form "view" attributes from being copied back to the Alpaca config ahead of render of a content form (this prevent some layouts and wizards from working as intended in those cases)
  • Fixed a bug that prevented the UI from rendering properly after a selected release is archived and the active branch is still being referenced in the browser URL (in this case, the browser URL is deliberately reset to prevent this from happening)
  • Document View Properties now shows the edited date instead of the modification date to make it more intuitive and consistent for editorial users
  • Fixed a bug that prevent content types (on the left hand side of the Content page) from being sorted correctly
  • The "My Projects" dashlet now supports specification of sort (recently created or recently modified with the former being the default)
  • Fixed a bug that prevented the Kaltura module's menu options from appearing in the right place


Cloud CMS Release 3.2.13

Published on 11/04/2018
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.13 release.

Upgrade from 3.1.x

For Docker on-premise customers and for customers who've built custom modules, we recommend reviewing the Cloud CMS 3.2 Migration Documentation.

Cloud CMS API

  • API now populates a special header ("x-cloudcms-api-execution-time-ms") that stores the time in milliseconds between when the API sees the request arrive and the first byte is committed to the output stream. This can be useful while debugging latency issues as it indicates what portion of the latency is network-related versus execution-related (i.e. DB timing or index performance).
  • Fixed a bug that prevented the "_parent" of a definition from being updated from within the user interface
  • Better handling of exceptions while sending emails
  • Branch repair function now automatically handles cases for duplicates QNames in the dictionary

Cloud CMS User Interface Server

  • Better handling of exceptions while sending emails - improved error messages when an email provider isn't available or is misconfigured.
  • Action titles now support config-service specification of titles and other attributes, allowing for dynamic configuration and override of action modals and labels using Handlebars.
  • Improved support for automatic Handlebars processing of values coming out of config service, allowing for dynamic labels for pages, buttons and more.
  • Content Model Builder now refers to "arrays" as opposed to "lists".
  • Fixed a bug that prevented Project-level sorting and display settings for Content Types from saving properly.
  • Fixed a bug whereby the "Copy to Folder" and "Move to Folder" actions were not allowing folders to be picked properly
  • Navigation has been improved so that clicking into a content instance from the "Content" page no longer jumps out to the "Folders" routes. Instead, the "Content" route remains and the breadcrumb is consistent, keeping users in the "Content" section and letting them click back at any point.
  • Fixed a bug that prevented pagination controls from showing up for the document list when viewing large data sets and viewing across subfolders.
  • Improvements to bread crumb to reduce the amount of information shown so that it is shorter and always relative to the left-nav menus.
  • Fixed a bug with the Create Data List wizard where the list item type wasn't being applied correctly.
  • Fixed a bug in which changes to a user's avatar image were not reflecting immediately

Cloud CMS Command Line Client

  • New version of the command line client that provides better support for scripting and non-interactive modes
  • Allows for easier scripting and response handling
  • Added commands for branch query, search, read and repair
  • Latency checks now report API execution time as well as round-trip latency timing inromation









Ready to Try Cloud CMS?

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