Release Notes 3.1.418
Publication Date: January 1st 2018
The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.418 release.
Cloud CMS API
- Improved support for geolocation feature so that its schema attributes appear properly for non-system nodes
- Enhancements to branch merge with explicit tracking of merge changeset ID. Fixed a bug whereby previous changeset ID wasn't tracked properly in some cases
- Tenant logging provides more detail and better targeted for nested exceptions in tenant log
- Added a new and easier to use public API for revert() and reset() service methods at the branch level (two different ways to effectively rollback to a previous changeset)
- Improvement to transfer import to provide an alternate way to detect last target's node path (allowing for merge of content from external platforms)
- Allow API to be configured with a globally-defined default locale (in addition to the fallback that the JVM provides)
- Improvements to accuracy of I18N locale fallback on API call translations
- UI dashlets controllers now run some code blocks as system to ensure operability for some non-project user cases
- Activities tracking now more accurate with better detection of root authenticated user for some cases
Cloud CMS User Interface Server
- System Diagnostics page now uses placeholders instead of fixed values
- Fix so that the "Most Recent Edits" dashlet only shows user's specific edits (no group impact)
- Improvements to formatting of activities
- Added indicator sets to document list and selected panel (with interaction)
Cloud CMS Java Driver
- Added method to read API keys for application deployments
- Improvements to multi-project copy (across platforms, using multiple API key sets)
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.