Deprecated, Obsolete and Restrictions
The following issues are deprecated, obsolete or restricted in Content Manager.
Generally, SDL provides platform support for up to two versions of any given platform to provide more flexibility in how organizations incorporate vendor changes. Typically, SDL provides support for the latest and previous version of a third party platform. This previous version is implicitly marked as deprecated.
- Since Content Manager 2016 (12.0.X)
-
- PreTranslation was promoted to a public interface as part of
<infoShareExtensionConfig>called<targetxmlfilegeneration>. Our implementation of PreTranslation based on this new interface is marked as deprecated. - BatchImport, visible in the Web Client's user interface Tools section, is marked as deprecated. More technically, background task implementation of handler
ISHBATCHIMPORTimplemented byISHBatchImport*.CBatchImportis deprecated. - BatchPerformAction, visible in the Web Client's user interface Inbox section or Reports, is marked as deprecated. More technically, background task implementation of handlers
BATCHPERFORMACTIONandRELEASETRANSLATIONSimplemented byISAuthor*.CInboxVieware deprecated. - Background task implementation of handler
DELETETRANSLATIONSis obsolete. - All programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced
IWrite*plugins as replacement forIOnDocStoreandICustomerFunction. In 11.0.1 we introduceIBackgroundTaskHandlerto replaceIEventHandler. This marks theIEventHandlerinterface as deprecated; andIOnDocStoreandICustomerFunctioninterfaces are obsolete as they are technically no longer available. - The support for the following software components is marked as deprecated in this release:
- Microsoft Windows 7
- Microsoft SQL Server 2012 (all service packs)
- Oracle RDBMs 11.2
- Microsoft Active Directory Federated Services 2.X (ADFS 2.0; part of Windows 2008R2/x64 and ADFS 2.1; part of Windows 2012/x64)
- JustSystems XMetaL 9.0
- <oXygen/> XML Author/Editor 16 (32 bit only)
- The support for the following software components is obsolete in this release:
- Microsoft Windows 2008R2/x64 (all service packs) as mainstream support ended January 2015
- Microsoft SQL Server 2008R2 (all service packs)
- Java 7 as support ended April 2015
- JustSystems XMetaL 8.0/8.0J
- <oXygen/> XML Author/Editor 15 (32 bit only)
- Arbortext Editor 5.X/6.X as standard support ended April 2015
- Adobe FrameMaker (all versions)
- Reusable Objects. Please contact SDL Support to discuss your usage and legacy conversion through deprecated API call
Document0bj20.GetDocObj. [TS-4673].
- PreTranslation was promoted to a public interface as part of
- Since Architect 2014 (11.0.X)
-
- All programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced
IWrite*plugins as replacement forIOnDocStoreandICustomerFunction. In 11.0.1 we introduceIBackgroundTaskHandlerto replaceIEventHandler. This marks theIEventHandlerinterface as deprecated; andIOnDocStoreandICustomerFunctioninterfaces are obsolete as they are technically no longer available. - Client Tools
Offlineworking mode is marked as deprecated. There are several technical challenges that don't allow us to offer the necessary experience and functionality in a mode when you are not connected to a repository. [TS-8796] - The legacy option to have Translation Management correct the status of all previous versions if a later version was released has been removed. This option was already deprecated since the introduction of the
FISHSTATUSTYPEfield. The option has been removed. - The usage of multiple contexts on either masters or publication versions through the
CTCONTEXTcard type is deprecated. All endpoints in UI and web services are already removed. - The support for the following software components is marked as deprecated in this release:
- Microsoft Windows 2008R2/x64 (all service packs)
- Microsoft SQL Server 2012
- Oracle RDBMs 11
- Adobe FrameMaker
- Arbortext Editor 5.4
- The support for the following software components is obsolete in this release:
- Microsoft SQLServer 2005 (all service packs)
- Microsoft SQLServer 2008 (all service packs)
- Oracle RDBMs 10.2.x (all versions) as Oracle Extended Support ends as of July 2013
- Microsoft Windows XP (all service packs) as Microsoft Extended Support ends as of April 8, 2014
- Microsoft Windows Vista (all service packs)
- JustSystems XMetaL 6.0/6.0J
- JustSystems XMetaL 7.0
- <oXygen/> XML Author/Editor 14 (32 bit only)
- Arbortext Editor 5.3
- Microsoft Internet Explorer 8
- Reusable Objects. Please contact SDL Support to discuss your usage and legacy conversion. [TS-4673].
- All programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced
- 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, but we continue to support the ASMX API in this release. The ASMX API will not be supported in the next release and as a result, customers using the ASMX API should start to consider upgrading to the new API.
- Since SDL Trisoft 2011R2 (9.2.X)
-
- Usage of single/double quotes in list of values like Statuses, UserGroups and UserRoles could lead to unexpected results in the Web Client. [TS-466]
- Object-level Access Control is not supported. Security settings can only be managed on the folder level, not on the object level.
- Size of fields is limited by the relevant data type in the database:
- Long: unrestricted
- Text: restricted to a length of 1333 bytes
- Since SDL Trisoft 2011 (9.0.X) or older
-
- "Pre-release" Translation Management is not included in this release
- No URN support for identifying metadata
- Export for publication
- Notification in the user interface if the set is not approved. This because multiple languages can be exported, and each of those can have a different status.
- Update packages.
- Recursive inheritance of metadata to lower levels other than labeling is not possible.
- Pre-Translation only on document component with XML as electronic Document Type (EDT).