2.2.14. Release 7.5.31

This chapter contains all changes made in Release 7.5.31 of CoreMedia Digital Experience Platform 8.

Follow the CoreMedia DXP 8 Help Center section to receive release and product announcements automatically.

Modules and Tooling

Release 7.5.31 contains the following CoreMedia modules:

  • CoreMedia Blueprint

  • CoreMedia CMS

  • CoreMedia Studio

  • CoreMedia Elastic Social

In addition, CoreMedia DXP 8 uses the following tooling:

ProductKeyVersion
CoreMedia Application Maven Plug-inAPPPLUGIN2.7.9
CoreMedia Project Maven ExtensionPROJEXT1.0.5

Table 2.14. Tooling of CoreMedia DXP 8


CoreMedia Studio Changes and Improvements

  • Workflow Configuration

    com.coremedia.cms.editor.controlroom.workflow.WorkflowStateTransition

    The WorkflowStateTransition class provides a new config option defaultStep which allows to configure the step that should be selected by default.

    (CMS-3974)

CoreMedia Blueprint Changes and Improvements

  • New CMLinkable document properties

    The properties htmlDescription and extDisplayedDate were added to the CMLinkable document type.

    (CMS-4118)

  • Chef v12 recommended

    Chef v12

    • The Chef client in our Vagrant setup is currently still v11 (e.g. 11.18.12)

    • Chef v12 (e.g. 12.4.0) is recommended though and will be the default in future releases

    (CMS-4043)

  • Chef version update in Vagrantfile

    The chef version in the Vagrantfile has been updated to 11.18.12.

    (CMS-4008)

  • Minitests have been removed from coremedia cookbook

    As of this version the minitests have been removed from the coremedia cookbook, because the minitest-chef-handler is not compatible with Chef >= 12.4.0. As a replacement, we strongly recommend the usage of TestKitchen in combination with ServerSpec.

    (CMS-3938)

Fixed Issues

  • CMS-4125: IBM APAR prerequisites

    This release has IBM APAR JR53438 ("Mandatory cumulative Interim Fix for WebSphere Commerce Version 7 Feature Pack 8") as prerequisite which contains all of the previous required APARs.

    Additionally, for B2B Stores with Customer Segments based on user accounst, APAR JR53688 ("Customer Segment REST API does not return segments with Account conditions") is required.

  • CMS-3939: blueprint.site.mapping Values

    The values of the blueprint.site.mapping application properties (prefixes for absolute URLs) used to be normalized by cutting off trailing slashes. In some corner cases this led to unwanted results, though. Therefore we deleted the normalization and thus give projects full control over the URI prefixes. In order to achieve backward compatibility, you must delete any trailing slashes from your blueprint.site.mapping values. The Blueprint's default values had no trailing slashes even before this change. If you preserved this pattern, there is nothing to do.

  • CMS-3701: Workflow Server Registration

    The Workflow Server registers itself with the Content Management Server at startup time now. The Content Management Server no longer has to retrieve the Workflow Server's main CORBA IOR through HTTP. It is no longer necessary to set the property cap.server.workflow.server.url in the file contentserver.properties. In order to ensure a controlled startup sequence, the Workflow Server is registered only after all of its service and all of its custom managers have been started. This ensures that client see a fully initialized server, but it also means that custom manager cannot open a Unified API connection that connects back to its own Workflow Server during startup.

Prev Up Next
 Home