Documentation Center

Deprecated, Obsolete and Restrictions

The following issues are deprecated, obsolete or restricted in Content Manager.

Generally, RWS provides platform support for up to two versions of any given platform to provide more flexibility in how organizations incorporate vendor changes. Typically, RWS provides support for the latest and previous version of a third party platform. This previous version is implicitly marked as deprecated.

Since Content Manager 15
The support for the following product features has become obsolete in this release:
  • The Tridion Docs web client is replaced with the new Organize Space user interface.
  • The Batch Import tool has been removed from Content Manager following the recent improvement and development of Content Importer.
  • The pre-translation and pull translation functionality have been removed from Content Manager.
  • The DITA-OT reference output format IshHtmlHelp has been removed, because it no longer works with Java 17, the only supported Java version. Use the DITA-OT plugin for HTML Help instead.
  • The Collaborative Review feature (previously known as Reach) is now obsolete.
  • The Content Editor feature is now obsolete.
  • Content Manager 15.0.0 no longer uses COM+ or Classic ASP technology. Apart from the email notification feature, which is now obsolete, all other functionality using these technologies has been reimplemented.
  • The User Generated Content (UGC) feature of Content Delivery is obsolete as from Tridion Docs 15. As a result, the Commenting Dashboard on the Content Manager side and commenting in DXA for Dynamic Documentation are obsolete. The Commenting Dashboard that was available in the web client is not available in its replacement, Organize Space.
Furthermore, the following features have been limited:
  • In the new Organize Space user interface, you can request a push translation only for a publication. A push translation for a map can now only be requested through the Content Manager API.
The support for the following software components is deprecated in this release:
  • Tridion Docs Content Delivery (DXD/UDP) 11.1.0
  • Tridion Docs Content Delivery (DXD/UDP) 11.5.0
  • SDL Tridion Sites 9.1
  • SDL Tridion Sites 9.5
  • TMS 12.4.x
  • TMS 12.5.x
  • WorldServer 11.5.x
  • WorldServer 11.6.x
  • Microsoft Windows 10
  • JustSystems XMetaL 14.0 x64
  • Syncro Soft Oxygen XML Author 23.x x64
  • Microsoft Windows Server 2019 x64
  • SmartLogic Semantic Enhancement Server 3.7.3
The support for the following software components is obsolete in this release:
  • Tridion Docs Content Delivery (UDP) 10.1.1
  • Microsoft Windows Server 2016 x64
  • Microsoft Windows 8.1 x64
  • Microsoft Windows 8.1 x86
  • Microsoft SQL Server 2017 (Standard Edition or Enterprise Edition)
  • Microsoft SQL Server 2016 SP2 (Standard Edition or Enterprise Edition)
  • Microsoft SQL Server 2016 SP1 (Standard Edition or Enterprise Edition)
  • Oracle Database 12.2 (12.2.0.1)
  • Oracle Database 12c (12.1.0.2.0)
  • Oracle Data Access Client (ODAC) 19c (19.3.0.0)
  • Microsoft OLE DB Driver for SQL Server
  • Eclipse Temurin OpenJDK 11 (18.9 LTS release)
  • Oracle Java Development Kit 11.0.x x64 also known as 18.9 LTS
  • .NET Runtime 4.7.2
  • JustSystems XMetaL 13.0 x64
  • JustSystems XMetaL 13.0 x86
  • JustSystems XMetaL 12.0 (Japanese) x64
  • JustSystems XMetaL 12.0 (Japanese) x86
  • JustSystems XMetaL 12.0 x64
  • JustSystems XMetaL 12.0 x86
  • Syncro Soft Oxygen XML Author 21.1 x64
  • PTC Arbortext Editor (any version)
Security Token Service for externalized authentication and Single Sign-On is deprecated as of Tridion Docs 15. We recommend that you configure all identity providers through the Access Management application. The exceptions are WCF .SVC web services, which will continue to use STS for this release.
Since Content Manager 14 SP4
The support for the following software components is deprecated in this release:
  • DITA-OT reference output format IshHtmlHelp
  • Pull translations functionality
  • Oxygen v20 and below.
Since Content Manager 14 SP3
The support for the following software components is deprecated in this release:
  • Arbortext Editor
  • Condition Management - Synchronize functionality
Since Content Manager 14 SP2
The UGC feature of Content Delivery is deprecated as of Tridion Docs 14 SP2. As a result, the Commenting Dashboard on the Content Manager side and commenting in DXA for Dynamic Documentation is also deprecated.
The pre-translation feature is obsolete. The Translation management extension where pre-translation relies on, through interfaces like ITargetXmlFileGenerateContext and siblings, is also deprecated as of Tridion Docs 14 SP2. Note that Collective Spaces does not respect the Translation Management extension interface (deprecated) - so in practice purging pre-translation is simply not happening and Collective Spaces doesn't know how to handle <pretranslation> tags.
The support for the following software components is deprecated in this release:
  • Microsoft SQL Server 2017
  • Windows 8.1
  • <oXygen/> 17.1
