Cloud CMS Release 3.2.38

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


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
  • 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

  • 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
  • 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)
  • 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
  • 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.
  • Fix to automatic extraction via Apache Tika for certain binary filetypes (such as .pkg or .zip files)

Get Started with Cloud CMS

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