Deprecation: ListDiff#elementEqual

In the Java API, method elementEqual of class com.coremedia.translate.workflow.ListDiff has been deprecated. Instead of overriding that method in a subclass, you can instead pass a predicate for equality to a constructor of that class.

(CMS-19502)

Improved Translation Workflow Auto-Merge

The "Auto-Merge" feature used in translation workflows to copy property values from master to derived content items has a new option for improved merging of translatable properties and link annotations. The new behavior is not enabled by default in this release to avoid unexpected changes. It will become the default in future versions.

By default and just like in previous releases, the "Auto-Merge" feature completely ignores translatable properties and never changes such properties in the derived content. This can however lead to unexpected results, especially for properties nested in structs. Furthermore, the new option has improvements for merging link annotations.

If the new behavior is enabled, then translatable (nested) property values will no longer be excluded from auto-merge, but also be copied from the master to the derived content in the same way as other values. However, opposed to non-translatable properties, if the derived content already contains a different value for a translatable property, for example some translated text, then the value of the derived content will be kept and no warning about a merge conflict will be shown. Furthermore, for annotated links like teaser targets with "call-to-action" texts or channel page grid links with validity dates: if a link is removed or replaced in the master content, then the auto-merge feature will also remove or replace the link correctly in the derived content, even if some annotation properties of that link were changed in the derived content. With the previous behavior, some annotation values could remain, even after the actual link had been removed. This is fixed if the new option is enabled.

To enable the improved merge algorithm, set the following Spring configuration properties for the Workflow Server:

These properties are documented in the Deployment Manual, section "CoreMedia Properties Overview | Workflow Server Properties".

(CMS-19498)

Multi-Site: Removed Deprecation for SiteModel's siteIndicatorDepth

We removed the deprecation notice for siteIndicatorDepth as part of the SiteModel .

As part of this change cm validate-multisite got extended by a new issue code:

The new issue-code is reported at level INFO and is triggered, when using a siteIndicatorDepth different to 0 (zero).

Motivation

As part of CMS-9521 we deprecated siteIndicatorDepth for 2001.1 and changed the default to 0 (zero) rather than 1 (one), as we got aware that many editors struggled with site indicators being hidden in the "depth" of a site – which in the end caused corrupted sites.

Nevertheless, migrating existing content from a depth 1 to depth 0 may raise considerable migration effort, as you have to move all site indicators up one level in one step (while stopping editorial work) and then republish all your sites.

Because of this, we decided to remove the deprecation notice, so that we will support site indicator depths different to 0 also on in the future. The default which ships with CoreMedia Blueprint will stick to the recommended default 0 , though.

(CMS-19378)