An overview of breaking feature changes you might consider in case you upgrade to a new version. Breaking changes are not backward compatible and you might lose a functionality you have used before.

Changed behavior

Feature changes that are not backward compatible and might need some adaption of configuration or customizing.

Deprecated features

Feature deprecations are mentioned for a specific major version.

Features are then removed from the product in the following major version.


For more technological and development-related topics please check the changelog in the Developer Guide.


Change/Deprecation

Feature

Description

Why

2021.2.x

3D models preview

3D models preview

The following formats have been recently deprecated by their third-party providers:

  • .AWD
  • .BABYLON

The assets are still kept in censhare, but no preview is possible for the 3D models


2021.1

End of support for Solaris OS

Solaris OS for censhare ServerAs of version 2021.1, Solaris OS is no longer supported for censhare Server installations. censhare no longer delivers installation packages for censhare products and software bundles targeting Solaris OS, and no longer provides support in administration, maintenance, and IT or application support on Solaris OS installations.

3D models preview

3D models preview

The assets are still kept in censhare, but no preview is possible for any 3D models


2020.2




End of support: social media-related XSLT commands

Social media-related XSLT commands

XSLT commands to access API related to social media functionality (Facebook, Twitter, YouTube) like post text, image or video or retrieve post information. 

Full list of affected commands: 

Facebook:

  • <cs:command name=“com.censhare.api.facebook.GetFriends”>

  • <cs:command name=“com.censhare.api.facebook.Search”>

  • <cs:command name=“com.censhare.api.facebook.Get”>

  • <cs:command name=“com.censhare.api.facebook.GetInfo”>

  • <cs:command name=“com.censhare.api.Facebook.postVideo” returning=“:resultVariable”>

  • <cs:command name=“com.censhare.api.Facebook.postMessage” returning=“:resultVariable”>

  • <cs:command name=“com.censhare.api.Facebook.postLink” returning=“:resultVariable”>

  • <cs:command name=“com.censhare.api.Facebook.postPhoto” returning=“:resultVariable”>

Twitter:

  • <cs:command name=“com.censhare.api.twitter.search” returning=“:resultVariable”>

  • <cs:command name=“com.censhare.api.twitter.readMessages” returning=“:resultVariable”>

  • <cs:command name=“com.censhare.api.twitter.postMessage” returning=“:resultVariable”>

YouTube:

  • <cs:command name=“com.censhare.api.Youtube.GetVideoInfo”>

  • <cs:command name=“com.censhare.api.Youtube.ListVideoCategories”>

  • <cs:command name=“com.censhare.api.Youtube.uploadVideo” returning=“:resultVariable”>


In version 2020.2, we moved functionality connected to social media to the separate Social Media Service, which provides REST API. 

End of support: Internet Explorer

Support for Internet Explorer 11Running censhare web with Internet Explorer 11IE 11 is outdated and deprecated. We support Chromium Edge instead.

Removed: Angular usage

Angular usage in censhare WebIn censhare Web we enabled the usage of Angular for prototyping and proofs of concept.As Angular was never actively used in censhare Web, we decided to reduce complexity and remove the possibility to use that framework. Please ensure that all your implementations are Angular JS compatible.

2020.1

Deactived feature: Lionbridge Connector

Lionbridge ConnectorOrder process to send text content via a normalized interface to Lionbridge for translation. The feature is supposed to be an alternative to our own translation tools in case they are not sufficient.

The censhare – Lionbridge connection needs certification and the certification process and required enhancements are not cheap.

At the moment we have neither an active customer nor a prospect requesting a working Lionbridge connection.

In the future, we expect necessary adaptions to the Lionbridge interface when a later Lionbridge version is released which will cause changes in any case.

So we are "Lionbridge ready" which was prooved in a PoC already and we can pick up the actual connection including the certification at any time as soon as a customer is interested.

Please inform product-management@censhare.com in case you have a prospect to plan the next steps.

2019.3




New default setting: Asset Deletion 3

Asset Deletion 3Asset Deletion 3 removes asset versions including their asset files to keep the amount of consumed disk space as low as possible.

After consolidating the learnings from two previous versions of Asset Deletion and adding some input from our stakeholders, we decided to implement an improved concept of Asset Deletion.

The latest version of the Asset Deletion improves performance and supports PostgreSQL databases.

New default setting: SQL based flag calculation

Flag calculationThe flag calculation informs the users about updates in their layouts and helps to resolve the updates automatically.

After the previous implementation had some performance issues the flag calculation was refactored. Most probably you will not notice any issues but please test your flag calculation after upgrading just in case you have an edge case configured that might have some impacts.

New governance model: Mandatory domain structure

Master data / Domains

The new censhare standard product has a new domain setup that allows a consistent governance model. The domain structure is mandatory for the censhare Dedicated solution as well as any custom solution:

  • root. - Stores system-relevant module assets. This domain provides the core functions of the censhare platform. (access restricted to the system administrators).

    • root.global-share. - Stores production assets that are available to all below domains (read/write access for user roles according to the permission model)

    • root.common-resources. - Stores resource assets that are available to all below domains (read access for all user roles mandatory)

The new governance model separates system-relevant module assets from configuration module assets.

2019.1

Removed: Asset Deletion 2

Asset Deletion 2

Asset Deletion 2 removes asset versions including their asset files to keep the amount of consumed disk space as low as possible.

Asset Deletion 2 was replaced by an improved version of Asset Deletion 3. Asset Deletion 1 is still available as a fallback.

End of life: GWT Client and Java Web Start Client

GWT Client and Java Web Start Client

Browser-based client

Applets are required to use the GWT Client. Without them, the GWT Client will no longer work.

Applets are supported in Java SE 8 until March 2019, pending continued support by browser vendors, after which they may be removed at any time!

As soon as we migrate to Java SE 11, Web Start Client will not work any longer.

End of life: Protected client

Protected client

The Protected client is a specially built Java Client version, where the code is encrypted so that the client cannot be "hacked".

The Protected client is not working any longer due to the update to Java 11.

End of life: 32 bit Windows client

32 bit Windows client

Client version that is compatible with outdated operating systems.

The 32-bit Windows client is not working any longer due to the update to Java 11.

Java 6 versions of censhare clients

Java 6 versions of censhare clients


The official and extended support of Java 6 ended in December 2018.

2018.3

Deprecated: Translation with memory – old version

Translation with memory

Supports the user to translate text by suggesting content modules based on similarity.

The Translation with memory needed a more stable foundation and was refactored completely. The new version of the  Translation with memory is based on the same data model and combines existing and new functionality. Downport of new functionality and bug fixes for the old version will not be provided.

2018.2




Deprecated: Project Editor – old version

Project Editor

Calendar and Gantt chart view to plan tasks and campaigns

To enable automated task calculation the Project editor needed a more stable foundation and was refactored completely. The new version of the Project Editor is based on the same data model and combines existing and new functionality. Downport of new functionality and bug fixes for the old version will not be provided.

Discontinued: Java client dark mode

Java client dark mode

Dark look and feel for the Java client application.

As most of the users prefer the bright look and feel of the Java client we decided to focus on it. The dark mode is still available but not tested any longer and we will not accept bug reports regarding the dark mode any longer.

Changed behaviour: Text placements (InCopy and XML)

Text placements (InCopy and XML)

VFS links are automatically converted when opening a layout. They are then embedded as (inlined) text stories and permanently stored as such. After that, no VFS file links exist in the layout anymore. As of that, text placements are no longer displayed in the InDesign palette.

Re-opening an InDesign layout with the embedded InCopy stories will take less time as all VFS file links are replaced. The preview of all assets in the layout is thus completed much faster.