Release Notes 3.1.448

Publication Date: June 20th 2018

The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.448 release.

Cloud CMS API

• Improvements to release and branch merges so that execution is faster and more accurate (removed a case where some updated nodes that had no changes could remain as part of the transaction set)
• Merge process now automatically detects nodes that are deleted and re-created with same ID or QName and converts them to updates to allow for seamless, non-deletion commits
• Improvements to merge error handling and error reporting
• Fixed a bug whereby an internal branch cache would behave improperly when two repositories with the same branch ID (the result of a replication using the COPY_TOP strategy) were being read from at the same time. Optimized cache to use a synchronized LRU cache to yield performance improvement as well.
• Fixed a bug whereby some rules could trigger before QName and ID uniqueness checks, resulting in errant "duplicate QName" or "duplicate ID" errors
• Fixed a condition by which a server initializing in a cluster might attempt to load a branch's runtime state if the branch is archived
• Added an administrative method to refresh a branch without rebuilding the underlying MongoDB transaction view first
• Upgrade to latest third-party libraries

Cloud CMS User Interface Server

• Updated release pages to provide better formatting and presentation of release conflicts
• Fixed a bug whereby print might not work for some browsers due to cross origin issues
• The "Release Immediately" button is now shown for the Project Manager authority.
• Fixed a bug whereby error messages on login could be misreported.
• Fixed a bug whereby lists might format incorrect for some columns where nowrap is specified.
• The "x-frame-options" header is now set to "SAMEORIGIN" by default (was previously left unspecified)
• Upgrade to latest third-party libraries