Release Notes 3.1.419
Publication Date: January 21st 2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.419 release.
Cloud CMS API
- Improvements to invalidation logic for page renditions so that less memory is consumed and large sets of page renditions process more efficiently and with a lower memory footprint
- Added ability to deleteAll() page renditions in one single operation (as opposed to iterating over the full set)
- Improvements to indexing for page renditions, allowing for faster lookup and retrieval, quicker invalidation for individual page renditions or groups of page renditions
- Fix so that tree() method uses a resolved branch ID instead of the incoming branch ID, fix so that tree path lookup works properly in all cases where a custom query is involved
- Node service tree() method automatically tries a fallback case when the root node isn't indexed, allowing "path" to be used more intuitively
- Improved logging if license provider fails to load a license
- Added ActiveMQ support
- Improved testing and core support for nested conditions in rules ("and", "or" and others)
- Allow for a "tags" request parameter on API calls to auto-populate related "_tags" on response for any nodes with "f:taggable" feature and related tags, allowing for efficient loading of related tags in a single call
- Upgrade to latest versions of Spring and other third-party dependencies
- Allow for properties file configuration of refresh token and access token validity periods
- Improvements to refresh token invalidation handling on the server-side including persisted "last_used" timestamp to prevent cluster-wide race condition that can arise in certain situations
- Added ScriptNode addFeature() and removeNode() methods
- Fix to Application import for cases where application is of type "Trusted" and doesn't have a required "host" field set
Cloud CMS Application Server
- Added logger service for global management of logging with log level and output file customization
- Added an "excludeAll" option to WCM page caching to allow for all request parameters to be ignored (instead of having to specify one at a time)
- Support for loading multiple dynamic configuration documents in different scopes (platform, project, user platform and user project)
- Dynamic config loading allows for explicit "invalidate" flag to force config stores to reload on the request (as opposed to waiting for SQS queue to catch up)
- Cluster support for all versions of Node up to 9.3.x (and beyond)
- Removed "multiple" cluster mode and added "sticky-cluster" as an option for continued support of Socket.io applications
- Added support for STOMP protocol (supporting many message queues including ActiveMQ, RabbitMQ and others)
- Support for path normalization within config service block loading
Cloud CMS Java Driver
- Improvements to how runtime settings can be provided (via gitana.properties as well as runtime System properties)
- Added support for "automatic reattempts" mode wherein streams are cached temporarily and automatically reused on reattempt if a 401 expired token is received - this allows for seamless, never fail usage of the driver
- Updated README with good information about how to set up different modes and system properties
- Additional tests to further stress multi-threaded access token and refresh token invalidation with race condition resolution
See Gitana with your own content
Talk with a solutions engineer about your content model, governance requirements and deployment — hosted in our cloud or running in yours.