The support for the following software components is obsolete in this release:
  • Oracle Client 12.1.0.1.2
  • ODAC 12.2.0.1.1
  • Microsoft Windows 7
  • Microsoft .NET Runtime 4.6.1
  • Oracle Java 10
  • Arbortext 7.0
  • <oXygen/> 16
  • SDL Web 8.5 no longer supported over TridionSitesTaxonomy connector
  • SDL WorldServer 10.x.x no longer supported by Translation Organizer
Since Content Manager 14 SP1
Integrations to the Collaborative Review component (previously also known as Reach) are disabled in the user interface and configuration. This means no Collaborative Review originating comments in Publication Manager, no possibility to publish or synchronize to Collaborative Review and more. The component Collaborative Review was deprecated earlier. The alternative is Collective Spaces, Review Space in particular.
Since Content Manager 14
The Batch Import tool is now obsolete. This feature have been removed from Content Manager following the recent improvement and development of Content Importer.
The support for the following software components is deprecated in this release:
  • Content Delivery (UDP) 10.1.1
  • SDL TMS 11.0.x through 12.1.x
  • SDL WorldServer 11.0.x through 11.3.x
  • SDL XPP 9.1
  • JustSystems XMetaL 12 (Japanese) (64-bit) support files
  • SyncroSoft <oXygen/> XML Author 20.0 (64-bit) support files
  • Microsoft Windows 2016 SP1 (64-bit)
  • Oracle RDBMS 12.2.0.1
  • Microsoft SQL Server 2016 SP1
  • Microsoft SQL Server 2016 SP2
  • Eclipse Temurin OpenJDK 11 (formerly known as AdoptOpenJDK OpenJDK 11) with Hotspot 11.0.0+28 (64-bit)
  • Eclipse Temurin OpenJDK 11 (formerly known as AdoptOpenJDK OpenJDK 11) with Hotspot 11.0.3+7 (64-bit)
  • AntennaHouse XSL Formatter 6.5 and 6.6
  • Microsoft Edge (Spartan/LegacyEdge)
The support for the following software components is obsolete in this release:
  • Microsoft Windows Server 2012R2 (64-bit)
  • Windows 8
  • Microsoft Windows PowerShell 5.0 (part of Windows Management Framework 5.0)
  • .NET Runtime 4.6.1
  • <oXygen/> XML Author 19.1 (64-bit)
  • Internet Explorer (all versions)
Since Content Manager 13 SP2

Due to the complete removal of legacy code from Content Manager 13.0.2, the earliest version from which you can upgrade directly to Tridion Docs 13 SP2 is SDL LiveContent 2013 (released with Architect 10.0.0). Upgrading from earlier versions requires that you first upgrade to SDL Knowledge Center 2016 (released with Content Manager 12.0.0).

The support for the following software components is obsolete in this release:
  • Microsoft SQL Server 2014
  • Java Runtime 10.0.1 (64-bit)
  • Java Development Kit 10.0.1 (64-bit)
  • Eclipse Help (output format)
Since Content Manager 13 SP1

There are exceptional evolutions for software support in the 13 SP1 release. One of them is the new support for 64-bit versions of XML Editors and at the same time the obsolescence of any 32-bit versions of those tools.

Because of the changes in software support, upgrading to Content Manager 13.0.1 from any earlier version makes the following versions obsolete:
  • Windows 7 32-bit
  • JustSystems XMetaL 10.0 / 10.0 (Japanese) (32-bit)
  • JustSystems XMetaL 11 and any 32-bit version
  • <oXygen/> XMLAuthor/Editor 17 and any 32-bit version
  • Arbortext Editor 7.0 and any 32-bit version
Since Content Manager 13
Translation review flow:
  • The simple translation review flow, without the approval step, is deprecated when WorldServer and TMS are set with a REST API protocol. It is however possible to maintain the old flow removing the approval steps from the out-of-the-box version of the flow.
  • The simple flow without the approval step should be used with the file system or when WorldServer is set with a SOAP API protocol. Whenever 'rejected' objects need to be sent again for translation, however, you need to either submit everything again for translation with the Include items already sent... checkbox selected, or manually change the rejected topics' status to In translation.
  • In all cases, it is no longer possible to send Only previously rejected translation items.
The support for the following software components is obsolete in this release:
  • Microsoft Windows 2008R2/x64 SP0/SP1
  • Oracle RDBMs 11.2
  • Microsoft SQLServer 2012 SP3
  • JustSystems XMetaL 10.0
  • JustSystems XMetaL 10.0 Japanese
  • <oXygen/> XMLAuthor/Editor 16
  • Microsoft Internet Explorer 10
Since Architect 2013 (10.0.x)
  • Reusable Objects are marked as deprecated, Support will be removed from the code base. Please contact SDL Support to discuss your usage and legacy conversion. [TS-4673]
  • Index Terms are Obsolete [TS-1232]
  • Limited Batch Metadata Operations [TS-768]
  • Client Tools using SSL might crash when using a URL that does not match the certificate
  • Authoring Bridge for XMetaL on Windows Vista/7 machines you have to have full access to folders C:\Program Files (x86)\Common Files\XMetaL Shared and C:\Program Files (x86)\XMetaL 6.0 before doing the installation.
  • The new WCF Web Services API deprecates the previous ASMX API. Although we continue to support the ASMX API in this release, it may be dropped in the next release. We strongly advise customers using the ASMX API to consider upgrading to the new API.