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

Published on 03/18/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.29 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 the ability for moved source folders to export and then import into a target project and auto-resolve previously existing nodes and move them accordingly
  • Improved performance of transfer import for large sets of nodes (includes optimization of a method that performs token substitutions in when running a "copy everything" strategy, improvements to caching, cache tuning and hot spot streamlining for progress tracking updates)
  • Added ability to customize token replacement and lowercase behavior of the "slugify" Handlebars helper during server-side template execution using project-level settings (this allows you to plug in custom character substitutions).
  • Fixed a bug whereby some owned associations were not properly enforcing concurrent deletion of the owner association source node
  • Improvements to Branch Changes calculation to make them more accurate for different views including a "full" view, an "editorial" view and an "editorial pull" view which are more meaningful when merging, comparing and pulling.
  • Adjusted how Platform and Project Owner roles are checked during context load when supporting the main user interface
  • Fixed a bug wherein transfer exports where not properly incorporating some of the settings from the posted JSON into the export config (resulting in larger, non-tip-mode-only export files)
  • Upgraded to Apache Tomcat 9.0.16

Cloud CMS User Interface Server

  • Added Markdown Field to the Content Model builder, letting you drag-and-drop and configure the Markdown field into your content definitions and forms.
  • Fixed a bug in the forms engine to adjust how default processing of multi-value strings (with a comma delimiter) works for checkboxes, radio buttons and select fields.
  • Fixed a few clever bugs in the Content Model builder that could affect usage of the Preview button
  • The Related Content field now formats information for clearly with a display mode when viewing properties for a document
  • Updated third party libraries
  • Fixed a bug that affected the ability to drag-and-drop files into a Related Content field for upload
  • Automatically default to "n:node" for relator property compatible fields that do not otherwise define a "nodeType" (includes Related Content field, File Picker field and Node picker field).
  • Fixed a bug that could cause a modal backdrop to hang when canceling the "create deployment target" action wizard
  • Cleaned up links to definitions so that the consistently link to builder view when appropriate
  • Consolidated the Content Model builder view into the Definition view to make it easier to graphically build your content models and then flip over to interesting aspects such as setting up default paths or forms
  • Improved the "Compare Workspace", "Pull From Workspace" and "Copy from Workspace" actions to make them easier to use and to have them reflect more clearly what precisely has changed in the other workspace for those scenarios.
  • Added Project Manage > Slugify page to allow users to edit token substitutions and behavior of the "slugify" helper used within server-side processing of Handlebars templates
  • Added a "terms" Alpaca forms control that provides an easier way to edit text arrays by putting all values side by side in text bubbles, with auto completion and key-press delimiting (tab, comma, enter). This form uses the Bootstrap Tags Input plugin.
  • The Upload Document action now automatically rolls back uploads when the modal is canceled.
  • Fixed a bug in the Admin Console that prevented exports from launching
  • When viewing Archives within a Vault, the "date" column now shows the modification date and the "published" column shows whether the archive has been made available for usage within the Create New Project wizard.
  • The Document Versions list now shows the specific modification date/time (as opposed to the relative date)
  • Added back the document list header to allow for Select All button.

Cloud CMS Application Server

  • Improved error handling for some cases where file I/O might get interrupted or otherwise fail during configuration service initialization or reload


Cloud CMS Release 3.2.28

Published on 03/07/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.28 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 MongoDB 3.6.10
  • Significant improvements to performance and scalability through benchmark testing of standalone and clustered environments - additional caching for tenant and client services, faster API methods
  • Improved support for bulk node creation via multipart POST to allow for individual property specification using file parts
  • Enhanced S3 storage provider to support improved chunking on large file multipart uploads
  • Improved rule execution so that some critical paths execute as system user, making things faster and also reducing potential of permission check problems

