Cloud CMS Release 3.2.48

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.48 release.

Update Recommendations (On-Premise Only)

  • For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the reindex-datastore command via the Cloud CMS Command Line Client (

You can execute it like this:

cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password>

Where the username and password are the credentials for your administrator account.


Import / Export
  • Improved the transfer subsystem to allow for much larger archive payloads to be processed more quickly. This has a positive impact on any copy, move or duplication operations including publishing and deployment and also allows for more efficient handling of larger data sets for backup and restore.
  • Optimizations to speed up transfer including in-memory indexes and more efficient use of EHCache when managing off-heap storage
  • Added the ability to Select All Branches within the Project Export Wizard
  • Additional logging for deployment handlers
Relator properties
  • Improved error logging for cases where relator property members are missing their ref attribute

Bug Fixes

  • Fix so that branch comparison operations that encounter single entry deletions will display properly within the user interface
Search Indexing
  • Fix so that bulk index operations that use a paginated query handler (for large data sets) will calculate the offset correctly on iteration ensuring that all content items index for those cases
Import / Export
  • Fix so that text token substitution processes delimitters properly for some cases where HTML is being processed and the delimitter splitter size differs from token splitter size
Web Hooks
  • Fix so that node paths are consistently applied to payload for deletion cases that follow from a merge operation
  • Fix so that multiple conflicting future Releases can be scheduled as intended for certain cases where the intentionality of a specific conflicting nodes wasn't clearly defined. This allows for the Scheduling of Content Availability for these cases - whereby content is published on one Release and then unpublished on a second Release. For information about Scheduling Content Availability, see
  • Fix aso that Archive pagination works as intended for cases where Archives are errantly present with duplicate IDs
  • Fix to the user interface so that users can be assigned via override to a swimlane for pooled task cases where swimlanes are assigned to a group
  • Fix so that document paths are displayed correctly for cases where UI encoding is force enabled
  • Fix so that Markdown field toolbar settings can more easily be configured
  • Fix so that SimpleMDB field events fire for all cases
  • Fix so that Array field raises separate events for add, remove and move operations

Get Started with Cloud CMS

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