Configuration of custom merge strategy for Synchronization Workflow

For Synchronization workflows a custom merge strategy can be configured. See Blueprint Developer Manual, Section "AutoMergeSyncAction" and Studio Developer Manual, Section "Synchronization-Specific Customizations" for details.

(CMS-17145)

Help Text for Conflict Resolution Options (Synchronization Workflow)

On the "Start Workflow Window" of a Synchronization Workflow a new help text is displayed, which explains the options for conflict resolution.

(CMS-17140)

Localization workflow window with new design for no issues

The localization workflow window now has a new design if there are no issues.

(CMS-17115)

Editorial Comments multiple application support

Editorial Comments work now with multiple applications (e.g. multiple Studio servers). All applications will be informed about updates regarding editorial comment threads or editorial comments for a content. To support this, two new database tables ( EDITORIAL_COMMENT_EVENTS and INSTANCES ) have been added to the schema cm_editorial_comments . The schema upgrade will be applied automatically by Liquibase . When a rollback during the upgrade process is necessary, the new tables can be deleted without any implication.

(CMS-17037)

Synchronization Workflow Warning

On composition of a synchronization workflow in the Studio, a warning is displayed, if a target site is deselected, which has a selected child target site. A confirmation popup is shown, asking if the child site should really be deselected. This dialog option can be disabled using the corresponding checkbox, so that it is not shown again. Resetting the option is possible via "User Preferences" on the Tab "Features".

(CMS-16892)

Issues window for localization workflows restructured and Issues API extended

When you try to start a localization workflow and there are issues, you can open the issues window which shows a list of errors and warnings together with content links. The issues listed in this window are now restructured in two main sections. The 'Localization' section lists errors and warnings related to localization problems, e.g. a missing target locale to synchronise. The errors must be fixed before the workflow can be started. The warnings should be fixed, but the workflow can be started. The 'Content' section lists errors and warnings related to content problems, e.g. a missing article title. These issues should be fixed also, but the workflow can be started.

To define content and localization issues, the Issues API has been extended. The interface com.coremedia.rest.validation.Issues has two additional addIssue methods to add a single category or a set of categories to an issue. Currently there are only two categories defined: Issues.CONTENT_ISSUE_CATEGORY and Issues.LOCALIZATION_ISSUE_CATEGORY. Only issues of the former category can be found in the 'Content' section of the restructured issues window. Only issues of the latter category can be found in the 'Localization' section of the issues window. Further categories may be added in future releases.

Besides the Issues class, the abstract base class com.coremedia.rest.validation.PropertyValidatorBase was extended to allow to add issues with categories. However no concrete property validator currently sets categories. The following validators of type com.coremedia.rest.cap.validation.CapTypeValidator create localization issues: ContentLocaleMatchesSiteLocaleValidator, CrossSiteLinkValidator, DuplicateDerivedInSiteValidator, MasterVersionUpdatedValidator, SameMasterLinkValidator, SiteNameValidator. All other CapTypeValidators create issues without a category which are treated as content issues by the issues framework. Also all workflow validators of type com.coremedia.rest.cap.workflow.validation.WorkflowValidator create issues without a category which are treated as localization issues by the issues framework.

(CMS-16864)

Improved Studio accessibility

(CMS-16764)

Three Maven plugins updated to 3.0.0-M4

maven-surefire-plugin , maven-failsafe-plugin and maven-surefire-report-plugin have been updated to 3.0.0-M4.

(CMS-16152)

Added ExternalLinkButton to public ASDoc

The new class com.coremedia.cms.editor.sdk.premular.fields.ExternalLinkButton was added to the public ASDoc. The section 'Customizing Richtext Toolbar' in the Studio Developer Manual was extended with an example on how to add an InternalLinkButton and an ExternalLinkButton to the TeaserOverlayPropertyField component.

(CMS-14242)

Added InternalLinkButton to public ASDoc

The class com.coremedia.cms.editor.sdk.premular.fields.InternalLinkButton was added to the public ASDoc.

(CMS-14240)