Cloud CMS User Interface Server

  • Updates to workspace and release conflict resolutions screens to tighten them up and improve usability
  • Fixed a bug in the forms engine to improve support for multi-value strings, allowing for custom join and split functions and improved parsing of delimited values
  • Added Markdown field to the Content Model builder
  • Fixed a bug in the Content Model builder that had prevented the Preview button from working for some Related Node fields
  • Improved display rendering on Overview page for some control types including Related Content
  • Fix for responsive layout of workspace bar for smaller screens

Cloud CMS Java Driver

  • Added ref() method to all driver objects letting folks quickly construct a reference (these are commonly used for permission checks, exports and many other aspects of the API)
  • Updated AutoClientMapping properties and methods
  • Removed Warehouse datastore and interaction objects


Cloud CMS Release 3.2.27

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

  • Moving a node now properly re-indexes the node within the FileFolderService for some edge cases
  • Changes to parental path relationships are now propagated to the target during deployment
  • Added a missing title for the "deployNode" action in the actions drop down

Cloud CMS User Interface Server

  • When viewing a document, the "type" link has now been corrected to point to the correct place
  • The "Selected..." dropdown now respects access control rights on individually selected items to reflect whether actions are enabled or disabled. If permissions are not granted for the selected item(s), they will be disabled.
  • When performing UI extensions, custom region overrides now push their configuration down into custom JS gadget implementations
  • Users with the Project Manager authority can now view and utilize the "Release Immediately" button (no need for a separate authority)
  • The Delete and Edit Attachment buttons for Document Attachments now enable or disable basedon the current user's authorities
  • The Delete and Change Password buttons for users at the Platform level now enable or disable based on the current user's authorities
  • On the Document Versions page, the Changeset Link (to admin console) only appears for Project Managers
  • Fixed a bug so that Project Owners can now see the Manage Project button (and no longer need separately have the Project Manager authority assigned)
  • Fixed a bug so that Project Managers can add users to Projects as intended (without the need for a separate authority grant)

Cloud CMS Application Server

  • Updated to the latest cloudcms-server node module
  • Now checks for the existence of a local custom.js file on startup and, if available, calls an init() function to allow for easy extension of the server (including registration of custom Dust functions, routes and more).


Cloud CMS Release 3.2.26

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

  • Introducing Workspaces - Editorial users can now create Workspaces to take advantage of ad-hoc branching with automatic change and activity tracking. Compare, copy and pull content between branches while taking advantage of instant indexing for search, query and GraphQL. Instantly preview changes on live application and merge at any time. Features merge conflict detection, side-by-side visual differencing and a friendly UI for property-level conflict resolution. Workspaces is an optional feature that works alongside Releases to offer flexible scheduled publishing and finalization.
  • Lots of improvements to merge conflict resolution including side-by-side differencing, browsing of workspaces and releases for merge conflicts, individual property-level conflict resolution management, commits and merge re-attempts. Applies to both Workspaces and Releases.
  • Fixed a bug wherein newly created translation nodes could retain the "f:locale" feature from the master node and therefore retain the master node's locale setting (if applied)
  • Improved some error handling paths when running in a cluster with some latency between cluster members
  • Improved transaction error logging so that more log information makes its way to project logs
  • Single and bulk creation of nodes now execute in a single transactions, fixing a bug wherein web hook calls could be fired early and without complete path information
  • Project Type controller now looks up Add Ons using the official Cloud CMS Archives registry (which now includes an updated Sample Project)
  • Added a "branch" sub-object to Web Hook payloads to provide more information about the node's branch
  • Added the "deployNode" action and rule executor to allow for nodes to be deployed or undeployed as triggered via action or conditional rule
  • Changed the behavior of thumbnail generation so that it no longer generates "json" thumbnails (which were printouts of the JSON) - instead it skips generation for those cases and hands back a 404 which offers better compatibility with upstream CDNs
  • Added /ref/deploy endpoint to allow for scriptable, API-drive bulk deployment of nodes using a deployment strategy
  • Fixed a bug whereby deletion of a platform user from within the UI was skipping past a needed permission check
  • Several updates to third-party libraries

