Third-Party Update: Spring Boot 2.1.6, Spring Framework 5.1.8 and other third party libraries

The following third party libraries were updated:

Follow Section, “Third-Party Update: Spring Boot 2.1.6, Spring Framework 5.1.8 and other third party libraries” for upgrade information.

(CMS-15069)

Removal: External Library Extension

The external library has been removed from the Blueprint. This feature is replaced by the Content Hub.

(CMS-14983)

Removal: Navigation Tree CollectionView Extension

The library extension for displaying the navigation tree has been removed (it was disabled by default). The functionality can be implemented with the Content Hub now.

(CMS-14838)

Extracted Remote Dynamic Packages from studio-client

The Remote Dynamic Packages feature has been extracted from the studio-client into a separate optional application called studio-packages-proxy. The studio-client now only serves static resources and no Java code. If enabled, the studio-packages-proxy can be deployed in front of the studio-client and will then proxy all requests to the studio-client, redirecting the requests to remote packages.

(CMS-14684)

Enhanced tool bar buttons functionality for workflows

Within the ControlRoomStudioPlugin.mxml the property "listToolbarButtons" was changed to "listToolbarButtonsFunction". Now it is possible to show buttons in the workflowPanelToolbar, depending from the chosen workflow and the current panel.

Follow Section, “Enhanced tool bar buttons functionality for workflows” for upgrade information.

(CMS-14584)

Quick Create has been moved to editor-sdk

In order to use the quick create functionality for core components, the quick create has been moved to the editor-sdk. Note that corresponding namespaces in MXML and imports have been changed accordingly.

(CMS-14483)

Studio REST Service now runs on Spring MVC Instead of Jersey

As part of our efforts for supporting Java 11, the Studio REST service now runs on Spring MVC instead of Jersey 1 (JAX-RS). Jersey dependencies are now banned throughout the workspace to avoid any mixture.

Follow Section, “Studio REST Service now runs on Spring MVC Instead of Jersey” for upgrade information.

(CMS-12077)

Increased Studio performance for reusable tabs

To increase Studio performance, we offer the possibility to reuse tabs for multiple working items instead of creating new tabs over and over again. Currently, this possibility is just implemented for document form tabs that display content items (Premulars). Consult the section "Re-Using Studio Tabs For Better Performance" of the Studio Manual.

(CMS-7863)

Document Type Selection for Preferred New Content

As an editor, I can now select the preferred document types that should appear on the top of the new content drop down menu (of the library toolbar) and on top of the "New Content" menu (of the favorites toolbar). Open the Content tab in the user preferences to select the preferred types.

(CMS-3081)

Default folder selection in New Content dialogs is back to normal

While replacing the textual selection of the target folder with a more sophisticated folder chooser, the default folder selection accidentally changed. The selection of the default folder is now back to normal so that custom lookup methods again take precedence over the built-in suggestions.

(CMS-15148)

Shoppable Video supports multiple banners at the same start time

The default behavior of the Studio validator used for the Shoppable Video has changed. It is now possible to define multiple content items with the same start time in the timeline, so that custom shoppable videos can support this use case per default.

Follow Section, “Shoppable Video supports multiple banners at the same start time” for upgrade information.

(CMS-15103)

Custom validation for translation workflows

As described in the Studio Developer Manual in section "Customizing Workflow Validation", you can define your own validators for a translation workflow. Within your custom validator you need to regularly call the runnable "isAbortRequestedRunnable" which will be provided by the parameters handed to the validator. The runnalbe will throw an exception if the validation was aborted. The exception will be handled by the validation framework.

(CMS-14260)

Removal: Studio IOC mechanism

The Studio IOC mechanism from the Studio core has been removed. Usages of the ComponentContextManager and the ActionScript annotations ProvideToExtChildren and InjectFromExtParent need to be refactored into using ValueExpressions with plain ExtJs component configurations.

Follow Section, “Removal: Studio IOC mechanism” for upgrade information.

(CMS-14063)

Quick Create configured by Setting content

The quick create dialogs consistently use the so-called Content Creation setting to enable setting the target paths for new content per content type. The possibility to use the deployment properties by setting CMArticle_home_folder= was removed.

Follow Section, “Quick Create configured by Setting content” for upgrade information.

(CMS-13219)