CoreMedia DXP Release Notes, Version 7.5.44-17
2.2. Improvements and Changes | 2.2.19. Release 7.5.26

The Freemarker Library was updated to patch version 2.3.22.

Also, the Freemarker Configuration is now initialized with the "incompatible_improvements" Flag set to "2.3.22" (was "2.3.20") since some of the bug fixes and performance improvements are only used when updating the version for this flag. While this change did not cause any problems with the sites contained in the Blueprint, it may cause problems with custom templates, so this version is now configurable using the Spring Property "freemarker.incompatible_improvements".

It's now possible to run the defaultFlowRunner directly which will re-throw Exceptions thrown by org.springframework.webflow.mvc.servlet.FlowHandlerAdapter in order to implement behaviour relying on specific exceptions. exceptionHandlingFlowRunner will use defaultFlowRunner and catch all Exceptions, just like the now deprecated "flowRunner" bean did. (see webflow-services.xml)

The studio library's performance when opening very large folders has been improved. Loading a document contained in the folder from the content server to the studio backend is now delayed until the document's properties are first accessed.

The Blueprint Maven site generation and deployment is skipped by default because the Blueprint does not contain any site content.

Additional CMCSS and CMJavaScript can be added to sites for Preview only. In order to use the feature add CMCSS to Link List setting "previewCss" or CMJavaScript to Link-List setting "previewCss" of a channel.

LiveContext for IBM WebSphere Commerce is successfully tested against IBM APAR JR52306 - Mandatory cumulative interim fix for WebSphere Commerce Version 7 Fix Pack 8/9

The LiveContext implementation for IBM WCS now uses the REST handlers of the IBM Commerce Search Servers to retrieve category and product information by default when FEP7+ is used. This speeds up initial loading and re-loading of product and category data in case of cache misses. A list of the URLs used can be found in the CoreMedia LiveContext 2.0 for IBM WebSphere Commerce manual.

CMS-3467: Timetravel in Studio now correctly sends selected timezone to IBM Commerce and in Fragment Requests

The Timetravel functionality in Studio allows users to set a date, a time and a timezone. The LiveContext extensions now correctly sends the selected timezone to IBM Commerce in the PreviewToken REST requests and thus ensures that IBM Commerce uses the correct time. Additonally, the preview date/time is now correctly send back in fragment requests from IBM Commerce to CoreMedia CAE. Nevertheless, in cases where the Studio user selects a different timezone than the timezone of the IBM Commerce server, the user must take care of calculating the correct offset for previewing IBM Commerce data. Especially Marketing Web Activities that use date/time as constraint, only rely on the IBM-server timezone. E.g. in Demo Cloud the timezone is UTC (GMT+0) without Daylight Saving Time (DST). Thus when using timezone 8pm Europe/Berlin in Studio, the actual IBM Commerce time is 6pm (during summertime with DST). Unfortunately, IBM does not offer different timezones to be used in Web Activities.

CMS-3377: Asset Management Extension now uses Blueprint ValidationService

The Asset Management Extension now filters pictures according to the Blueprint ValidationService. Example: a Picture with a future validFrom date is filtered out until it is valid. If no valid picture is found for a concrete SKU (e.g. Mickey Mouse Shirt in XL white), the fallback is to get valid pictures for the "main" product (e.g. Mickey Mouse Shirt). If the "main" product does not have any valid pictures, the "missing product picture" is shown.

CMS-3361: Timetravel for eSpots commerce-led not working

Timetravel for eSpots in commerce-led scenarios now also work if the CMS renders the eSpot in a fragment. The timetravel datetime is now correctly passed from CMS to WCS and back to CMS in the fragment request.

CMS-3348: Adjusted minimum system requirements documentation

Documentation of the minimum system requirements for a development setup were increased to realistic values

CMS-3316: Exit codes of XML Importer

If you use an XML importer in automated setup scripts, you might like to get a useful exit code rather than scanning the logfile for errors and warnings. However, the importer API did not enable custom Transformers and MultiResultGenerators to control the exit code in case of recoverable errors so far. Now the AbstractTransformer (existing class) and the AbstractMultiResultGenerator (new class, recommended to be used as base class for custom MultiResultGenerators) provide methods suggestExitCode for this usecase. For details see the API documentation of the methods. Why do we speak of "suggest"? There is only one exit, so if the methods are invoked multiple times, only one suggestion can win. Moreover, in case of severe errors, the importer still sets its own error exit code.

CMS-3180: CAE Feeder recovers from database connection failures

The CAE Feeder and the Proactive Engine are now able to recover from database connection problems. If the connection to the database has been lost, they will keep retrying database calls until the connection has been restored.

CMS-3141: Added var parameter of lc:include tag to documentation

The LiveContext manual now contains a description of the var parameter of the lc:include tag.

CMS-3124: FragmentConnector uses Live CAE if preview is launched from Management Center

CoreMedia FragmentConnector now correctly uses Preview CAE when launching store preview from IBM WebSphere Commerce Management Center.

CMS-2842: Using JSP Taglibs in Freemarker does not work out-of-the-box in Servlet 3.0 webapps

After updating to Freemarker 2.3.22, it is now possible to import TLD files placed under servlet 3.0 paths. To activate this new behaviour, a system property must be set. See Freemarker Documentation for details. It is still recommended to re-implement JSP taglibs as Freemarker Functions / Macros instead of reusing JSP Taglibs.

CMS-2707: Studio Library Toolbar: File Upload

If a user has no right to upload content in the selected folder, the upload file button in the library toolbar is disabled. For uploading content to a manually entered folder path you can still use Upload Files entry in the Create Content menu.

CMS-1102: IE: Richtext Context Menu rendered at wrong position when scrolled

In a RichText field, Studio shows context menus for images and links. When using Internet Explorer and the RichText content has been scrolled, the context menu appeared at a wrong position. Now, the scroll offset is also taken into account in IE.