Cloud CMS User Interface Server

  • Added support for Workspaces
  • Enhanced pages for resolving Merge Conflicts - now includes side-by-side diff, visual selection of per-property resolutions, merge retries and an easier UI for merge comparison and management
  • Improvements to Releases to be consistent with new user interface for Merge Conflicts and Workspaces
  • Added support for the Alpaca Markdown field - use the "markdown" field type to embed a visual Markdown editor (SimpleMDE) on top of your string fields. Full support for Markdown with in-context preview.
  • Added a "Deploy Content..." action to the Folders and Content Instances view. Available to managers, this action provides a quick dialog to let you deploy an arbitrary piece of content via a deployment strategy.
  • Fixed a bug so that "sort by Attachment file type" works as intended in the File Folder picker
  • Added a UI refresh call so that the document path updates properly when the title of a document changes
  • Added a validation check to the "Add Publication" dialog so that the user cannot proceed unless a valid form valid has been provided
  • Added a catch-all fix for a stale or stuck "open-modal" class that could cause the page to no longer scroll
  • Fixed escaping of titles on some page header sections where HTML was getting double escaped
  • The Content Instances page now derives its selected actions from configuration - allowing third party customers and systems integrators the ability to extend the UI options.

Cloud CMS JavaScript Driver

  • Merge conflict commit() method now takes an optional target branch ID
  • Updated conflict resolve() method and added conflict commit() method
  • Fix to stringify() method to handle boolean false properly

Cloud CMS Developer SDK

  • Added a module example that demonstrates how to override and customize a Cloud CMS action (add-attachment) to provide your own user interface adjustments

Cloud CMS Command Line Client

  • Added list-datastore-deletions and refresh-db-connections commands to make it easier for customers to schedule nightly purges of deleted datastores from MongoDB (without having to call the REST API manually)


Cloud CMS Release 3.2.25

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

  • Improvements to performance and scalability for high load branch operations resulting in faster branch performance and scalability for both clustered and standalone (single server) configurations
  • Fixed a bug that would exhibit itself over time as via a "Cannot find source view" error and was due to certain kinds of repeated operations against a branch that failed to release transient transaction state.
  • Tightened up and improved many aspects related to how nested transactions process and manage state, ensuring that things are cleaned up and transactions neatly and reliably handle failure cases for all possible transaction phases.
  • Fixed a bug that could cause some import jobs to fail with an array index out of bounds exception.
  • Fixed a bug where some jobs could be launched without their tenant platform marked onto them. This didn't prevent them from working but did prevent them from being polled or reported on.

Cloud CMS User Interface Server

  • Fixed a bug that could prevent text selection for controls nested within a drag-and-drop array container.
  • Fixed the linking of Containers (folders) within the Content Instances page so that they properly link to the overview page for the content instance.
  • Added a quick action for Containers within the Content Instances page so that editors can jump over to the Folder view of those Containers if they so desire.
  • Fixed the sort order for the File Folder Picker and the Project Branch Picker.
  • Updated the password validation logic so that the Create User wizard cannot proceed without a password that contains at least 1 numeric character.
  • Cleaned up UI formatting and templates, tightened up CSS and removed a rather contemptible apostrophe from the document view page.

Cloud CMS Developer SDK

  • Now includes drivers to Python, PHP and Microsoft C#.
  • Added Nuxt sample and Cloud CMS Nuxt module to make it easy for developers to generate static web sites that surface Cloud CMS content.
  • Added Gatsby.js sample to help developers generate static sites that hook into Cloud CMS GraphQL and surface Cloud CMS content.


Cloud CMS Release 3.2.24

