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

Published on 07/10/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.38 release.

Update Recommendations

  • For improved performance, we recommend you rebuild your platform and project indexes.
  1. Go to Manage Platform > Tools > Index Platform Data Stores
  2. Go to Manage Project > Tools > Index Project Data Stores

New Features

Job Reaper

Enhancements

Content Models
  • Improved the JSON schema validation checks that run when a definition is created or updated to help safeguard against any syntax errors and catch them earlier
  • Added automatic cleanup for existing schemas to handle invalid JSON schema that might have crept in (such as incorrect type or enum entries - this helps to make sure everyone's existing schemas compile and are normalized to a proper structure ahead of use
JSON Patch
  • Faster and more accurate JSON patch calculations are now used during the branch merges
MongoDB
  • Improved some internal code paths that greatly reduce DB connection requirements when performing bulk creates, updates or deletes where chunks are segmented and executed in parallel

Bug Fixes

Deployment
  • Fix so that cluster-wide indexes that track dirty deployment records and pending packages work more efficiently and faster, reducing CPU utilization during large publishing and deployment operations
Tree
  • Fix so that depth-specific lookups using the Tree API work correctly and return results much more quickly
Relator Properties
  • Fix so that re-ordering relator property elements in an array will correctly adjust relator mappings and execute mappings against the correct indices within the index (preventing any overwrite)
Associations
  • Fix so that associations are more effectively crawled during a deletion to account for a case where a node may have both an owned and child association pointing to it and the assembly was failing to include the node because of the duplicity
Transactions
  • Fix to specific code path that would allow for an exception to be thrown inside of a transaction to fall out of the transaction block, such that the distributed write lock could fail to be released. This could lead to hung write operations (504 timeouts) until the lock released on its own.
Extraction
  • Fix to automatic extraction via Apache Tika for certain binary filetypes (such as .pkg or .zip files)


Cloud CMS Release 3.2.37

Published on 06/24/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.37 release.

Update Recommendations
  • With this release, we move to OpenJDK 11. As such, if you're running an API cluster, we recommend a full restart of the cluster to ensure that you don't have any Hazelcast cluster state serialization issues.
  • Please review the api.env file in the Download ZIP to see the configuration options for the G1G2 garbage collector. We recommend this garbage collector configuration going forward.
  • For improved performance, we recommend you rebuild your platform and project indexes.
  1. Go to Manage Platform > Tools > Index Platform Data Stores
  2. Go to Manage Project > Tools > Index Project Data Stores

New Features

OpenJDK 11
  • The API container JDK was upgraded to OpenJDK 11. OpenJDK is the open-source reference implementation of the Java Standard Edition (maintained by Oracle). This upgrade was driven in part by the coming EOL of Oracle JDK 8 but was also made because of some beneficial improvements to the development process and licensing model adopted for OpenJDK 11 and beyond. This upgrade includes a number of JDK bug fixes and improvements for socket management, network (HTTPS) support and much more.

For more information, see https://blogs.oracle.com/java-platform-group/oracle-jdk-releases-for-java-11-and-later).

Enhancements

Exports
  • Exporting content to CSV, Excel, ZIP or any other format now supports recursive lookup of subobjects for any folders. It also supports path-based exports for ZIP files to ensure the downloaded ZIP has a similar folder-based export structure as seen within the document library.
Node Policies
  • Node policies now feature incremental compilation, resulting in faster execution when changing policy bindings for a branch
SAML
  • Improved support for HTTPS ACS URLs - better logic for determining how to route and redirect to HTTPS IdP endpoints.
Branches
  • Branch Changes now ignore JSON diffs where the only differences are different branch IDs in relator mappings (since these will be cleaned up on merge anyway) This results in smaller and more useful diffs for editors.

Bug Fixes

Tree Support
  • Fix so that the /tree API method operates more efficiently for for nested folders with large sets of sub-objects (for certains queries and/or searches). This has been improved to fix a bug where the main user interface document library tree could take too long to respond (resulting in a CloudFront 504 exception).
Releases
  • Fix so that some system-driven operations against a release won't fail if the release is in a finalized state.
Node Policies
  • Fix so that branch policy bindings can no longer get out-of-sync in a clustered configuration.
  • Fix so that deletion of rule bindings with the UI works as intended
Relator Properties
  • Fix so that relator properties with custom mappings work more efficiently and don't incorrectly revert mappings for some cases where adjustments are made to an array
Custom UI Module Deployment
  • Fix so that a custom GitHub branch can be specified and deployed via the user interface
Branches
  • Fix so that custom branch indexes are preserved when a branch is reindexed


Cloud CMS Release 3.2.36

Published on 06/10/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.36 release.

Recommended Upgrade Actions
  • For improved performance, we recommend you rebuild your platform and project indexes.
  1. Go to Manage Platform > Tools > Index Platform Data Stores
  2. Go to Manage Project > Tools > Index Project Data Stores

New Features

Distributed Jobs
  • Added a new Jobs page that lets Platform Managers and Project Managers view and inspect background jobs that are running for a given platform or project. These jobs include things like background indexing tasks, deployment and publishing tasks and tasks devoted to off-process machine learning analysis, multilingual translation and image recognition calls. Previously, this was only accessible via the Administration Console and we are now making awareness of these background jobs more central to main user interface.
Multilingual Translation Services
  • Added support for automatic translations using Google Translate (https://www.cloudcms.com/documentation/integrations/google/translate.html).
  • Added support for automatic translations using Microsoft Azure (https://www.cloudcms.com/documentation/integrations/azure/translate.html).
Node Policies / Events
  • Added support for p:beforeRefreshNode and p:afterRefreshNode event policies allowing customers to explicitly chain event handlers to refresh actions.

Enhancements

Image Transformation
  • Faster image manipulation, sizing and transformations for popular image formats.
Authentication
  • Additional properties are now available to allow further customization of login handling, including the max number of attempted logins per account and the default reset timeout in case of an exceeded attempt.
Binary Storage / Attachments
  • The Refresh Node action now restored node attachment attributes (such as content type and length) by inspecting the binary storage source to help repair any attachments that may be improperly recorded.
  • Faster storage of attachments to GridFS, S3, the file system or other binary storage providers.
Email Service
  • Emails dispatched from the Cloud CMS API are now multipart by default and have their body payload inspected to ensure that both HTML and Text parts are applied so as to improve spam scoring.
Branches / Releases
  • Faster and more accurate caching of branch-to-branch diffing and change tracking.
Forms
  • Forms now support inheritance (following the definition _parent property or a per form _parent form key).
  • Upload Field within Forms now provides better error handling and messages when XHR uploads fail.

Bug Fixes

Image Transformation
  • Preview image generation from some deeply-layered PDF files could take an excessive amount of time to process due to the high number of layers.
Node Policies / Events
  • Chained rule event handlers properly maintain property value assignments when relator property mappings execute.
  • The Rules Policies page now reflects all of the bound rule policies (instead of just the most recent)
  • The p:afterTouchPropertyPolicy only fires for non-empty values of property on node create.
Binary Storage / Attachments
  • Node attachment object IDs always increment on create/update, ensuring uniqueness of attachments in node version history.
  • Attachment merges are handled more elegantly so as to resolve a bug in which the contentType and/or length could be improperly merged when treated as individual collisions.
  • The p:beforeDeleteAttachment and p:afterDeleteAttachment policies are triggered automatically whenever a node that has attachments is deleted.
Branches / Releases
  • The deletion of definitions during a merge occurs after the deletion of any instances of that definition type, allowing more complex merges to proceed without any additional effort.
  • Fix to pagination and improved accuracy of results traversal for "Compare Workspace" and "Copy From Workspace" actions
Forms
  • Updated Regular Expression within the Forms Engine for emails and URLs to allow for more accurate representations of those data elements.


Cloud CMS Release 3.2.35

Published on 05/30/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.35 release.

Recommended Upgrade Actions
  • For improved performance, we recommend you rebuild your platform and project indexes.
  1. Go to Manage Platform > Tools > Index Platform Data Stores
  2. Go to Manage Project > Tools > Index Project Data Stores

New Features

Slack
  • Added a Slack Action to allow rules and scripts to send notification messages to Slack channels and users (see https://www.cloudcms.com/documentation/integrations/slack.html).
  • Added a Slack workflow event handler so that Slack messages can be automatically sent as documents transition between workflow states (see https://www.cloudcms.com/documentation/workflow/workflow-handlers/slack-message.html).
  • Added a Slack release event handler so that Slack messages can be automatically sent when releases are merged and go live (see https://www.cloudcms.com/documentation/releases/actions.html#send-a-slack-message-release-action)
  • Added support for Handlebars templates for Slack message generation within the aforementioned actions and handlers
Security
  • Allow for configuration of optional guest user account (guest user is disabled by default)

Enhancements

Transfer
  • Added a faster cached write option for binary storage, doubling the speed of writes to S3
  • Optimized transfer imports from a remote URL to increase the speed of importing, copying or creating projects from URL-based archives
User Interface
  • Moved platform "My Tasks" link into header
  • Node Picker now offers a description column to help editorial users distinguish between entries with common attributes

Bug Fixes

Elastic Search
  • Fix so that HTTP Client bulk writes work as intended for some JSON structures
User Interface
  • Fix so that sorting works as intended for content instances page
  • Fix so that pickers mounted on relator fields insert the correct reference object for some cases
  • Fix so that slug field correctly supports the emptyOnly option
  • Fix so that CKEditor keyup event handling works as intended


Cloud CMS Release 3.2.34

Published on 05/26/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.34 release.

Recommended Upgrade Actions
  • For improved performance, we recommend you rebuild your platform and project indexes.
  1. Go to Manage Platform > Tools > Index Platform Data Stores
  2. Go to Manage Project > Tools > Index Project Data Stores

New Features

Refresh Node
  • Added a new refresh() node method that takes on much of the "repair" functionality that had been introduced as part of touching a node.
  • Going forward, a touch is a call to perform an empty update (with no additional operations occuring on the API-side).
  • A refresh is a call to do anything needed server-side to "repair a node" or clean it up. This is includes rebuilding relator associations.

Enhancements

Relator Properties
  • Faster performance of relator properties, some solid improvements both on the API-side and within the forms engine to support
Forms
  • Faster validation and rendering for deeply nested forms with internal $ref structures
  • The text field type (text) now supports the lowercase and uppercase formats directly (no need to use a different field type)
  • The text field type (text) now supports boolean trim option to automatically trim value ahead of assignment
Elastic Search
  • Elastic Search HTTP client now supports customization of connection timeout, socket timeout, retry timeout and bulk chunk sizes, providing administrators with more flexibility in terms of scaling the Elastic Search cluster and network throughput
Dynamic User Interface
  • ACL checks on lists of items are now conducted in more places and more effectively used to ensure that the "Selected..." menu more accurately reflects available choices (automatic enabling and disabling of menu options)
Log In
  • Added more safeguard checks and validation during the sign in process to avoid unnecessary server-side handling of authentication failures
  • Improved validation and error messages during the sign in process to give users better immediate feedback

Bug Fixes

File and Node Pickers
  • Fix to ensure that new items can be added to file pickers and node pickers without regenerating existing reference objects (and un-applying any previously applied relator property mappings)
Branches
  • Fix so that branch creation within the user interface no longer times out with an error for branches that take a long time to setup and prepare (now uses an asynchronous job processor)
Error reporting
  • Fix to restore prior modal notification of validation errors that are raised during commit
Content Model Builder
  • Fix to Attachment Field editor so that the Attachment ID can be updated after assigned.
Jobs Administration
  • Fix so that Jobs administration page within the Administration Console sorts correctly for a large number of collection entries (additional Jobs collection index added)


Cloud CMS Release 3.2.33

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

Recommended Action
  • For improved performance with relators you will need to rebuild the project indexes. Go to Manage Project > Tools > Index Project Data Stores

New Features

UI Templates
Themes
  • Several new Themes have been added -- including a Dark Theme -- to give users more choice and better options.
Command Line Client
  • The Command Line client now supports commands to compress repository changesets and apply patches

Enhancements

Relator Properties
  • Updates and mapping execution for relator properties now executes between 3x to 5x faster than before
  • Updating a node that has a large number of relator properties now updates much faster
  • Reordering items within an array Relator Property now updates with a much small footprint (and thus, much more quickly)
GraphQL
Forms
  • Forms that have many relationships (such as many node-picker, file-picker or related-content fields) will render much more quickly due to optimization of the dataloader mechanism.
Branches
  • When creating a new branch, any problems that might arise during the population of the Elastic Search index are now ignored and the branch is no longer blocked from being created.
Platform Members
  • Fix so that the Platform Members render more information onto the screen when being viewed

Bug Fixes

Relator Properties
  • Fix so that relator properties correctly detect nested properties, aiding ease of migration from non-relator properties to relator properties within the content model
Internationalization (I18N)
  • Fix so that publishing a multilingual master node will not result in the additional publication of translation nodes. Translation nodes may publish separately or they may be shipped all at once (along with master node) via a multi-node commit.
Project Teams and Members
  • Fix so that team members page renders properly for some cases where team permissions were not set for the current user
  • Fix so that projects that do not have their own Domain configured within the stack can still use the Project Members page


Cloud CMS Release 3.2.32

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

With these release notes, we're trying out a new layout that breaks down changes by:

  • New Feature - new additions to the product
  • Enhancement - improvements to existing areas within the product
  • Bug Fix - a fix to a bug that was reported within the product

Please contact us with any feedback regarding these changes to the release notes.

New Features

Dashboard
  • The platform level My Projects Dashlet now indicates the total number of projects and the number of projects being displayed
Application Server
  • Handle SIGTERM in addition to SIGINT on exit. This helps apps running on docker containers exit cleanly

Enhancements

Branches / Releases
  • Improved the speed and accuracy of branch merging and differencing.
  • A new master node index was added that, if available, will be used to speed up database queries.
  • Reduced the amount of memory required during the merge (tested using very changeset histories in the millions)
  • Clicking on a workspace or release in the Network view now navigates the browser to that respective workspace or release
  • The assigned release date is now validated and must occur in the future
Transactions
  • Improved how transaction bookkeeping is done to improve speed and save on memory required.
User Management
  • Improved password validation on client side for better immediate feedback when creating new users or filling out registration and registration confirmation forms
  • Improved validation messages throughout user registration flow
  • The Create User wizard has been optimized to be a single page requiring fewer clicks and letting you get everything done in one place
Forms
  • The "upload" field now supports a "progressall" option which allows custom field developers to hook in a progress listener (to report progress state back to the user)
Upload
  • User avatar and platform logo upload forms are now easier to use
Publishing
  • Added an Edit Publication action for project publications

Bug Fixes

Branches / Releases
  • Fix to ensure that relator properties and their ref field have their branch ID adjusted when merging between branches.
  • Touching a document now walks the relator properties and automatically corrects any ref fields it discovers that point to the wrong branch
  • When deleting a current workspace, the browser now navigates back to the parent workspace
Content Model
  • Fix to ensure that setting required: false for a property will cause that property to be removed from any top level required: [] blocks
  • Fix to content model builder so that buttons activate for some cases where they were not
  • Fix to content model builder so that targeting for drag/drop of elements into nested objects and arrays works as intended
User Management
  • Fix to ensure that users can be added in bulk to multiple teams for cases where a user might already be a member of a team (the duplication is noted and proceeds with remaining teams)
Security
  • Fix to ensure that admin password can be overridden when specified via docker.properties
Forms
  • Fix to ensure that pagination works on the Choose a Form card when creating a new content instance
  • Fix to ensure that custom HTML tags introduced via CKEditor are preserved in transitions to/from source
Custom Indexes
  • Fix to ensure that creating a custom index will work for all cases
Search
  • Fix to Search properties list so that it updates properly as content types are adjusted
Data Lists
  • Fix to allow for some cases where Create New Item action was not showing up correctly for Data Lists
Publishing
  • Fix project publishing sync when user deletes deployment strategies
  • Fix project publishing sync after editing deployment strategy


Cloud CMS Release 3.2.31

Published on 04/05/2019
The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.31 release.

With these release notes, we're trying out a new layout that breaks down changes by:

  • New Feature - new additions to the product
  • Enhancement - improvements to existing areas within the product
  • Bug Fix - a fix to a bug that was reported within the product

Please contact us with any feedback regarding these changes to the release notes.

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.

New features

Antivirus
Internationalization
JavaScript Driver
  • Added method branch.queryDefinitions() to allow for querying definitions on a branch
User Interface
  • Allow the Create Project Wizard to load its list of Project Templates from a custom registry (loaded from HTTP). This lets customers store their Project Archives at an HTTP address and have those registries be parsed and made available to the editorial team when they create new projects.

Enhancements

Content Model
  • A filter is now available on the Content Model screen to allow users to filter content types, associations and features by query term
  • The content definitions tree is now more responsive and allow you to filter the list by clicking on items within it
Deployment
  • The family of file-based deployers (File System, S3 and FTP) now allow for configuration driven deployments. Use custom mappings to define how deployed nodes map down into files. Use Handlebars templates to determine deployment paths based on the context and data of content being deployed. For more information, see: https://www.cloudcms.com/documentation/deployment/deployment-mappings.html
Docker (On-Premise)

Java Driver

  • Use explicit UTF-8 charset on JSON response handling (instead of relying on system defaults)
Projects
  • The system now checks to ensure that multiple Projects are not created with the same title
User Interface
  • The Branch Picker now features a hierarchical view of branches (similar to Workspaces page)
  • The configuration section for Custom Locales was moved to its own page under Manage Project
  • It is now possible to edit Service Descriptors after they've been created (if you have Manager rights)

Bug Fixes

Antivirus
  • Fix slow antivirus performance by using the out-of-process Cloud CMS Antivirus service
Application Server
  • Slight fix to ensure SSO user and group mappings (auto principal sync) work as intended
Branches / Releases
  • Fix for node deletions not showing up consistently in the Branch Changes list (when comparing or pulling between branches)
Content Model
  • Fix to ensure that updates to server-side javascript properly rebind for the branch in all cases
Core
  • Fix for save issue that could occur due to the filename feature being applied as mandatory to parent type
Deployment / Transfer
  • Fix to ensure that exports and imports work correctly when multiple nodes are exported in a changeset manifest. This may resolve occasional exceptions for large, multi-document deployments.
Search
  • Fix so that definitions when created, updated or deleted, are incrementally indexed as intended
  • Fix so that Elastic Search Scroll API is used properly for some large paginated calls
User Interface
  • Fix so that password policy validation errors and messages are more accurate when a user is invited and registers for a project
  • Fix so that pressing the enter button when creating text files doesn't auto-submit


Cloud CMS Release 3.2.30

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

  • Faster branch creation that takes advantage of some improvements to MongoDB that allow for optimized collection copies
  • Improved branch merging that now leverages a memory cache for much faster execution. Many improvements including more efficient string substitution on merged objects, a more robust method for applying JSON patches, reduced event handling overhead
  • Improved support for JSON Patch, patch generation and patch merging as used within the product to detect and resolve merge conflicts. Improved support for nested arrays and enumerated value sets.
  • Added some safety checks to ensure that Access Control lookups that contain any unresolvable references will continue to process and will just ignore the missing reference.
  • Added some safety checks to ensure that module deployments will work even if the Application deployment sub-objects contain bad data or do not parse as expected.
  • Adjusted Remote Deployment Receivers so that they default to using a GET to retrieve remote deployment package status
  • Certain reserved user names are now blocked for being used on creation and update of principals so as to prevent confusion (such as system, admin, everyone and other reserved names).
  • Fixed a bug where some distributed jobs executing in the cluster could error out but remain stuck in a RUNNING state (this impacted some cases where multiple jobs could execute concurrently and get stuck until the sync timeout).

Cloud CMS User Interface Server

  • For Releases and Workspaces, the "Pending Merges" page now only appears when the underlying branch has unresolved merge conflicts.
  • Fixed a bug that prevented the CKEditor-Tools plugin from loading properly for some cases.
  • Fixed a bug that prevented the Project Members page from correctly performing ACL checks when users in the project spanned multiple domains.
  • Added the ability to configure the "maxFileSize" option for Node Picker and File Picker uploads.
  • Removed an extraneous "path" sorting option from the Node Picker.
  • Fixed a bug that could cause the Markdown field to not render properly for some cases
  • Fixed a bug that impacted how fields would internally get named by adjusting how field names with square brackets and slashes are serialized and token replaced
  • Fixed the "Pick A Color" field so that it properly puts the hash ("#") in with any selected values.

Cloud CMS JavaScript Driver

  • Fixed a bug that prevented References acquired using the ref() method from being incorrectly typed for Users and Groups (those types were capitalized when they should not have been).
  • Added the ability to plugin a custom map handler function for chainPost() calls
  • Added a generic ResultMap class


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









Get Started with Cloud CMS

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