close

Filter

loading table of contents...

Release Notes / Version 13.2512.0

Table Of Contents

CoreMedia Core

Workflow Action Exception Logging

Fixed a bug in the logging of some workflow action exceptions where the underlying cause was not visible.

(CMS-28851)

XLIFF-Import: Relaxed xlink:href and xlink:role Validation

When importing XLIFF that includes a CoreMedia Rich Text 1.0 property value having an anchor with href like href="https://", you may have observed an error such as:

[Fatal Error] cvc-datatype-valid.1.2.1: 'https://' is not a valid value for 'anyURI'.

The cause is a mismatch between the CoreMedia Rich Text 1.0 specification (given as DTD) and the XLink namespace, thus, CoreMedia Rich Text 1.0 allows any string value as xlink:href while the XLink schema-based namespace does not.

As fix to grant that “any exported CoreMedia Rich Text 1.0” can be imported again as XLIFF, we relaxed the schema validation for xlink:href and also for a comparable mismatch in xlink:role.

No adaptations to existing XLIFF files are required.

(CMS-28696)

Deprecated Remote Client Actions

Remote client actions for workflows have been deprecated. There are no clients implementing this API anymore except the workflow-server itself.

To this end the AbstractClientAction and all derived classes have been deprecated for removal, as they come with some unnecessary overhead like timeouts, potentially causing issues during execution.

The ApproveResources and PublishResources Actions have been re-implemented as Approve and Publish, based on LongActionBase. If you implemented actions based on AbstractClientAction yourself, please also consider migrating them to extend LongActionBase instead.

The built-in workflows studio-simple-publication.xml and studio-two-step-publication.xml have been adjusted to use the new Actions, so you should re-upload these workflows. Please consider updating usage of these actions in your own custom workflows in the same way.

(CMS-27908)

Increased Maximum Content-Type Name Lengths

Allowed maximum content-type name lengths got increased from 18 to 56 for all supported databases.

(CMS-27798)

Extended Output of cm dump Tool for Workflow Processes

The cm dump and the cm processes --verbose command-line tools were extended to output more data about workflow processes. The output now includes “task states”, “task escalation exceptions”, and “task warnings”. This can be helpful to analyze the current state of a running workflow, including errors that happened during the execution of a workflow task.

Previously, such information was only written if these tools were used to dump the workflow tasks itself, for example if cm dump was called with a task id, cm dump --verbose was used to dump a process, or with cm processes --very-verbose.

(CMS-25759)

Fixed Bug In Integrated Workflow Conversion With PostgreSQL

Integrated workflow conversion (enabled in the workflow-server with workflow.server.enable-workflow-converter=true) has been fixed for PostgreSQL.

(CMS-25566)

Archive Broken Workflow Definitions

Parameter -A has been added to the workflowconverter which can be used to potentially keep broken workflow definitions for usage in the workflow archive, so that already archived workflows of a broken workflow definition can still be accessed.

For details, please see section “Workflowconverter” in the Workflow Manual.

(CMS-23988)

Optionally Pass Authentication Data for Content Server's HTTP Endpoints in Request Header Fields

Each Content Server provides HTTP endpoints for blob up- and download as well as for processor usage data. These are internally used endpoints that are not supported for use by custom clients. You may configure whether authentication data for those endpoints is to be sent as part of the URL (which was the only way prior to CMCC 13) or as a request header field. While sending the token as a query parameter is inherently insecure, it is the default to keep backward compatibility. Unless connection to an older server (prior to CMCC 13) is required, it is recommended to set these properties to false.

See Deployment Manual, section 4.4.7 Securing Session Authentication for Content Server HTTP Endpoints for details of configuration.

(CMS-16480)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.