Published on 02/03/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.24 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 within the job processor whereby child jobs were not carrying forward platform information - this allowed for a UI bug whereby jobs were not correctly being polled for completion.
  • Allow the DictionaryService to lazy fault branch runtime init state
  • Fixed activity service pagination so that it is more efficient and works as intended.
  • Adjusted EC2 Discovery to take advantage of Hazelcast's AwsDiscoveryStrategy. Allow for configurable hazelcast binding ports on discovered instances.
  • Improved default logging for Hazelcast clustering so as to leverage better log4j2 settings

Cloud CMS Developer SDK

  • Updated examples for Angular, Vue.js and ReactJS


Cloud CMS Release 3.2.23

Published on 01/31/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.23 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 in the Dictionary Services cache which could result in some users seeing "Cannot find source view for repository" errors due to dictionary views not being found when committing nodes.
  • Significantly improved the performance of merging during branch merges or during release executions (or finalize). For large sets of source nodes (i.e. if you have a lot of changes), things are now much faster.
  • Fixed a bug whereby I18N translation nodes were carrying over relator information from the master node. This resulted in duplications of the relator set on the translation node and yielded poor performance when creating new translation nodes for some cases where a large number of relators existed on the master node.
  • Added automatic cleanup for existing translation nodes via a touch() operation. When a translation node that has errant relator properties and associations stored against it is touched, these errant properties and associations are automatically cleaned up.
  • Fixed bugs and introduced considerable improvements to the Distributed Job Queue to handle cases where complex jobs with multiple dependencies and AWAIT stages processed cleanly and efficiently within a clustered API configuration. This offers some compelling improvements for customers using Publishing or Deployment with complex payloads consisting of multiple assets deployed in a single shot.
  • More testing added for Deployment and Publishing along with improved execution within clustered environments. Cluster verification now includes both 2 and 4 node clusters. Lots of little improvements along the way.
  • Fixed a bug whereby the tree() method was not handling back results in alphanumeric order. It now does.
  • Custom branch indexes now copy from source branch to target branch on branch creation
  • The Node listVersions() call is now much faster and auto-limits to a result set size of 1000
  • Enhanced Inline Links so that the check to determine whether a link can deleted now takes into consideration whether the transactional deletion set includes all of the nodes that link to the Inline Linked object. This allows for bulk deletes of folder structures (or any document set) where the inline link object and any of its linkers are being deleted all at once.
  • Fixed a bug in the layered transaction engine by which node queries for nested transactions could sometimes produce a slightly wrong result set. This now does an additional check to filter out an edge case where some nodes might have been included when they should not have been.

  • Added the ability to manually declare your own API Keys using the "keyset" field on the Authentication Grant object
  • Added controller methods to hand back full API Key Sets for Owners and Managers of a platform. This now includes additional information such as principal, project and application bindings.
  • Association and Feature definitions are now included when importing definitions from a previous project into a new one.
  • Improved the way that deleted nodes are tracked during a transaction commit, resulting in a slight performance improvement (depending on how many nodes are in the transaction)
  • Improvements to the background Job Sweeper thread so that it picks out and cleans up more old or expired jobs on each pass

Cloud CMS User Interface Server

  • The environment variable CLOUDCMS_UI_HTTP_SERVER_PORT can now be used to specify the base location of the UI server for "forgotten password" emails (i.e. https://myserver.com:port). This can be used to point to a CDN entry point or load balancer at any location you prefer.
  • Fixed a bug so that sorting works as intended for lists within pickers.
  • Fixed a bug whereby documents may fail to render for older projects that have Publishing enabled afterwards.
  • Fixed a bug so that the link to the multilingual master node within documents lists works as intended.
  • Fixed a bug so that the document tree now respects the "hide system folders" setting.
  • Fixed a bug so that the Home Project selector field displays correctly.
  • The API Keys page now uses the new back end controller to hand back more information about API Keys. In addition, it now includes support for manually created API Keys using the "keyset" fields on Authentication Grants.

Cloud CMS Command Line Client

  • Added the ability to create projects from archives located within our official "addon" registry or a URL pointing to an archive living anywhere on the internet.


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









Ready to Try Cloud CMS?

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