Cloud CMS Release 3.2.88

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

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-88.html

With this upgrade:

• MongoDB 4.0 or above is required
• You will need to perform a cold restart of your API cluster.

Enhancements

Auto Translation

• The f:auto-translate feature now processes auto-created translated nodes using background asynchronous tasks, allowing the on-request operation to complete more quickly while translations are fetched, populated and automatically created in the background.

Database Guardian

• Added database guardian thread that automatically monitors analyzed queries to detect inefficient queries and hotspots.
• Automatic optimization of slow query hotspots on a per repository/branch basis.
• Automatic circuit breaking and quarantining of client / API keys that induce overload of DB usage due to inefficient queries – resulting in higher net performance of the system by guarding against overallocated DB connections and cursors.

Events

• Faster event handling for associated nodes and associated node attachments.

Find

• Faster and more accurate implementations for node find operations that act as a composite of layered calls into Elastic Search, the path index and MongoDB.

Index Auto-Optimizer

• Default maximum for composite key size has been raised to 10.
• Improved analysis of existing indexes that now takes into account bad locator strings while rebuilding candidate indexes.

Query Optimization

• Incoming queries are run through an optimizer ahead of passing through to the underlying database, allowing for optimization of the query structure to best accomodate the underlying facilities and strengths of MongoDB and the DSL.

Single Sign On

• Added the ability to enable/disable the requirements for SAML 2.0 assertions and response to be signed. In the SAML 2.0 specification, both assertions and the overall response payload are specified to be digitally signed. However, some custom SAML 2.0 implementations by customers do not this. As such, we’ve added these configuration options to support customer migration with the understanding that customers will implement this in due course.

Third-Party Libraries

• Upgrades to third-party lirbaries adn dependencies to address critical-level common vulnerabilities and exposures.

User Interface

• Faster rendering and performance throughout the UI and the Alpaca forms engine.
• Faster modals, pickers and popups.

Bug Fixes

Associations

• Fix so that committing nodes have their association source and target verified ahead of commit. This was done previously but failed for some cases. The new implementation is robust and certain to validate.

Command Line Client

• Fix so that the upgrade command provides better error handling.

Inline Links

• Fix so that inline links parser handles unresolved references gracefully.
• Fix so that inline links parser handles more syntatic references (such as mailto:) while parsing HTML.

Merge Results

• Several fixes to ensure that internal merge result cursors are properly closed at runtime to prevent potential memory leaks.

Mongo Lock Provider

• The MongoDB lock provider now uses the same configuration settings as the general MongoDB facility.

Transfer

• Fix so that very large exports work as intended by reducing heap overhead.

User Interface

• Fix so that pickers gracefully handle null data for min/max items validation.
• Fix so that the Tagged Documents page properly apply pagination information while browsing.
• Fix so that Content Items and Documents pages utilize the faster and more efficient find API.
• Fix so that Analyzed Queries list page truncates JSON blocks after 1024 characters for improved display.
• Fix so that Dataloaders consistently apply Chain() to retrieved objects ahead of render.
• Fix so that the table Alpaca field element renders consistently as intended.