SDL Knowledge Center Release Notes

SDL Knowledge Center 2016 SP4

June 2017 Legal notice

SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request.

All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL.

SDL Knowledge Center is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred.

This product may include open source or similar third-party software, details of which can be found by clicking the following link: Acknowledgments on page 0 .

Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.

To the maximum extent permitted by law, SDL Group shall not be liable in contract, tort (including negligence or breach of statutory duty) or otherwise for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software Documentation even if such losses and/or damages were foreseen, foreseeable or known, for: (a) loss of, damage to or corruption of data, (b) economic loss, (c) loss of actual or anticipated profits, (d) loss of business revenue, (e) loss of anticipated savings, (f) loss of business, (g) loss of opportunity, (h) loss of goodwill, or (i) any indirect, special, incidental or consequential loss or damage howsoever caused.

All Third Party Software is licensed "as is." Licensor makes no warranties, express, implied, statutory or otherwise with respect to the Third Party Software, and expressly disclaims all implied warranties of non-infringement, merchantability and fitness for a particular purpose. In no event will Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct, actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and on any theory of liability.This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties acknowledge that this is a reasonable allocation of risk.

Information in this documentation, including any URL and other Internet Web site references, is subject to change without notice. Without limiting the rights under copyright, no part of this may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of SDL Group.

ii SDL Knowledge Center Release Notes Contents

1 Welcome to Knowledge Center Release Notes ...... 1

Customer support ...... 2

Acknowledgements ...... 2

2 Release Notes - SDL Knowledge Center ...... 7

What's New in Content Manager ...... 8 New and changed ...... 8 New and changed in version 12.0.4 ...... 8 Client tool changes ...... 8 New and changed in version 12.0.3 ...... 9 New third-party software support ...... 9 New and changed in version 12.0.1 ...... 10 New third-party software support ...... 10 Client tools changes ...... 10 Content Editor changes ...... 11 Typical Server Vanilla Installation using ISHDeploy ...... 12 Translation Flow and Integration Improvements ...... 13 New and changed in version 12.0.0 ...... 14 Rebranding in SDL Knowledge Center 2016 ...... 14 New third-party software support ...... 15 Client Tools changes ...... 16 Content Editor changes ...... 18 Typical server installation changes ...... 21 Database layer changes ...... 24 Web client security ...... 26 Taxonomy/ontology integration ...... 27 Publish throttling by raising different event types per output format . . . . . 29 Publish pipeline changes ...... 31 Translation Flow and Integration Improvements ...... 32 PushTranslation flow comparison between 11.0.0 and 12.0.0 ...... 35 Background Task ...... 36 Federated Services changes ...... 37 Programmer's Interface Changes ...... 41 Prevent automatic document title overwriting during import ...... 46 API changes ...... 47 Fixed issues ...... 50 Fixed issues in version 12.0.4 ...... 50 Fixed Issues in 12.0.4 Web Client ...... 51 Fixed Issues in 12.0.4 Client Tools ...... 51 Fixed issues in 12.0.4 Content Editor ...... 52

SDL Knowledge Center Release Notes iii Fixed issues in 12.0.4 Web/App/Db server ...... 52 Fixed issues in version 12.0.3 ...... 52 Fixed Issues in 12.0.3 Web Client ...... 52 Fixed Issues in 12.0.3 Client Tools ...... 53 Fixed issues in 12.0.3 Content Editor ...... 53 Fixed issues in 12.0.3 Web/App/Db Server ...... 54 Fixed issues in version 12.0.1 ...... 54 Fixed Issues in 12.0.1 Web Client ...... 54 Fixed Issues in 12.0.1 Client Tools ...... 55 Fixed Issues in 12.0.1 Authoring Bridge ...... 56 Fixed Issues in Content Editor ...... 56 Fixed Issues in 12.0.1 Web/App/DB Server ...... 59 Fixed issues in version 12.0.0 ...... 60 Fixed Issues in 12.0.0 Web Client ...... 60 Fixed Issues in 12.0.0 Client Tools ...... 61 Fixed Issues in 12.0.0 Authoring Bridge ...... 65 Fixed issues in 12.0.0 Content Editor ...... 67 Fixed issues in Content Manager version 12.0.0 Web/App/Db server ...... 68 Fixed Issues in 12.0.0 Documentation ...... 78 Known Issues ...... 78 Deprecated, Obsolete and Restrictions ...... 86 Software compatibility across releases ...... 89 Content Manager API compatibility across releases ...... 99

What's new in Content Delivery ...... 113 New and changed ...... 113 New and changed in version 7.5.0 ...... 113 New and changed in version 7.4.0 ...... 114 Fixed issues ...... 115 Fixed issues in version 7.5.0 ...... 115 Fixed issues in version 7.4.0 ...... 117 Known Issues ...... 117 Deprecated, Obsolete and Restrictions ...... 118

iv SDL Knowledge Center Release Notes 1

Welcome to Knowledge Center Release Notes 1 Welcome to Knowledge Center Release Notes

This document contains the complete Release Notes for SDL Knowledge Center 2016 SP4.

Customer support

To contact Technical Support, connect to the Customer Support Web Portal at https://gateway.sdl.com and log a case for your SDL product. You need an account to log a case. If you do not have an account, contact your company's SDL Support Account Administrator. Acknowledgements

SDL products include open source or similar third-party software. 7zip Is a file archiver with a high compression ratio. 7zip SFX Modified Module The SFX Modified Module is a plugin for creating self-extracting archives. It is compatible with three compression methods (LZMA, Deflate, PPMd) and provides an extended list of options. Reference website http://7zsfx.info/. Apache Ant Apache Ant is a Java library and command-line tool whose mission is to drive processes described in build files as targets and extension points dependent upon each other. The main known usage of Ant is the build of Java applications. Ant supplies a number of built-in tasks allowing to compile, as- semble, test and run Java applications. Ant can also be used effectively to build non Java applications, for instance C or C++ applications. More generally, Ant can be used to pilot any type of process which can be described in terms of targets and tasks. DockPanel Suite .Net Docking Library for Windows Forms DITA-OT The DITA Open Toolkit is a Java-based implementation of the OASIS DITA Technical Committee's specification for DITA DTDs and schemas. It contains ANT, SAXON,... Apache FOP Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF. GeckoFX Gecko is a free and open source layout engine used in many applications developed by the Mozilla Foundation and the Mozilla Corporation (notably the Firefox web browser). globalize JavaScript globalization and localization. Formats and parses strings, dates and numbers in over 350 cultures.

2 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1

GNU Aspell GNU Aspell is a Free and Open Source spell checker designed to eventually replace Ispell. It can either be used as a library or as an independent spell checker. Its main feature is that it does a superior job of suggesting possible replacements for a misspelled word than just about any other spell checker out there for the English language. Unlike Ispell, Aspell can also easily check documents in UTF-8 without having to use a special dictionary. Aspell will also do its best to respect the current locale setting. Other advantages over Ispell include support for using multiple dictionaries at once and intelligently handling personal dictionaries when more than one Aspell process is open at once.

Specifically we are using GNUASpell dictionaries for de-CH, de-DE, en-CA, en-GB, en-US, es-ES, fr-FR, fr-CH, nl-NL. google-code-prettify google-code-prettify is a Javascript module and CSS file that allows syntax highlighting in an html page. Hunspell Hunspell is the spell checker of LibreOffice, OpenOffice.org, Mozilla Firefox 3 & Thunderbird, Google Chrome, and it is also used by proprietary software packages, like Mac OS X, InDesign, MemoQ, Opera and SDL Trados Studio. InstallAnywhere InstallAnywhere is the leading multi-platform development solution for application producers who need to deliver a professional and consistent cross installation experience for physical, virtual and cloud environments. From a single project file and build environment, InstallAnywhere creates reliable installations for on-premises platforms - Windows, Linux, Apple OS X, Solaris, AIX , HP-UX, and IBM iSeries - and enables you to take existing and new software products to a virtual and cloud infrastructure. Jetty The Jetty Web Server provides an HTTP server and Servlet container capable of serving static and dynamic content either from a standalone or embedded instantiations. Starting from Jetty version 7, the Jetty webserver and other core compoments are hosted by the Eclipse Foundation. jQuery jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. jquery-cookie jQuery plugin for reading, writing and deleting cookies. jQuery Highlight Highlights the search keywords/terms in a preview. jQuery UI jQuery UI is a set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library. jSON-js JSON is a light-weight, language independent, data interchange format. See http://www.JSON.org / The files in this collection implement JSON encoders/decoders in JavaScript. JSON became a built-in feature of JavaScript when the ECMAScript Programming Language Standard - Fifth Edition was adopted by the ECMA General Assembly in December 2009. Most of the files in this collection are for

SDL Knowledge Center Release Notes 3 1 Welcome to Knowledge Center Release Notes

applications that are expected to run in obsolete web browsers. For most purposes, json2.js is the best choice. Json.NET Json.NET is a popular high-performance JSON framework for .NET. Knockout JavaScript library Knockout is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), KO can help you implement it more simply and maintainably. Apache Lucene, SOLR The Apache Lucene™ project develops open-source search software. MVC Web Projects Auxiliary MVC Web Project libraries to serve ISHCM and ISHSTS. Typical libraries like WebGrease, StringTemplate (antlr3), AutoMapper, RouteDebugger, WebActivator,... NHunspell NHunspell brings the spell checking, hyphenation and thesaurus to the Microsoft® .NET Framework. NHunspell is C# library and wraps native libraries for Hunspell, Hyphen and MyThes. One design goal of this library and wrapper is to keep the source code of the included libraries as unmodified as possible. New versions of the base libraries can therefore easily adopted to NHunspell.

The integrated libraries are used in OpenOffice and they work with the dictionaries published on OpenOffice.org. Red Hat Linux Red Hat Enterprise Linux OpenStack Platform delivers an integrated foundation to create, deploy, and scale a secure and reliable public or private OpenStack cloud. Red Hat Enterprise Linux OpenStack Platform combines the world's leading enterprise Linux and the fastest-growing cloud infrastructure platform to give you the agility to scale and quickly meet customer demands without compromising on availability, security, or performance. Rx .NET Reactive Extensions for .NET library used to validate entered values Xalan-Java Xalan-Java is an XSLT processor for transforming XML documents into HTML, text, or other XML document types. It implements XSL Transformations (XSLT) Version 1.0 and XML Path Language (XPath) Version 1.0 and can be used from the command line, in an applet or a servlet, or as a module in other program. Thinktecture IdentityServer Front-end Secure Token Service to serve SAML tokens. Apache Tomcat, Tomcat Embed Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. WiX The WiX toolset builds Windows installation packages from XML source code. The tool-set integrates seamlessly into build processes.

4 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1

Apache Xerces The Apache Xerces Project is responsible for software licensed to the Apache Software Foundation intended for the creation and maintenance of: • XML parsers • related software components XULRunner XULRunner is a runtime environment developed by the Mozilla Foundation to provide a common back-end for previewing.

SDL Knowledge Center Release Notes 5 1 Welcome to Knowledge Center Release Notes

6 SDL Knowledge Center Release Notes 2

Release Notes - SDL Knowledge Center 2 Release Notes - SDL Knowledge Center

This section describes all that is new and changed in SDL Knowledge Center's capabilities and client tools for this version. What's New in Content Manager

For this release, Content Manager has these new features that support SDL Knowledge Center functionality.

New and changed

New or changed features and functionality from Content Manager are described.

New and changed in version 12.0.4

An overview of new features and enhancements, as well as improved or changed functionality in Content Manager 12.0.4, compared to the previous version of the product.

Client tool changes

Client tools improvements for this version are explained.

Client Tools user interface is now available in Chinese

The client tools user interface labels have been translated to Chinese. Also the necessary server side resources like error messages are available. [TS-11682]

Improved all Client Tools properties of Date/DateTime behavior

By default, the date control initializes itself with the current date and time. When using the variable currentdate only the current date is set and time is always defaulted to 00:00:00. Because the time is set at midnight, the date can easily shift in different time zones. Dates should always have a time component. In a globalized world, dates always have to be adapted to the time zone. So, when changing time zones, it is always possible that the date shifts a day, even two. The advice is to use type typedatetime over typedate.

The operator (Any) specifies that any date and/or time is allowed. Basically, the criteria is ignored when searching. We now disable the entry to avoid confusion. Also after typing a date in the value panel, the value will be retained, when setting the focus to another control. Before the value in the value panel was set to the current date. [TS-12526|TS-12404]

8 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2

Improved location and focus when a Publication Manager table of contents refresh happens

The usability of Publication Manager has been greatly improved like improved navigation in the publication tree (left pane of the Content tab), and optimization of the zooming results. [TS-12101|TS- 12304] • Checking in a topic no longer closes opened nodes. [TS-12304|SRQ-59151|SRQ-5932|SRQ-6535| SRQ-6634] • Changing the version of topics no longer closes opened nodes. [TS-12305] • Checking in a map containing topic groups no longer closes opened nodes. [TS-12347|SRQ-5915| SRQ-5932|SRQ-6535|SRQ-6634] • Saving a publication no longer moves the tree regardless of the selected object. [TS-12358] • Moving a topic with the Move commands (from the right-click menu) no longer hides the topic: the moved topic stays visible. [TS-12369]

New and changed in version 12.0.3

An overview of new features and enhancements, as well as improved or changed functionality in Content Manager 12.0.3, compared to the previous version of the product.

New third-party software support

Support for databases, operating systems and XML editors has been updated.

This has a number of consequences: • Classic .ASP files, .VBS files and COM+ DLLs are modified. Typically MSXML2.DOMDocument. 4.0 becomes MSXML2.DOMDocument. 6.0 with extra configuration for optional resolveExternals or validateOnParse properties where required. • It breaks COM+ DLLs binary compatibility. However, COM+ interface became obsolete in Knowledge Center 2014 SP1. • ConvertStyles. bat implementation changed from MSXSL.EXE to xslTransform. vbs. • Obsolete pages regarding IndexTerms and ClassicASP implementation of PreviewExternal are removed. • Custom files are changed (e.g. Rep*Dlg.asp). Therefore you need to remove the MSXML4

SDL Knowledge Center Release Notes 9 2 Release Notes - SDL Knowledge Center

dependency for your custom pages.

New and changed in version 12.0.1

An overview of new features and enhancements, as well as improved or changed functionality in Content Manager 12.0.1, compared to the previous version of the product.

New third-party software support

Support for databases, operating systems and XML editors has been updated.

Client tools changes

Client Tools improvements for this version are explained.

Publication Manager content refresh message can now be dismissed

The blocking modal dialog in Publication Manager stating The object 'some-title' has been changed by another application, and the new content has been loaded. can happen frequently and requires a lot of extra clicking. By adding an optional checkbox Don't show this dialog again for this session on that dialog you can chose to no longer see this information dialog appear for the duration of your application session. [TS-11441|TS-10709|SRQ-1893|SRQ-3032|SRQ-4409|SRQ-1674] Note however that the message is there to indicate that a refresh information is about to happen in Publication Manager. • For images and topics, it typically comes down to a refresh of the preview window. • For maps, it can be the preview window, but it can also force a refresh on the tree (TOC). As this could be a small or really big refresh operation (e.g. removing or adding many links), this might take a while.

10 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2

Syncro Soft XML Author

For regular sized DITA Maps, we originally did a preprocessing step to make sure the required information is retrieved from the CMS in batch. Pushing data sizes up to a map holding up to 2500 means that the blocking preprocessing step takes up quite a lot of time thereby blocking several editor actions. The chosen solution was to step-away from the synchronous preprocessing step. Mixing in client- server distance/network-latency and map size (>2000 ); the blocking preprocessing was perceived as a unwanted experience. The chosen solution was to step-away from the synchronous preprocessing step. When opening the large map in the Map Editor view, the UI should not freeze/wait until all the topics referenced in the map are downloaded. Only the referenced topics visible in the Map Editor view should be downloaded. When scrolling down in the Map Editor view, the next batch of referenced topics should be downloaded. [TS-11315]

JustSystems XMetaL 11

Introducing JustSystem XMetaL 11 support. The first XMetaL version with full Windows 10 operating system support. Note that we only support the 32-bit edition, and require patch version 11.0.0.083 or later. We support their significantly improved new Map Editor which has multi-level undo, and is integrated with Attribute Inspector.

Verified Acrolinx on top of AuthoringBridge for JustSystems XMetaL 11

Verified that the JustSystems XMetaL 11 integration Content Manager Authoring Bridge works together with Acrolinx. The XMetaL server-side files are enriched with statements needed by Acrolinx in the DTD-related macro files for XMetaL 11. These files are synchronized from the server. If Acrolinx is not installed on the client, these statements will just be ignored by XMetaL. We used the Acrolinx Plug-in for XMetaL 4.7.0 build 5 (client_XMetaLV4. 7_B5.32_bit.msi) to verify the behavior. [TS-11376|TS- 11356]

Content Editor changes

A description of the new and improved editor behavior that you can expect with this release. Improved copy/paste- XML support on the clipboard With this version, we put the XML structure on the system clipboard when copying in Content Editor. This enables users to copy from one document to another without the loss of any information. In the old situation, sometimes information about the structure was lost since content was copied as HTML, and converted back into XML upon pasting into the editor. As not all structures that can be described in XML can be represented in HTML, this extra conversion caused the content to be pasted differently than expected.This problem was especially noticeable when copying and pasting tables. New documentation for implementers With this release we've included a new Customization section in the product documentation (http://docs.sdl.com/ContentEditorCustomization ). This section is written with the intention to help you understand the possibilities and get started implementing Content Editor. Previously, we just provided API and configuration references. A new dialog when you are pasting large amounts of content To improve the user experience, if it is expected to take more than 1.5 seconds to paste content, then we now show a dialog to inform the user that the application is busy pasting content.

SDL Knowledge Center Release Notes 11 2 Release Notes - SDL Knowledge Center

New configuration for an equation-block element The DITA 1.3 element equation-block is a specialization of the paragraph element (topic/p). Because of that, we applied the paragraph element configuration to equation-block elements automatically. In the case of the paragraph role, the inherited configuration for the equation-block caused the equation-block element to be inserted too often. With the improved default configuration that includes specific configuration for the equation-block element, this element will only be inserted when appropriate. New tooltip descriptions for DITA elements The default DITA configuration now contains descriptions for most DITA elements, based on the descriptions from the DITA 1.3 standard. These descriptions will be shown as tooltips in the UI, and can be accessed using the XopusNode.getDescription API method. Improved wording in the Content Editor UI The More Content ribbon group is now renamed to the more specific All elements, and the Technical content ribbon group is renamed to the more correct Common elements. Note that the Common elements group can be customized to contain the elements your organization uses most often. This can be done using the overlay on page 0 mechanism in the configuration.

You can now see the processing-role topicref attribute In previous Content Editor versions, the processing-role attribute was given thehidden-from-ui role in the default configuration, causing it to be invisible in the properties panel. It is now shown by default, but only if the user has enabled the Authoring Attributes group in the Properties panel.

Typical Server Vanilla Installation using ISHDeploy

The Content Manager installation process is being simplified as we developed the notion of a vanilla deployment. In this type of deployment, most parameter values are calculated or set to a default, and authentication is set for a local use with ISHSTS. This makes the installation usable and testable out of the box with minimal effort.

Introducing ISHDeploy

With the help of an independent PowerShell module named ISHDeploy you can now install and configure Content Manager easily and have it run locally without mandatory post-installation tasks except the setting of a few input parameters. The global integrated vanilla deployment including the ISHDeploy's code as configuration approach consists in the following steps: 1. Set a subset of input parameters, the rest is calculated for you. We advise to stick to the suggested defaults as much as possible. 2. Install. 3. Setup connection with any commercial STS such as Microsoft ADFS or PingIdentity PingFederate using ISHDeploy cmdlets if you need to use those. 4. Further code-configure using ISHDeploy cmdlets during the lifetime of Content Manager. ISHDeploy ISHDeploy is a separate PowerShell module that lets you literally code your configuration intentions. The name of this module is ISHDeploy xx.x.x, where xx.x.x is the version of Content Manager it is compatible with.

For example Knowledge Center 2016 SP1 matches ISHDeploy 12.0.1. The presentation and documentation for ISHDeploy can be found here. This module uses cmdlets with which you can express

12 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2

your intentions, the module performs the specific settings for you.

More derived and default inputparameters for InstallTool

In the default inputparameters. xml we only keep the following parameters: osuser, ospassword, connectstring, apppath, serviceusername, and servicepassword. The rest of the parameters should be either defaulted or calculated based on values of other parameters. For example apppath will initialize datapath and webpath which are remnants of physical hard drive optimizations. Although deprecated, all original parameters can still be set explicitly if required. As a fall back mechanism if the system for example detects the wrong ps_java_home parameter value. [TS-11359|TS-11332|TS-10217|TS-11052|TS-11357]

Translation Flow and Integration Improvements

Some improvements and changes are specific to Translation Management and Translation Organizer.

Introducing an External Validation endpoint

The CMS contains your document types (DTDs and catalog) configuration, potentially including specializations. The new endpoint allows to single source that configuration by making them available over a REST endpoint. First use case is to allow SDL TMS and SDL WorldServer to validate xml-based translations before allowing retrieval to the CMS. It is now possible to validate the XML against the DTD by using a newly created endpoint: the External Validate endpoint accessible at https://ish.example.com/ ISHCM/ Api/ ExternalPreview/ Validate with either a GET or a POST call. The endpoint will provide a detailed list of errors.

Remember: The Validate endpoint is below ExternalPreview to single source the security exempt configuration. ExternalPreview can also be configured in your translation management system to show a proper preview including layout and images.

Removed racing condition that send out content twice

Regarding predictability, translations were requested by sending out translation jobs to the target translation systems. However, in some high volume scenarios some items were requested more than once which results in an increased translation cost. This happened when a content object is part of more than one translation job being prepared for sending out. The correction is in avoiding the sending race condition. We do this by introducing a lease mechanism (visible in Settings > Default Settings area). Only one Translation Organizer instance can send out a job. Note that scaling out services Translation Builder and Translation Organizer still has benefits for the more often executed preparing, checking and retrieving translation actions. Before: Parallel sending Translation Builder grabs a job, breaks it down into topics and checks the status of each topic. If the status turns out to be In Translation, the topic is not passed over and will not be translated. Translation Organizer then sets the status of the topic to In Translation before sending it. There is a probability that a topic (Topic A in this example) is sent at the same time by both Translation Organizer instances. After: Sequential sending

SDL Knowledge Center Release Notes 13 2 Release Notes - SDL Knowledge Center

The status In Translation is checked again just before sending, and topics are sent one at a time. No more double sending.

Improved polling increases throughput

Translation Organizer checks for pending jobs at regular intervals. The interval is configured through jobPollingInterval in TranslationOrganizer. config, the default value is 5 minutes. When a group of smaller jobs is available for processing, this interval could make the global processing longer than it should, as Translation Organizer waits for the end of the interval before it picks up the next job. Now Translation Organizer automatically checks for an available job whenever a job has been completed, in addition to the regular check after the interval.

Stability improvements for the SDL TMS and SDL WorldServer integration

Whenever the server returns an http 500 error to Translation Organizer - which typically means that the remote system is severely disturbed - during the retrieval phase, the former behavior was to request the user to manually restart the job. Now Translation Organizer automatically retries the job. Some transmission issues have also been fixed, such as the processing of Logical Identifiers having GUIDs with dots (.) as separators. An issue which was introduced on 2016/12.0.0. Logging details have been added for a better follow-up of every step of the interaction between Translation Organizer and TMS or WorldServer.

New and changed in version 12.0.0

An overview of new features and enhancements, as well as improved or changed functionality in Content Manager 12.0.0, compared to the previous version of the product.

For your convenience, new and changed features and functionality for Content Manager versions 11.0.3, 11.0.2 and 11.0.1 are included in this document as well.

Rebranding in SDL Knowledge Center 2016

A list of names have been changed for this release of Knowledge Center, starting with the product's name. Documentation Here is the list of name changes for this release:

Current name Obsolete name SDL Knowledge Center SDL LiveContent Content Manager SDL LiveContent Architect, Content Explorer Content Delivery SDL LiveContent Reach, Review and Collaboration Content Editor SDL LiveContent Create Quality Assistant SDL Enrich ISHSTS InfoShareSTS

14 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2

Current name Obsolete name ISHCM InfoShareAuthor ISHWS InfoShareWS Content Importer DITA2Trisoft

The usage of the obsolete names is maintained in all content focused on previous versions of the product. Artifacts The new names are used in all SDL Knowledge Center user interfaces. Visible artifacts have changed like installer names, default install paths, menu items, splash screens, etc.

All details have been adapted in the documentation accordingly.

EXE/MSI files are now signed by SDL PLC, the products are now represented by SDL Group.

New third-party software support

Support for databases, operating systems and XML editors has been updated.

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. The following software component support was added in this release Client Software • Microsoft Windows 10 • Google Chrome (release update channel) • Mozilla FireFox (release update channel) • JustSystems XMetaL 10 / 10 J(apanese) • PTC Arbortext Editor 7.0 (32b only) • Syncro Soft XML Author 17.1 (32b only) Server Software • Microsoft Windows 2012R2/x64 SP1 (including Active Directory Federated Services 3.0) • Microsoft SQL Server 2014 SP1 • Oracle RDBMs 12.1.0.2 • Oracle Client 12.1.0.1.2 • Java Runtime 1.8.0_60 (64b) • DITA-OT 1.8.5 • Windows PowerShell 4.0 (part of Windows Management Framework 4.0) Integrations • SDL TMS 2011 SP6 CU1 • SDL TMS 11.0.x

SDL Knowledge Center Release Notes 15 2 Release Notes - SDL Knowledge Center

• SDL WorldServer 10.4.4 • SDL WorldServer 11.0.x • SDL Quality Assistant 2.2.0 • SDL XPP 9.1

Client Tools changes

Client Tools improvements for this version are explained.

General

All Client Tools benefit from the write and read performance improvements that were made in web services API 2.5.

New Installers • All .msi files (and assemblies) are now signed by our legal entity certificate SDL PLC. This replaces the earlier signing by SDL Trisoft or even before that the yellow User Account Control (UAC) message indicating that The publisher is unknown. • Updated preview components (GeckoFX/XULRunner) fixes AccessViolation (0xC000005) crashes related to Windows 7/8 with enabled Pen and Touch hardware devices/drivers. [SRQ-3008|SRQ-3809] • The Print the preview (Ctrl-P) button was disabled before and is now enabled again in all client tools preview windows. [TS-9513|TS-9606|TS-9505]

File 'Synchronize' Performance

After initial set up of an account in a client tool, the Synchronize is triggered which will receive the necessary metadata configuration, DTDs, catalog, preview stylesheets, etc. from the single-sourced configuration area on the web/app server. Furthermore at client tools startup time this action is triggered to make sure your configuration is up-to-date. The files will be transferred with HTTP compression provided by Microsoft Internet Information Services (IIS), and in parallel which reduces the waiting time. [TS-9047]

More throughput by group retrieval per 1000 objects

The web service data compression - introduced in 10.0.3 - allows for transfer of more data through one web service call without actually transferring more bytes. We raised the default page size from 300 which used to be visible by status messages like Retrieving objects (300 of 24474)... to 1000 resulting in Retrieving objects (1000 of 24474)... which essentially means that less web service calls are made to load list views. The configuration option @defaultPageSize restriction in Trisoft.PublicationManager. Host.exe.config of maximum 999 has been removed. [TS-9090| TS-6877]

16 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2

Set Title plugin only triggered on editor templates

When a user manually creates a new object based on editor templates, the SETTITLE plugin inserts the FTITLE value in the element. This is normal behavior. However, the same would occur when importing content with BatchImport or Content Importer. This is unwanted behavior, since it would overwrite a longer and usually correct title with a shorter file name acquired from the metadata. The SETTITLE plugin configuration modification addresses this issue. If you want the plugin to make a distinction, we suggest you adapt your editor templates so they hold a <?ish-replace-title?>, which will trigger the plugin to override your document title. A title will not be forced for other new incoming objects. See documentation Prevent automatic document title overwriting during import.Preview does dynamic link text resolving for <xref>, <link> and <topicref>Starting from 11.0.0 the Insert dialog no longer filled in the Text to Display field, leaving it empty by default as suggested by the OASIS DITA standard in order to allow dynamic resolving afterwards. This results in, for example, an <xref> element without text body. It is now up to the XML editor to do just-in-time resolving of the title of the <xref>. The same goes for Publication Manager, which now shows the <xref> with a gray background (similar to @conref) to indicate that it is resolved text and not part of the actual XML document. The behavior of JustSystems XMetaL 9 and 10 is now fine-tuned and usability changes on our Authoring Bridge implementation (before, when inserting an <xref> or <link>, the dynamic text resolving of XMetaL wasn't triggered and you had to do a manual Edit > Refresh all references (F11)). Our common efforts are packaged in this release. [TS-9780|TS-9779|TS-9784|TS-9790|SRQ-3272]Important: By default the dynamic resolving behavior of XMetaL is not enabled. You need to activate this by going to Tools > DITA Options > Update Content tab and selecting the checkbox in front of xref/related-links.If the XML editor version behavior is insufficient for you, you can use an extra configuration option that we've added. This option will let you roll back to 10.0.x and earlier data behavior. The current behavior is that the Text to display field is no longer initialized with the logical object title (FTITLE), therefore our current templatespecification. xml configuration will assign the empty Text to display field value to variable (selecteditem: text). This results in an empty <xref> or <topicref> navtitle entry. Note that a user can still provide a value in the UI that will be passed to the variable for usage in the inserted XML element.Two new variables are introduced for use in templatespecification. xml next to selecteditem: text [TS-9772|SRQ-3272|SRQ-3255|SRQ-3264]: selecteditem:textortitle When Text to display is empty the link text will be filled with the logical title (FTITLE) of the referenced object. selecteditem:textordefault When Text to display is empty the link text will be filled with the ./title of the referenced element, if the element has a title. Similar on how our client tools previews resolve it as introduced in the 11.0.0 release.Restriction: Do note that the UI behavior will still show the Text to display field as empty, but as a post processing depending on the configured variable in templatespecification. xml we will insert the requested string. If the user fills in the field, we will use that value for the inserted XML element.SDL Knowledge Center Release Notes 17 2 Release Notes - SDL Knowledge CenterVerified Acrolinx on top of AuthoringBridge for XMetaL and oXygenWe verified that the JustSystems XMetaL 10 and 10J integrations with Content Manager Authoring Bridge work together with Acrolinx. The XMetaL server-side files were enriched with statements needed by Acrolinx in the DTD-related macro files for XMetaL 10 and 10J. These files are synchronized from the server. If Acrolinx is not installed on the client, these statements will just be ignored by XMetaL. We used the Acrolinx Plug-in for XMetaL 4.2.0 build 1153 (client_XMetaLV4. 2_B1153.msi) to verify the behavior.Remember: In case the Knowledge Center menu disappears, you can reset the editor's workspace by launching XMetaL again with the Ctrl key pressed.We verified that the <oXygen/> XML Author/Editor 17.1 integrations with Content Manager Authoring Bridge work together with Acrolinx. No server-side files changes are required here. We used the Acrolinx support for <oXygen/> 14.1+ 3.4.0 build 4179 to verify the behavior.Note: We installed the Acrolinx plugin using the <oXygen/> plugin system via Help > Manage add-ons..., using the following instructions: http://infocenter.acrolinx.com/en_plugins/topic/com.acrolinx.doc.plug_ox/Plug-ins/Plug-in_for_Oxygen/installing_with_update_site_OX.html .Content Editor changesA description of the new and improved web editor behavior you can expect with this release.Table editing improvementsSeveral improvements will let you edit tables much more easily. Pasting merged cells Tables with merged cells are now pasted correctly into documents that use the CALS table model. You can have merged cells if they were copied from Word or HTML. Column names in CALS tables In tables that are following the CALS table model, every column has a name specified in the column specification. This can be used on the cells to facilitate spanning cells over multiple columns. These column name attributes are now updated correctly when inserting new columns. Column commands from the breadcrumb for column When working with CALS tables the breadcrumbs show an item for the column element (colspec) as well. The menu for this item now shows options to delete or move the column, and add to additional columns to either side of the current column. Improved label: Change cell type The label for changing a header cell used to say "Change header cell", but it was not clear what will be changed. The new label is "Change cell type (cell/header cell)" for when you wish to switch the cell type from header to regular(non-header) cell. Allow delete of selection spanning several cells In previous versions, selections over multiple cells could not be deleted at all, or resulted in a broken table structure. It is now possible to select a part of the table and delete, the table will be kept valid, and the selected content will be removed.18 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Delete tables from the table tab You can now delete tables from the Table tab as well. Bug fix: Table is broken (additional tgroup added) when pasting table with header Pasting a table with a header would result in a table with two tgroups: one tgroup with the header row and and a row with one empty cell, and another tgroup with the table body.New functionalityNew functionality improving configuration and user experience. Auto-save to local storage While working on a document, a copy of the document is stored in the browser's local storage. If for any reason you are not able to save your document, you can continue from the point where you left when you open the document again. The draft is removed when finishing or canceling editing. When loading a document, we check if there is a local draft for the same document available. XMetal-style placeholders In XMetal, placeholders can be configured by using an XML processing instruction in the document or template. Those placeholders are now behaving as real placeholders in our editor as well. This is not a replacement of the existing placeholder feature, but an addition for improved compatibility. Handle unique attributes • Some attribute values are meant to be unique in the <a href="/tags/ConTEXT/" rel="tag">context</a> of a document. However, the default behavior in the editor is to copy attributes when pressing enter. • When attributes are defined as do-not-duplicate, those attributes are not duplicated on copy/paste. Attributes can be defined as unique because they are defined with the xs:ID type in the XML Schema, or by using the do-not-duplicate role in the node configuration. Tags on view An additional configuration option is available to define a tags on view. The tags will be automatically injected in the rendering. Configuration is available to define what tags should have a tag shown and if the pretty name or the raw XML name should be shown. Exposed API for defining custom spell checker functions New API methods are now available for letting you define a custom spell checker, which for example can use a server-side spell checking service.Data Layer ImprovementsThe data layer of Content Editor is rewired giving a considerable performance boost. These new private WebAPI integration points reduce round-tripping and avoid unnecessary serializaiton/deserialization. Obsolete and unnecessary properties were removed. All these changes give you a much nicer editing experience.SDL Knowledge Center Release Notes 19 2 Release Notes - SDL Knowledge CenterCodeblock editing improvementsThe following bugs have been fixed: • correct cursor position with inline elements in codeblock • space-preserving content is now wrapping in the xml view • newline at the end of a codeblock is now shown • linebreaks are no longer lost when copying codeblock to another codeblock • cursor down in a codeblock now works in Chrome • cursor position is now rendered correctly at the end of the line in a codeblock in IE • new linebreaks are now shown in IE after moving cursor • cursor position is now updated when typing in codeblock in IEImprovements in modifying the ribbon UICustomizing the ribbon UI is key to setting up the editor according to your preferences. You can now: • Create custom ribbon tabs and groups. • Disable the out of the box ribbon tabs and groups. • Insert elements using roles.Note: Previously it was already possible to configure a button for an element using the role configuration. Pressing that button would then toggle the element. There is now an additional configuration option for situations where insert behavior is preferred over toggle behavior.Bug fix: all library panel buttons now have different ID's. It is thus now possible to enable or disable panel buttons separately.Improved DITA supportA few improvements of interest to DITA users, as Content Editor continuously evolves with DITA.Improved display of draft-comments In particular, draft-comments with paragraphs inside are rendered in a better way now.Added placeholder for topichead When inserting a topichead element a placeholder is shown.Better use of the scalefit attribute The scalefit attribute is now ignored when a width, height or scale value is set. Added icons and ribbon tab for Task elements When working with a topic of the Task type, a new ribbon tab is available to insert the relevant elements. Configuration specific to DITA is split from generic out of the box configuration This makes it easier for you to maintain configuration files.20 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Improved way to insert references • The panel for selecting references is now shown when an image or link is inserted using the breadcrumbs, right-click menu and CTRL-Enter quick insert menu. • When a template is configured to insert one of these elements, the panel is shown to select which object to reference. Insert references panel behavior The panel will now be closed and the operation will be cancelled whenever you click somewhere outside of this panel.Correctly identifying the used browserOpera 15 and later was recognized as Chrome, causing the editor to be run without warning that Opera is not a supported browser. The warning is now shown again. If you want to use Opera anyway, that is possible by clicking the try anyway button, or by configuring a URL parameter (platformtest= skip).References in the correct languageWhen inserting references, the editor will show previews in the same language as the document that is active in the editor. Also when resolving referenced content in the editing view, the same language is used. If the reference is not available in the same language as the document that is edited, an error is displayed.Typical server installation changesThings that have changed on a single web/app server setup when using InstallTool (IT) or DBUpgradeTool (DBUT).PrerequisitesYou'll find the full list and versions in the documentation Requirements chapters (also present in the Installation and Upgrade guides). Here is a focus on the changes: 1. Operating System Programs and Features • We added an official statement that we only fully qualify on English Windows Server Operating Systems. [TS-7891] • By a one-time operation to open up permissions in %WINDIR%\ System32\ inetsrv\ config\ applicationHost. config, we can now easily overwrite server settings per web site and/or virtual directory through their web.config file. See Configuring IIS applicationHost.Config. This will move typical settings like <defaultDocument>, <directoryBrowse>, <asp>, <static- Content>, ... to Web.config. Note that <security> and <authentication> are still part of applicationHost.config. • Installation of Static and Dynamic compression features have been added to requirements. 2. Third Party Components have been raised to: • Microsoft Server .NET Framework 4.5 • Microsoft .NET Framework Visual C++ Redistributable 2013 (64-bit) • Java Development Kit 1.8.0_60 (64-bit) • Java Runtime Environment 1.8.0_60 (64-bit) • Oracle Data Access Client (ODAC) 12.1.0.1.2SDL Knowledge Center Release Notes 21 2 Release Notes - SDL Knowledge Center• PowerShell v4.0 (part of Windows Management Framework 4.0)While installing or upgradingInstallTool doesn't stop or start Windows service IISAdmin.By opening up applicationHost. Config we can enable Static and Dynamic Compression for regular HTTP and SOAP messaging calls out of the box. The end result of applying our typical installation steps will result in a system where WCF SOAP messages and DTD related files that are synchronized by Client Tools are now also compressed. Starting from IIS 8.x, so Windows 2012R2, InstallTool (IT) will configure every IIS Application Pool to always be alive. This will shorten delays of first requests to an idle server.Post installation stepsConfiguration overview when upgrading from 11.0.X to this version.Settings / File 11.0.0 Config Version 12.0.0 Config Version What has changed Admin.XMLBackgroundTaskConfiguration.xml1.1 1.1 Added handlers: • CREATETRANSLATION- FROMLIST, CREATETRANSLATION- FROMREPORT, CREATETRANSLATION Removed handlers: • DELETETRANSLA- TIONS, BATCHPERFORMACTIONAdmin.XMLChangeTrackerConfig.xml1.0 1.0 • n/a Admin.XMLExtensionConfiguration.xmln/a 1.0 • New configuration, holds<infoShareEx- tensionConfig>; disabled PreTranslation configuration and IMetadataBinding extensions Admin.XMLInboxConfiguration.xml1.0 1.0 • n/a Admin.XMLPluginConfig.xml1.0 1.0 • Deprecated, replaced by Admin.XMLWriteObjPluginConfig.xmlAdmin.XMLStatusConfiguration.xml 2.0 3.0 <OutOfDateStates> • must be configured as regular statuses22 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Settings / File 11.0.0 Config Version 12.0.0 Config Version What has changed Admin.XMLTranslationConfiguration.xml1.0 2.0 Controlled pivot • <languagepaths> and moved <ComparisonElements> to Admin.XMLExtensionConfiguration.xmlAdmin.XMLWriteObjPluginConfig.xml 2.0 2.0 ISHRAISEPUBLISHEVENT • should be the last plug-in in section <write ishcondition=" ISHType= 'ISHPublica- tion'">otherwise publishing will not work • Element names can be used instead of labels for configuration Deactivated • CHECKREVIEWERFILLEDIN and CHECKTRANSLATOR- FILLEDIN • Plugins on Translation Management means: Finetuned @ishcondition CurrentAction called CreateTranslation and updated handlers ISHSYSWORDCOUNT, ISHSYSCOPYFISHTO- BETRANSLWC and ISHSYSTRANSLATIONLOADAfter the installation is complete, none of our Windows services (including Crawler, TrisoftSolrLucene,...) will start automatically. The first reason is that the database is not guaranteed to be in the right state until you run DBUpgradeTool (DBUT). Another reason is that in a multi server environment you wouldn't want all your servers to pick up the same role. For your convenience on a single web/app server setup, we've provided a simple PowerShell script that will start and mark all services as Automatic. For using it, execute\App\Setup\Manage\Enable-DefaultServices.ps1asAdministrator.SDL Knowledge Center Release Notes 23 2 Release Notes - SDL Knowledge CenterDatabase layer changesChanges and additions impact Microsoft SQL Server and Oracle RDBMs database systems performance, setup or process.Empty/demo databaseThis applies to both Microsoft SQL server and Oracle RDBMs. An "empty" database is available in order to facilitate fast setup. A more adapted expression than "empty" would be "ready to use", as this database already contains the basic structure helping an immediate application, as well as all minimal settings. Specifically: • The database is upgraded to Content Manager 2016 level; • The latest out-of-the-box configuration files (e.g. Admin.XMLStatusConfiguration. xml) are submitted; • The status Translation Rejected which is used by Translation Management via the translation jobs is submitted; • The user role TRANSLATORSERVICE and user ServiceUser with user role TRANSLATORSERVICE are added to support translation jobs; • All editor templates are added and released in English, German, Dutch and Japanese; • For all output formats Keep default attributes is enabled to improve performance; • For Japanese .chm file support with code pages, all output formats with transtype htmlhelp are redirected to ishhtmlhelp; • Legacy electronic document types (EDTs) like EDT-WORD are removed; • EDTs for new MS Office formats like .docx (EDTDOCX) are submitted with the correct mime type . So, the "empty" database now contains EDTs for the following file extensions: .docx, .ppsx, .pptx, .xlsx, .3dxml, .jar, .mp3, .mpg, .smg, .svg, .svgz, .swf and .zip.Remember: Even if the database is up-to-date with the Content Manager version, you still need to run DBUpgradeTool (DBUT) to ensure that a database job is created, the latest database upgrade scripts are executed and all statistics for the indexes are generated.Note: For demo purpose there is an equivalent "demo" database which contains everything for the Mobile Phone publication in addition to the structure mentioned above.Microsoft SQL Server Versions Introducing Microsoft SQL Server 2014SP1 support, next to Microsoft SQL Server 2012 SP2. Changes • During normal operation it is possible to run with revoked db_owner. Still required are: SELECT, INSERT, UPDATE, DELETE, CREATE TABLE, CREATE VIEW, CREATE FUNCTION, CREATE PROCEDURE, REFERENCES, ALTER ANY SCHEMA and EXECUTE.24 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Restriction: Note that DBUpgradeTool (DBUT) runs still require db_owner. More information in Optionally minimize the database user's roles and permissions.• One job with 1 step which contains a stored procedure ISHCore_TrisoftInfoShareJob with optional parameters documented. • Only minimal maintenance: rebuild indexes for fragmentation > 10% and update statistics using SQL Server method without full scan.Oracle RDBMs Versions Introducing Oracle RDBMs 12c support. Ensuing from this: • Oracle Data Access Client (ODAC) raised from 11.2.0.4 to 12.1.0.1.2. This version offers us better transaction handling. For .NET components even less distributed MSDTC-promoted transactions. • Gathering statistics is now rerouted to the standard Oracle autotask instead of our database job TRIDKANALYZEDB. This leads to a faster DBUpgradeTool (DBUT) run. • The performance is improved when passing larger data sets to our *_VALUES tables, like for example STRING_VALUES or NUMBER_VALUES. Required differences when upgrading our database from a previous Oracle setup to Oracle RDBMs 12c: • We stepped away from the Oracle deprecated UTF8 character set in favor of AL32UTF8. AL32UTF8 character set. • Reduced tablespaces to only ISH_DATA_M, ISH_INDEX_M and ISRC_PAGE. Storage clauses are removed. • NLS_LENGTH_SEMANTICS remains BYTE and no longer required to switch to CHAR. • Reduced minimal isource user rights, resulting in matching isrcuser.i and CheckMinimalUserRoles.sql. • The documentation describes import/export routines based on Oracle's data pump technology exdp and impdp instead of deprecated exp and imp. • Matching new database template file are delivered. • Dynamic sampling is new in Oracle RDBMs 12c and gathers statistics on the fly during query execution. However, on all our test environments this had a neutral to adverse effect which made us decide to turn off Dynamic sampling. We set Oracle optimizer_dynamic_sampling to 0 instead of the default setting 2.Important: This means that we expect every Oracle RDBMs 12c environment to run with the above described new setup.SDL Knowledge Center Release Notes 25 2 Release Notes - SDL Knowledge CenterWeb client securityAs there is more and more awareness about security, we invested in tests and enhancements on our web clients. This resulted in improved security against a wide range of potential threats.Penetration testing was done on our web client. All critical and potentially high issues coming out of this regarding Cross-Site Scripting (XSS), information leakage, insufficient authentication, content spoofing, predictable resource location, SQL injection are fixed.Cross site scripting (XSS) • Stored XSS: these generally occur when user input is stored on the target server. The data can be retrieved from the web application without being made safe to render in the browser. • Reflected XSS: these occur when user input is immediately returned by a web application in an error message, search result or any other response that includes some or all of the input provided by the user as part of the request. This happens without that data being made safe to be rendered in the browser and without permanently storing the user provided data. Our Classic ASP pages were fixed by using the reform libraries provided by the “https://www.owasp.org/” on page 0 encoding project. (ASP).NET pages make use of the build-in libraries from the .NET Framework.CookiesCookies are now verified to be Secure, so preventing cookies from being observed by unauthorized parties; and HttpOnly which helps mitigating the risk of client side scripting accessing the protected cookie (if the browser supports it).HTTP Response HeadersRevealing the specific software version of the server may allow the server machine to become more vulnerable to attacks against software that is known to contain security holes. The headers X-Powered- By, X-AspNet-Version and Server are removed through web.config configuration and assisted by an HttpModule called RemoveVersionHttpResponseHeaderModule. Response headers now no longer reveal information like [TS-10481|TS-10093]Server: Microsoft-IIS/8.5 X-AspNetMvc-Version: 5.2 X-Powered-By: ASP.NETSQL InjectionThis basically consists in inserting a SQL query via the input data form from the client to the application. A successful injection exploit can read sensitive data from the database, modify data, execute adminis- tration operations, ... During the scans there was no evidence found that this is an issue for our web client. Overall, Content Manager's web client is build up with a dedicated Data Access Layer which fully relies on techniques like parameter binding.26 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Insufficient Transport Layer ProtectionSSL/TLS has a good version negotiation mechanism that should prevent a browser (and .NET client applications) and server that support a modern TLS version from using anything less. However, because some servers are buggy and don't implement version negotiation correctly, browsers break this mechanism by retrying connections with lesser SSL/TLS versions when TLS handshaking fails. By injecting some trivial errors on the network, an attacker can cause a browser to speak SSL3 to any server and then run the above attack. The essence is that client and server can be forced to handshake down to the minimal common intersection of protocols supported which out of the box is an SSL 3.0 that has a serious security risk (POODLE attack).We've adapted our client tools to no longer accept a protocol handshake resulting in SSL3 overwriting the out-of-the-box .NET runtime behavior. [TS-9114|TS-9428]You can also avoid the usage of protocol SSL3 by no longer allowing it on your server as described on https://technet.microsoft.com/ ; this will also make it work for web browsers.Taxonomy/ontology integrationThe ability to live link an external source to your content, which can provide a living semantic hierarchy (or ontology) to your topic repository, has been developed and enhanced under the technical name of MetadataBinding.GeneralMetadataBinding allows our metadata fields to be linked to external sources. An external source is a repository of items. These items can be related in a simple (e.g. flat list) or complex hierarchy (e.g. graphs). Every item must have a unique identifier and a label. In the repository we only save the identifiers, which in turn means that labels and navigation hierarchy is always retrieved live. Every field can be linked to a different MetadataBinding interface implementation.User ExperienceA control named LabelManager is available in the web client. It gives access to a dedicated interface that lets you use configurable search capabilities through your objects with the assistance of the external taxonomy. A control named TagList is available in the Client tools. You also have access to specialized options in the configuration file MetadataConfig. xml. This gives you control on every aspect of the Metadata- Binding system: suggestions, filtering, options for a messaging system, ... Both controls offer the following behavior: • Tree view shows the tree navigation implementation of the bounded connector (MetadataBinding25. RetrieveTagStructure) showing navigation and selectable items. • Auto suggest (as-you-type) shows you items that match your criteria (MetadataBinding25. RetrieveTags). • Tree view with as-you-type experience performs a client side filtering of the open tree view, eventually only showing navigation and selectable items.SDL Knowledge Center Release Notes 27 2 Release Notes - SDL Knowledge CenterRestriction: As the tree of navigation and selectable items is fully present on the client side, we suggest information architects and integrators to make a conscious decision on how much data is transferred every time.• Recent tags in suggestion mode shows the last 10 selected items for this field. The control also supports batch metadata in the Client Tools.Hierarchical ExperienceAll of the UI control behavior is supported by an API which also allows to pass context of other metadata fields. In practice, the content of one or more fields can define the behavior of the currently active field. For example, the values selected in a Continents field can be passed to the Countries field to filter to only European countries. If a user would immediately go to the Countries field, it is up to the connector implementation to either show all countries or inform the user to select a continent first. This will help reduce data sets and guide the user to allowed combinations.Search ExperienceAs the repository stores identifiers, it means that all Find and Search capabilities of the system rely on passing identifiers. Only when using the UI control to select a certain identifier, the connector is in play. The chosen identifier(s) are then passed to the existing Find and Search operations.As an extra, the incoming <ishquery> structure which is passed to Search25.PerformSearch from the Client Tools or Web Client search screen can be rewritten through an implementation of the IQueryEnhance interface. As an example, when searching on Continents North America, your connector implementation might want to enhance the search to also search for Canada, USA.ValidationThe UI controls will guide the users, but eventually validation will happen on the web/app server through an IWrite* plugin (MetadataBinding25. Validate). This ensures that any API integration follows the same rules.ConfigurationThe connectors are configured in the Web Client Settings area. Configuration is stored as part of <infoShareExtensionConfig> stored in FISHEXTENSIONCONFIG field available through Set- tings25 API. We use the notion of a <source> for a connector to allow configuration reuse across several fields.We offer some Web Client assist functionality (data-metadatabinding-view) to make LabelManager easier. And the MetadataConfig. xml drives the Client Tools configuration of typetaglist.28 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Connector for SmartLogic Semantic Enhancement Server (SES)This reference implementation connector covers a lot of use cases to connect to this ontology system. This connector can handle identifiers, labels, classifications through extensive configuration.Restriction: When using a rich customizable taxonomy system, there are potentially unlimited configuration setups and some of them cannot be expressed in our current configuration options. That is why we consider this a reference implementation.The connector is implemented in \ Plugins\ TrisoftSmartlogic. dll file, and can be used by providing handler name: SmartlogicSESConnector. Some implementation notes are: • RetrieveTagStructure uses recursion over the SES API hierarchy service to build the tree step by step. • RetrieveTags uses the SES API prefix service to get the results while applying the selectable and entry nodes of the configuration. • IQueryEnhance is not implemented in this connector. • Relation parameters describe how to walk over the graph: relation incorporates the instructions on how to move from one term to others, ID identifies the relation to be used from metadatabinding fields parameter, type identifies if the relation is hierarchical or associative, abbreviation points to the relationship name as defined in the model, direction and from conditions are used to identify if a rule can be used for a term, to conditions are used to filter out the expanded terms when using this relation. • Describe per field what part of the graph you are targeting: entrynodes defines where to begin on the graph, relations to references which relations are allowed to be used to create the set of terms for this field and selectable to defines which terms are selectable by the user.Publish throttling by raising different event types per output formatConfiguration of distinct even types per publish type variations releases the full capability of the background task engine.OverviewHistorically the event type triggered by any UI or API driven Publish operation triggered a hardcoded event of type named EXPORTFORPUBLICATION on our background task system. From then on all of these publish operations were considered equal. There was no distinction possible based on: • Output format, such as PDF (XPP A4), PDF (XPP letter), Content Delivery, Compiled Help, ... • Size, such as booklet, service manual, flyer, ... • Usergroup. • Language. • Result (EDT), such as PDF, CHM, ZIP, ... • Available licenses of third party software. • ... Important: The out-of-the-box behavior has not changed. But you have to adapt the Settings > XML Write plug-in Settings so that ISHRAISEPUBLISHEVENT is the last plug-in in section <write ishcondition="ISHType='ISHPublication'">; otherwise publishing will not work.SDL Knowledge Center Release Notes 29 2 Release Notes - SDL Knowledge Center<plugin name="ISHRAISEPUBLISHEVENT" handler="RaisePublishEvent" ishcondition="ISHLevel='lng' and CurrentAction='SetMetadata'"> <description>Starts a background task when the 'FISHPUBSTATUS' field is changed to 'Pending'</description> <workingset> <ishfields> <ishfield name="FISHPUBSTATUS" level="lng" /> <ishfield name="FISHEVENTID" level="lng" /> </ishfields> </workingset> <initialize> <parameters> <parameter name="EventTypeConfiguration"> <configuration><eventtype>EXPORTFORPUBLICATION</eventtype></ configuration> </parameter> </parameters> </initialize> </plugin>New IWrite* plugin named 'RaisePublishEvent' [TS-9408]Technically API calls PublicationOutput20. Publish and PublicationOutput25. SetMetadata (when updating field FISHPUBSTATUS to value VPUBSTATUSPUBLISHPENDING) will no longer raise the hardcoded EXPORTFORPUBLICATION event. This has now moved into a documented plug-in called RaisePublishEvent that also takes care of an EventMonitor entry.Tip: As the necessary code to raise a publish event moved into a plug-in, it is now possible to create your own custom plug-in that drives publishing based on other metadata.Example: Separate publish to the Content Delivery output format from the other output formatsThe goal of this example is to serialize all background tasks that asynchronously connect to Content Delivery like synchronize and publish, without affecting the regular PDF, CHM, ZIP type of publish operations. 1. Navigate as an Administrator to Settings > XML Write plug-in Settings and adapt or add the following RaisePublishEvent plugin as the last plugin in section <write ishcondition=" ISHType='ISHPublication'">. After submit, one output format will trigger an event named EXPORTFORPUBLICATIONREACHINTERNAL while all others will still trigger a EXPORTFORPUBLICATION.<plugin name="ISHRAISEPUBLISHEVENT" handler="RaisePublishEvent" ishcondition="ISHLevel='lng' and CurrentAction='SetMetadata'"> <description>Starts a background task when the 'FISHPUBSTATUS' field is changed to 'Pending'</description> <workingset> <ishfields> <ishfield name="FISHPUBSTATUS" level="lng" /> <ishfield name="FISHEVENTID" level="lng" /> </ishfields> </workingset> <initialize> <parameters> <parameter name="EventTypeConfiguration"> <configuration>30 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2<eventtype ishcondition="FISHOUTPUTFORMATREF='GUID-3005828F-C93A-4 0DE-B5E9-3B47AD575899'">EXPORTFORPUBLICATIONREACHINTERNAL</eventty pe> <eventtype>EXPORTFORPUBLICATION</eventtype> </configuration> </parameter> </parameters> </initialize> </plugin>2. Navigate as an Administrator to Settings > XML Background Task Settings. a. Duplicate the <handler eventType="EXPORTFORPUBLICATION"> ... </handler> node an adapt the @eventType name to the new entry EXPORTFORPUBLICATIONREACHINTERNAL. Potentially you can adapt configuration like time outs, error numbers, OASIS DITA configura- tions, ... b. Insert a <add ref="EXPORTFORPUBLICATIONREACHINTERNAL"/> next to <add ref=" SYNCHRONIZETOLIVECONTENT"/> in the group named SynchronizeToLiveContent. This group is out-of-the-box and part of the Default service role. It is set to only allow 1 execution per BackgroundTask service.Restriction: If you have multiple back end servers, you can set up a new service role and configure one BackgroundTask service to pick up your new specific service role.3. Depending on the event type name, you need to configure EventMonitor so that it groups your Publish related logging entries. We pre-configured the following variations in EventMonitorMenuBar.xml: • EXPORTFORPUBLICATION (default) • EXPORTFORPUBLICATIONPDF (typically used by all PDF generators like SDL XPP,AntennaHouse XSL Formater, ... • EXPORTFORPUBLICATIONZIP (typically used by Web Help, dita, ... • EXPORTFORPUBLICATIONCHM (Compiled Help) • EXPORTFORPUBLICATIONREACHINTERNAL (internal review collaboration system) • EXPORTFORPUBLICATIONREACHEXTERNAL (public delivery system) Note: The group All Events will always list all entries in case you skip this group configuration.Publish pipeline changesThe publish process benefitted from a couple of minor improvements.Publishing to Content DeliveryThe publish (FeedSDLLiveContent. ps1) and synchronize (SynchronizeToLiveContent. ps1) code responsible to upload and prepare material in the Content Delivery stack have been enriched with retries. In their matching .config files you can configure the number of retry attempts (livecontentrequestretries defaults to 1 retry and livecontentprepareretries defaults to no retries) and time between retries (livecontentrequestwaitbetweenretries and livecontentpreparewaitbetweenretries default to a 30 seconds timespan) for regular and prepare calls. The end result is that a single failing file upload because of network glitches will not fail the complete EXPORTFORPUBLICATION event handled by the BackgroundTask service. [TS-10242]SDL Knowledge Center Release Notes 31 2 Release Notes - SDL Knowledge CenterDebugging publishing to Content DeliveryTo allow easier debugging, we already generated a __publish.cmd that allows you to reexecute the POSTPROCESSING step.We now generate an extra file __FeedSdlLiveContent. ps1 per publication export that handles the Content Delivery part of the POSTPROCESSING. So in essence it is a subset of __publish.cmd that almost immediately starts addressing the Content Delivery upload.Note: Only available when publishing to Content Delivery (LiveContent) of course. This also requires you to Run As Administrator.OtherUnexisting folder path to a style processor can make cscript.exe hang. A pro active check on file existence should avoid this. [SRQ-1540]Translation Flow and Integration ImprovementsSome improvements and changes are specific to Translation Management and Translation Organizer.GeneralTranslation Management has been fully refactored, resulting in stability and performance improvements. On top of this we made sure that IWrite* plugins now also runs on the newly created target languages. The source language used for the generated target languages is better controlled by the introduction of <languagepaths>.Event typesThe background tasks/event types for Translation Management have changed, and one (DELETETRANS- LATIONS) have been removed. The Event Data for these event types has also changed.32 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Event Name Description Event Data SampleCREATETRANSLATIONFROMREPORT <data> • Finds the objects that need <targetlanguages></ to be translated (through a targetlanguages> baseline report) and splits <requestedlanguages>true</ them per logical object in requestedlanguages> separate new <inheritedlanguages>true</ CREATETRANSLATION tasks inheritedlanguages> <ishfields></ishfields> • Previously known as <ishobjects> PUSHTRANSLATIONS <ishobject ishref="GUID-A" ishtype="..." ishlogicalref="..." ishversionref="..." ishlngref="..." /> <ishobject ishref="GUID-B" ishtype="..." ishlogicalref="..." ishversionref="..." ishlngref="..." /> </ishobjects> </data> CREATETRANSLATIONFROMLIST <data> • Takes the objects and splits <targetlanguages>de, them per logical object in fr, ja, nl</ separate new targetlanguages> CREATETRANSLATION <requestedlanguages>false</ background task requestedlanguages> <inheritedlanguages>false</ • Previously known as inheritedlanguages> CREATETRANSLATIONS <ishtype>ISHModule</ ishtype> <logicalid>GUID-X</ logicalid> <version>3</version> <languages/> <resolutions>High, Low</resolutions> <ishfields> <ishfield name="FCOMMENTS" level="lng"></ ishfield> <ishfield name="FTRANSLATOR" level="lng">admin</ ishfield> </ishfields> </data>SDL Knowledge Center Release Notes 33 2 Release Notes - SDL Knowledge CenterEvent Name Description Event Data SampleCREATETRANSLATION <data> • Creates the target language <targetlanguages></ objects targetlanguages> Previously known as <requestedlanguages>true</ • CREATEPRIVATETRANSLATIONSrequestedlanguages> <inheritedlanguages>true</ inheritedlanguages> <ishfields></ishfields> <ishobjects> <ishobject ishref="GUID-A" ishtype="..." ishlogicalref="..." ishversionref="..." ishlngref="..." /> </ishobjects> </data>Combining this revisited granularity of having many CREATETRANSLATION as early as possible and the introduction of Background in the previous release, we greatly boosted throughput and introduced extra scaling options on top.Language pathsIt is now possible to define preferences in source language for translations. This is determined by the top-down succession order of the <languagepath> elements. When a path is specified first, it will be applied in priority. For example, the paths define that when it comes to translate content into fr, the source language will be es in preference to en, because the path from es to fr is specified first. On the other hand, es can only be created from en.<languagepaths> <languagepath from="es" to="fr" /> <languagepath from="en" to="es" /> <languagepath from="en" to="fr" /> </languagepaths>Resolution control on the Translation JobYou can now control which Image resolutions are being generated by Translation Management to be pushed out by the Translation Organizer service. Do note that Translation Management should be enabled on the image objects in question. [TS-9096|TS-8999|SRQ-2510]File System enabled out-of-the-boxIn the past you had to configure either WorldServer, TMS or file system to work. From now on, TranslationOrganizer. exe.config has file system readily configured for usage. [TS-8992]34 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Translation Management on ImagesThe logical level Translation Management flag (FNOTRANSLA- TIONMGMT) on images was not respected. When Translation Management is enabled it should not be possible to manually add language/resolution combinations. When Translation Management was triggered on the image, it resulted in error Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another near Generating mixed language file. The implementation of RunTranslationManagementOnResolution was corrected. [TS-8940|TS-8910|SRQ-2574]Translation OrganizerIntroducing support for WorldServer 11 and TMS 11. In essence Translation Organizer does database (repository) to database (translation management system) synchronization. We optimized the routines and introduced better debugging support. Retry routines are tuned towards our repository and towards WorldServer and TMS - for example when synchronizing templates. The routines of unleasing Translation Jobs are tuned to make sure jobs always keep moving. Translation Job Properties will now show the Leased by and Date leased on fields for informational purposes. EventMonitor entries are no longer deleted if they are connected to an incomplete Translation Job entity.OtherAs all other processes, Translation Management benefits from the fact that now all API25 methods accept element names. This means that developers can change user role labels as they go along. As other processes, Translation Management benefits from the Background tasks polling system. Translation tasks can be carried out in parallel with publication, synchronize and other tasks. The delay before the tasks are started is also reduced.PushTranslation flow comparison between 11.0.0 and 12.0.0A schematic depiction of a PushTranslation flow shows how the new background tasks system improves the PushTranslation throughput.Former flowIn the 11.0.0 version of the Background Task System, when the Client sent one publication for translation, only one task, the first one, was created for this publication, and the process passed around an event data containing the data for all remaining objects. Any valid Background Task Service could then pick up this single task. If there was more than one Background Task Service active, only one could take on this event.When the Background Task Service had finished executing this task, the next task was created for this publication, from the event data containing X-1 remaining objects, and could then be picked up. And so on, passing around an event that contained all remaining objects and that was getting smaller and smaller. In this flow, one publication could be processed by one Background Task Service at the same time. A scaling would have no effect on the PushTranslation speed.Current flowSDL Knowledge Center Release Notes 35 2 Release Notes - SDL Knowledge CenterIn the 12.0.0 version of the Background Task System, when the Client sends one publication for translation, all the tasks for this publication are created from the start. If several valid Background Task Services are active at that time, each of them can pick up a task. This enables a certain degree of parallel processing for a given publication at a given time.Background TaskEnhancements on the centralized Background Task system that replaces the decentralized Microsoft Message Queuing (MSMQ) system.Attention: When upgrading an existing database, you should submit the Admin.XMLBackgroundTaskConfiguration. xml into the XML Background Task Settings before using the system.Attention: None of the Windows services will be automatically started after an installation. This avoids blocked database upgrades when using DBUpgradeTool (DBUT) and background task pickups with the wrong configuration.GeneralBy introducing the Background Task system, we offer a full replacement of the previously used Microsoft Message Queuing system (MSMQ). Some features we introduced are: • DatabasecentralizedXmlSettingsconfiguration(\ Websites\ Author\ EnterViaUI\ Admin. XMLBackgroundTaskConfiguration. xml). This provides a single point of configuration. Through Windows environment variable settings, we still allow per server changes. You can set on top of this extra environment variables such as installation paths in \ Applications\ BackgroundTask\ Bin\BackgroundTask.exe.config. • Matrix based polling with maximum executions per message type, server or server role - if desired. By default we will restrict the number of publish operations to 2 in parallel, but we will at the same time also allow 2 translation management operations, a synchronize and 2 other (customer) types. So in this example up to 7 tasks are handled in parallel allowing various message types to make progress. Configuring the number of parallel executions protects the available server resources.Note: The retry mechanism relies on the error handling of the background task handler. If the handler suppresses the exception or makes a new background task for handling the retry, there can be more or less attempts that configured.• Scalability and fairness based on the central database queue. • The background task will be leased. This allows lease refreshes, lease time outs and hence recoveries without administrator interventions. All programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced IWrite* plugins as replacement for IOnDocStore and ICustomerFunction. Now we introduce IBackgroundTaskHandler to replace IEventHandler.36 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Improved polling increases BatchImport and PushTranslation throughputThe BackgroundTask service poller sleeps a configured interval (by default 10s) if all slots in all groups are occupied or when there are no tasks waiting to be executed. Some COM+ handlers like PushTransla- tion and BatchImport work with a single task that they continuously resubmit. This causes in practice the sleep interval to always be triggered. So effectively a slow down of these background tasks services (a BatchImport file import for example) takes less than the 10 seconds sleep time. [TS-8977|TS-8799] As a general improvement, the poller will now be activated when a slot is freed up from a group. For the above example it means that the resubmitted task of a BatchImport will almost immediately be picked up again, therefore increasing throughput. Besides this throughput improvement we changed the out-of-the-box XMLBackgroundTaskConfiguration. xml ISHBATCHIMPORT @isolationLevel value from Process to None. This avoids starting a new process for every file that needs importing. This could only be done by adjusting the logging engine to avoid file lock issues.BackgroundTask isolationLevel AppDomain addedThe execution by the BackgroundTask service of implementations of the IBackgroundTaskHandler configured through the @isolationLevel attribute can now be driven through these variations: • None; meaning that the code is directly loaded and executed by the BackgroundTask service (BackgroundTask.exe). • Process; meaning that the code is directly loaded and executed by a new child process of the BackgroundTask service (BackgroundTaskIso. exe). • AppDomain; meaning that the code is loaded in a separate .NET application domain (for the background task id) and then executed by the BackgroundTask service (BackgroundTask. exe). When the execution finishes this domain is unloaded in order to release all resources loaded in the domain. [TS-8989|TS-8350]Federated Services changesThe federated services and claims-based authentication system received improvements to reduce network traffic.GeneralSeveral scripts are added to simplify your maintenance across server nodes. We advise you to run the scripts after installation as they will have the correct parameters already set. The scripts are located: • ForMicrosoftADFS,in\App\Setup\STS\ADFS\Scripts\. • ForISHSTS,in\App\Setup\STS\ISHSTS\Scripts\. Out of the box for ISHSTS, our setup routines will add prefixes to the relying party configuration such as ISH, LC and BL. This prefix will be used in our basic claims set transformation (see \ Web\ InfoShareSTS\ Configuration\ infoShareSTS. config) so they are immediately ready to go.SDL Knowledge Center Release Notes 37 2 Release Notes - SDL Knowledge CenterSimplified STS configurationFor integrating Content Manager with a Security Token Service (STS), ISHCM and ISHWS require a set of identifiers to be configured within the target Security Token Service. We already had 1 relying party URL for Content Manager web client (ISHCM) and 1 for Content Delivery web client (CD). Previously we required 100+ entries for the Web Services relying party in a scaled setup. From now on we only need 1 relying party URL as well for the Content Manager web services (ISHWS). Overview The number of identifiers for ISHWS has been significantly reduced in order to reduce STS related configuration complexity. This improvement makes the STS independent of the Content Manager cluster composition. No action is required on the STS when adding or removing nodes from the cluster. ISHCM identifiers ISHCM requires one identifier to be configured on the STS and that is the baseurl/ infoshareauthorwebappname/ where baseurl and infoshareauthorwebappname are the values from the input parameters. E.g. https://example.com/ ISHCM/ . ISHWS identifiers ISHWS requires a minimum of one identifier to be configured on the STS and that is the baseurl/ infosharewswebappname/ where baseurl and infosharewswebappname are values taken from the input parameters. E.g. https://example.com/ ISHWS/ . The identifier must be configured with an encryption certificate using the public key of the Content Manager service certificate. This is referenced by the servicecertificatethumbprint input parameter.The Content Manager has been adjusted to depend only on this identifier. Other integration against ISHWS might require an additional optional set of identifiers depending on their code. This optional set is made of one identifier for each ISHWS WCF endpoint based on this pattern: baseurl/ infosharewswebappname/Wcf/API25/Application.svc.Remember: The out-of-the-box system will work with the single relying party. In case you have legacy code, we strongly advise you to adapt your code as described in Best practices using .SVC Web Service in C#.. If you want you current code base to work, you can rely on the deprecated 31 compatibility endpoints (one for every svc endpoint like baseurl/ infosharewswebappname/ Wcf/ API25/ Application. svc) that we submit as well.Tip: <a href="/tags/Microsoft_Visual_Studio/" rel="tag">Microsoft Visual Studio</a>'s default behavior is to Add references using the baseurl/ infosharewswebappname/ Wcf/ API25/ Application. svc style which in turn means that you rely on the deprecated 31 compatibility endpoints. Please have a look at Best practices using .SVC Web Service in C#. in the documentation.ISHSTS configuration ISHSTS will automatically seed its database with the required identifiers. For convenience it will also seed the optional set for each svc endpoint. To enforce the re-seeding of the database, this file's versionwasincreasedto Web\ InfoShareSTS\ App_Data\ IdentityServerConfiguration-2. 2.sdf. The previous version IdentityServerConfiguration-2. 1.sdf is now obsolete and should be removed.The scripts folder was moved from \ App\ Setup\ STS\ InfoShareSTS\ Scripts \ to \ App\ Setup\ STS\ ISHSTS\ Scripts\ .Thescriptfileswithinthefolderarerenamedto • SDL.ISH-ISHSTS-Configure for Windows Authentication.ps1 • SDL.ISH-ISHSTS-RP-AddRelyingParty.ps1 • SDL.ISH-ISHSTS-RP-UpdateCertificate.ps138 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Fromwithinthefolder \ App\ Setup\ STS\ ISHSTS\ Scripts\ ,thefiles SDL.LiveContent. Architect-InfoShareSTS-RP-AddNode.ps1andSDL.LiveContent.Architect- InfoShareSTS-RP-RemoveNode. ps1 are removed because the new configuration requirements are cluster composition independent. Microsoft Active Directory Federated Services (ADFS) v3 Support Existing ADFS relying parties must be deleted and then replaced by new ones to reflect the changes described here. All scripts in \ App\ Setup\ ADFS\ Scripts\ are renamed to match the current version of ADFS (ADFSv3.0 for this release). The script SDL.ISH-ADFSv3.0-RP-Install. ps1 script will create on ADFS the necessary relying parties. As with ISHSTS, the optional set for each svc endpoint is also added for convenience.Thefiles SDL.LiveContent. Architect-ADFSv2. 0-RP-AddNode. ps1 and SDL.LiveContent. Architect-ADFSv2. 0-RP-RemoveNode. ps1 are removed because the new configuration requirements is cluster composition independent.DocumentationNew content describes deployment guidelines and limitations of various setups. There is now, for example: • An explanation on front-end certificate usage (in for example Network Load Balancing scenarios) and back-end (batch) certificate usage. • Security flows and scaling limitations of ISHSTS. Customers authenticating with on-premises Microsoft ADFS STS can use a SDL Knowledge Center installation deployed on SDL hosted servers outside their network. The services (web sites like ISHCM, ISHWS, Content Delivery, Quality Assistant, etc) can be configured to accept a token from ISHSTS additional to the originally configured ADFS one. This configuration removes the dependancy of delegated services or even background tasks to connect to your on-premises STS installation which is usually not accessible because of your company's firewall. All clients (browsers and client tools) running from the customers network have access to both ADFS and SDL Knowledge Center products. The solution is based on using the internal ISHSTS as the STS for all back-end initiated activities. This configuration removes the dependency on the customer's ADFS. Out-of-the-box ISHSTS allows delegation with tokens that were issued only from itself. All back-end activated entities are redirected to use ISHSTS as their issuer instead of the customer's ADFS. For Security Token Services other than ISHSTS and ADFS, such as PingIdentity, the Security Token Service Requirements chapter is added to explain what is necessary for the successful integration of Content Manager and the Security Token Service. To help advance 3rd party integrations, a best practices topic has been added. When integrators utilize the suggested pattern then the optional set of identifiers is no longer required.Light weight Windows Authentication on ISHSTSOur backward compatible solution ISHSTS was created to allow customers relying on Content Manager user accounts (read Trisoft accounts) to continue to work but still have the benefits of a Secure Token Service (STS) and Single Sign On (SSO) across the Knowledge Center solution. From an STS perspective ISHSTS forced authentication by requesting a valid username/password combination which would be validated in the Content Manager repository. A popular request was to re-introduce simple Windows Authentication without introducing Microsoft Active Directory Federated Services (ADFS) in the environment. We now offer indirect Windows Authen- tication on top of ISHSTS. This is a light weight solution that is provided for hidden authentication bySDL Knowledge Center Release Notes 39 2 Release Notes - SDL Knowledge Center your logged on Windows account. [TS-8818].Attention: If high-availability, scaling or uptime are important to you, we advise you to go with the more dedicated STS system matching your authentication and identity provider requirements.Tip: From now on it is important to distinguish the Secure Token Service (like ISHSTS, ADFS, ...) from the Authentication Type (like username/password, Windows authentication, kerberos, ...). In the past ISHSTS was becoming a synonym of username/password, which is no longer the case.An overview of typical combinations that are confirmed by the field is provided below. For a more elaborate description of the inputparameters. xml parameters, refer to the installation documentation.Choose your STS, ISHSTS by UsernameAuth ISHSTS by WinAuth ADFSv3 by then your WinAuth Authentication Type issuerwstrustbind-UsernameMixed WindowsMixed WindowsMixed ingtype issuerwstrustend-BASEURL/ BASEURL/ ADFSURL/adfs/ pointurl INFOSHARESTSWEBAPPNAME/ INFOSHARESTSWEBAPPNAMEserices/trust/13/ issue/wstrust/mixed/ /issue/wstrust/mixed/ windowsmixed username windows issuerwsfederation-BASEURL/ BASEURL/ ADFSURL/adfs/ls/ endpointurl INFOSHARESTSWEBAPPNAME/ INFOSHARESTSWEBAPPNAME issue/wsfed /issue/wsfed issuerwstrustmexurlBASEURL/ BASEURL/ ADFSURL/adfs/ INFOSHARESTSWEBAPPNAME/ INFOSHARESTSWEBAPPNAMEservices/trust/mex issue/wstrust/mex /issue/wstrust/mex serviceusername ServiceUser empty, the account of empty, the account osuser will be used of osuser will be used servicepassword ED47BA6B... empty empty issueractorusernameValue of serviceusername Value of osuser Value of osuser issueractorpasswordValue of servicepassword empty emptyTo be able to use this you need to add an Operating System feature/role for enabling Internet Information Services (IIS) Windows Authentication (Internet Information Services > World Wide Web Services > Security > Windows Authentication) on ISHSTS after installation. [TS-8816]40 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Other changesAll future active profile requests will no longer force a token type from the client side. Do note that we still require an OASIS SAML 1.1 token as a result. In practice Trisoft.Utilities.ServiceReferences is used to pass <trust:RequestSecurityToken><trust:TokenType>urn:oasis:names:tc:SAML:1.0:asser- tion in its token request which confused some Secure Token Services (STS) like PingIdentity PingFederate. [TS-9049|TS-9034|SRQ-2523]In previous versions of ISHSTS, the actor user for delegation purposes - like server-side connection of web client code to web services code - was never verified as an existing account. From now on a valid account has to be specified at installation time through inputparameters. xml parameters issueractorusername and issueractorpassword. The actor must exist in the Content Manager repository as an Internal user. We recommended to use the same as the ServiceUser, see inputparameters. xml parameters serviceusername and servicepassword.Programmer's Interface ChangesNew interfaces for MetadataBinding, QueryEnhance and TranslationManagement. Interfaces ICustomer- Function and IOnDocStore are replaced by IWrite*-plugins and IEventHandler by IBackgroundTaskHandlerAll interfacesAll programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced IWrite* plugins as replacement for IOnDocStore and ICustomerFunction. In 11.0.1 we introduced IBackgroundTaskHandler to replace IEventHandler.Introducing MetadataBinding ExtensionsEvery MetadataBinding connector should implement Trisoft.InfoShare.Plugins.SDK. Extensions.MetadataBinding interfaces. The connector is read-only. Configuration is stored as part of <infoShareExtensionConfig> under <metadatabindings>, located in FISHEXTENSIONCONFIG field available through Settings25 API.Interface Short Description IHandler Interface to retrieve information from an external system IHandlerConfiguration Interface is implemented by the object passed to .NET handler Initialize method. It provides a handler with the parameters configured in the XML Extension Settings IFieldsFilter Interface for passing metadata that can be used to further filter the results to the RetrieveTags and RetrieveTagStructure methods IMessage The message and all information necessary to translate the message IMessageParam One parameter for the (error)message IResolveIdsContext Implement this interface in order to pass it to the metadata binding ResolveIds methodSDL Knowledge Center Release Notes 41 2 Release Notes - SDL Knowledge CenterInterface Short Description IResolveIdsResult An object implementing this interface is returned from the metadata binding ResolveIds method IRetrieveTagsContext Implement this interface in order to pass it to the metadata binding RetrieveTags method IRetrieveTagsResult An object implementing this interface is returned from the metadata binding RetrieveTags method. IRetrieveTagStructureContext Implement this interface in order to pass it to the metadata binding RetrieveTagStructure method IRetrieveTagStructureResult An object implementing this interface is returned from the metadata binding RetrieveTagStructure method IStructureTag Container for the minimal metadata of the object in the external system and of the propriety that defines if the object can be selected or not. It is used when returning results from the RetrieveTagStructure method. ITag Container for the minimal metadata of the object in the external system. It is used when returning results from the ResolveIds and RetrieveTags methods ITagRelation Container for the relationship between 2 Tag objects. It is used when returning results from the RetrieveTagStructure method IValidateContext Implement this interface in order to pass it to the metadata binding Validate method IValidateResult An object implementing this interface is returned from the metadata binding Validate methodIntroducing QueryEnhance ExtensionsThe Web Client and Client Tools full-text index search actions are all routed over Search25 API. All the API consumers don't and shouldn't know if a field is metadata bounded or not. So there are no API changes for this. This extension point can enhance the incoming XML query before submitting to the full-text index. The examples are adding extra search criteria.Tip: Only the query (<ishquery>) is enhanced, not the search result.Restriction: The additional clauses are not weighted in the result. They are equal to other search criteria.The configuration is stored as part of <infoShareExtensionConfig> under <search> stored in FISHEXTENSIONCONFIG field available through Settings25 API. The <queryenhance> entries are executed in the configured order.42 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Interface Short DescriptionIEnhanceQueryContext Uses the IEnhanceQueryContext instance properties to access the input data passed to the EnhanceQuery method of IQueryEnhanceHandler classIEnhanceQueryResult Returns IEnhanceQueryResult instance from the EnhanceQuery method of IQueryEnhanceHandler class IQueryEnhanceHandler Interface for dynamically enhancing the search query IQueryEnhanceHandlerConfiguration Contains the objects required for the query enhance handler initializationIntroducing Target XML File ExtensionsIt is now possible to configure a list of processing actions performed on to-be-translated XML files before they are sent to translation. You can do so using interfaces described in the documentation as Translation management plugin interfaces. This set of interfaces is also responsible for purging any of the generated target file markup. For example going from a mixed language file back to a single language file.PreTranslation functionality is now implemented using this new interface through Trisoft. InfoShare.Plugins.SDK.Extensions.TranslationManagement.Tip: The original PreTranslation is deprecated and hence disabled out of the box.Interface Short Description ITargetXmlFileHandler Custom handler for generating a target file based upon the current source file and the previous released translation ITargetXmlFileGenerateContext Implemented by the object passed to the handler Generate method. It provides the handler with the necessary input data ITargetXmlFileHandlerConfiguration Implemented by the object passed to the Initialize method of the handler implementing the ITargetXmlFileHandler interface. It provides the handler with all parameters configured in the XML Extension Settings.ITargetXmlFileGenerateResult The Generate method of the ITargetXmlFileHandler class return an ITargetXmlFileGenerateResult instance ITargetXmlFilePurgeContext Implemented by the object passed to the handler Purge method. It provides the handler with the necessary input data ITargetXmlFilePurgeResult Needs to be implemented in order to return the result of the Purge method from the ITargetXmlFileHandler classSDL Knowledge Center Release Notes 43 2 Release Notes - SDL Knowledge CenterIBackgroundTaskHandler replaces IEventHandlerBackground Tasks can now be handled by a full stack .NET implementation. The following interfaces are provided and documented: IBackgroundTaskHandler, IBackgroundTaskHandlerContext and IBackgroundTaskHandlerConfiguration.Restriction: Your older IEventHandler, now deprecated, implementations will still be handled by the BackgroundTask service as configured through <comIEventHandler> in Admin.XMLBackgroundTaskConfiguration. xml. Migration to the new interface is advised as your implementation probably also relies on older API 1.0 or API 2.0 code base.As a first implementation we offer an IBackgroundTaskHandler alternative implementation of the following plugins.Name IEventHandler (COM+) IBackgroundTaskHandler (.NET) THUMBNAILSUBMIT ISHPluginsIso. SetThumbnail CDocSetThumbnail INBOXEXPORT, REPORTEXPORT, SEARCHEXPORT, IshPluginsIso.cOut ExportObjects PUBLICATIONEXPORT PUBLISHINGSERVICEPROCESS, ZIPFILES, IshPluginsIso.cIshShell IshShell SYNCHRONIZETOLIVECONTENTAPI References documentation is available for the interfaces or on how to Create a background task handler.IWrite* plugins Improvements Execution during translation creation It is now possible to configure a list of write plugins which will be executed during the creation of the target language objects. When a translation is created, all Write plugins that have value CreateTranslation as CurrentAction configured in the @ishcondition in the IWrite* configuration are executed.Note: The write plugins will be executed after the translation management extensions.Execution when objects are sent to publish During PublicationOutput, when an object is sent to publish on a specified output, IWrite plugins can be executed. It can only be plugins that act on metadata (so, no IWriteMetadataAndBlob. .. is applicable) because the blob cannot be modified at this point. These plugins can add additional actions during a status transition, such as changing a date or starting a messaging background task.CopyField plugin A IWriteMetadata - CopyField plugin is introduced. This plugin copies values from one field to another. It is used by CreateTranslation during Translation Management to make sure that mandatory or unchanged fields (e.g translation word count) are available.LoggerName A specific LoggerName for the PluginLogService is available and can be configured from now on. [TS-8913]44 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Context based on element names The IWrite* plugins that will be executed on your objects are selected by conditional publishing of the IWrite* configuration (Settings > XML Write plug-in Settings or Admin.XMLWriteObjPluginConfig. xml). Your incoming object will drive the context used for conditional publishing. Configuration can now be done by element names besides the more volatile labels. An @ishcondition entry such as DOC-LANGUAGE='en' AND ishoutputformat='PDF a4' - which breaks if somebody renames the language to en-US - should now be configured using the stable element names like DOC-LANGUAGE='VLANGUAGEEN' AND ishoutputformat= 'VOUTPUTFORMATPDFA4'.Language, resolution and output format are extended. The documentation describes the possible condition names and values that define a context for content objects and publication outputs. So an example context, also called product definition, looks like this:CurrentAction = SetMetadata IshType = ISHIllustration FMAPID = GUID-BC80B446-62BB-4583-9AF5-1C94D0C236E2 VERSION = 1 DOC-LANGUAGE = en, VLANGUAGEEN FRESOLUTION = Thumbnail, VRESOLUTIONTHUMBNAIL EDT = EDTJPG ISHUserGroup = VUSERGROUPDEFAULTDEPARTMENT ISHLevel = logical, version, lngTip: Almost all of our controlled values have a fixed readable element name prefix like VLANGUAGE, except some older output formats which were based on our generic GUID-... naming scheme.IWrite* plugin BlobExtractMetadata finetunedA configuration like <Parameter name="ExtractXPath">//*[contains(@class,' topic/ shortdesc ')] that returned an element was not possible anymore. When multiple values were returned from the XPath and stored in a single value field, we returned a TooManyValues error, instead of concatenating the values with a comma space.For example, assume FSHORTDESC is a single value string field, and the XML file contains:<shortdesc>The Title provides information about configuring networking for SDL Architect, such as iSCSI, Fibre Channel, and so on. </shortdesc>For an ExtractXPath = "//*[contains(@class,' The Title provides information about configuring topic/shortdesc ')]" the result in FSHORTDESC networking for SDL Architect such as iSCSI, Fibre would be: Channel, and so on. For an ExtractXPath = "//*[contains(@class,' The , provides information about configuring topic/shortdesc ')]/text()" the result in networking for, Architect such as iSCSI, Fibre FSHORTDESC would be: Channel, and so on. For an ExtractXPath = "//*[contains(@class,' The , Title, provides information about configuring topic/shortdesc ')]//text()" the result in networking for , SDL, Architect such as iSCSI, Fibre FSHORTDESC would be: Channel, and so on.ThenSDL Knowledge Center Release Notes 45 2 Release Notes - SDL Knowledge Center• For an ExtractXPath = "//*[contains(@class,' topic/shortdesc ')]" the result in FSHORTDESC would be The Title provides information about configuring networking for SDL Architect such as iSCSI, Fibre Channel, and so on. • For an ExtractXPath = "//*[contains(@class,' topic/shortdesc ')]/text()" the result in FSHORTDESC would be The , provides information about configuring networking for, Architect such as iSCSI, Fibre Channel, and so on. • For an ExtractXPath = "//*[contains(@class,' topic/shortdesc ')]//text()" the result in FSHORTDESC would be The , Title, provides information about configuring networking for , SDL, Architect such as iSCSI, Fibre Channel, and so on.Prevent automatic document title overwriting during importThe SETTITLE plugin configuration has been modified, and an <?ish-replace-title?> processing instruction has been added to the Editor templates. This prevents the title of a document from being automatically replaced with the metadata title during a BatchImport or Content Importer operation.About this task When a user manually creates a new object based on editor templates, the SETTITLE plugin inserts the FTITLE value in the <title> element. This is normal behavior. However, the same would occur when importing content with BatchImport or Content Importer. This is unwanted behavior, since it would overwrite a longer and usually correct title with a shorter file name acquired from the metadata. The SETTITLE plugin configuration modification addresses this issue.Procedure 1. Modify the SETTITLE plugin configuration in the database through the Content Manager web client: 2. In the web client, select Settings > XML Write Plug-In Settings. 3. In the XML plugin configuration file, browse to the SETTITLE plugin XML definition. 4. In the SETTITLE plugin XML definition, look for the OnNodeXPath parameter. In this parameter, replace any occurrence of the [title] text part with [title[child: : processing-instruction('ish-replace-title')]], then save your changes. After implementing these plugin configuration changes, the original document title should remain unchanged, also when performing Duplicate or Check In As operations in the Client Tools. The modified SETTITLE plugin configuration should be similar to the following example:<plugin name="SETTITLE" handler="BlobSetXmlNode" ishcondition="EDT='EDTXML' and VERSION='1' and CurrentAction='Create'"> <description>Set the title for new objects using the metadata title</ description> <workingset> <ishfields> <ishfield name="FTITLE" level="logical" /> </ishfields> </workingset> <initialize> <parameters> <parameter name="OnNodeXPath">(/*[contains(@class,' map/map ')][title[child::processing-instruction('ish-replace-title')]]) | (/*[contains(@class,' topic/topic ')][title[child::processing- instruction('ish-replace-title')]])</parameter> <parameter name="NodeType">node</parameter> <parameter name="NodeName">title</parameter> <parameter name="OverwriteExisting">Yes</parameter>46 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2<parameter name="Value"> <value type="MetadataField"> <parameter name="MetadataField">FTITLE</parameter> <parameter name="MetadataFieldLevel">logical</parameter> </value> </parameter> </parameters> </initialize> </plugin>5. Modify all Editor templates in the database through the Content Manager web client: 6. In the web client, select Repository. 7. In the folder tree structure on the left pane, browse to the ../System/Editor template/ Topics folder. 8. For each object in this folder, carry out the following steps: a. Select the version of the object you want to modify, click Download to download the current content of the object, then click Save in the Save As dialog window to save it locally. b. Open the object in a text editor, for example Notepad, insert or append the text <?ish- replace-title?> to the title text of the <title> element, then Save the file. c. In the web client, create a new version of the object. d. In the pop-up dialog window, associate the appropriate language to the new version of the object, and fill out the input fields as necessary. e. Upload the object by clicking File > Choose File on the dialog window, and then by selecting the file you edited in the text editor. f. Release the object. If the object has multiple languages, for example en-us, ru-ru, and ja-jp, repeat these steps for each language. 9. Repeat these steps with any other objects in the folders under ../System/Editor template where your topic, map and library templates are stored. The modified templates for topics, maps and library topics should be similar to the following topic template example:<?xml version="1.0" encoding="utf-16"?> <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic> <title>Enter the title of your topic here<?ish-replace-title?><title> <shortdesc>Enter a short description of your topic here (optional).</ shortdesc> <body> Your topic begins here. </body> </topic>API changesThe web services API changes.SDL Knowledge Center Release Notes 47 2 Release Notes - SDL Knowledge CenterGeneralThe web services API are made available for integration using the Windows Communication Foundation (WCF), resulting in SOAP 1.2 services like /ISHWS/ WCF/ API25/ Application. svc capable of support- ing claims-based authentication.The deprecated endpoints like /ISHWS/ Application25. asmx relying on proprietary authentication are still present in this release.Typically users write their first code based on a label (e.g. statusIn translation). If you want to change the label later on, you have to adapt a lot of code. Now all API25 methods accept element names (e.g. stable id for status VSTATUSINTRANSLATION) as input for parameters making code independent from label renames. This is valid for all ListOfValue based entries like for example: language, resolution, outputformat, user, usergroup, userrole, etc. [TS-6473]The FISHSTATUSTYPE calculation is no longer done asynchronously, avoiding a lot of background task Translation Managements to spin up. The FISHSTATUSTYPE field holds shortcut values to identify if your object is either draft (10), released (20), out-of-date (30), etc.Comma Space (, ) is now allowed in string fields. With the changed back-end, the system can now easily make the difference between a multi-value field where comma-space is the separator, and a regular string field. [TS-5104] In the version algorithm, the build number system changed. We will now continuously increase the build number. For example version 10.0.312.5 has build number 312 and can be read as March 12 from the year 2013. Version 10.0.1629.5 has build number 1629 and can be read as 29 April 2014 (every multiple of 1200 indicates a year). [TS-6951]We introduced full stack write functions for classes DocumentObj25 and PublicationOutput25 in 11.0.0. These optimized versions got a considerable performance improvement because of a new architecture and the rewrite of the IOnDocStore system, resulting in the IWrite plugins. This now allowed us to introduce a considerable read performance improvement on all API 25 classes like for exampleDocumentObj25 and PublicationOutput25 - available since 11.0.1. The boost is visible in metadata field retrieval areas such as: • Publication Manager, when opening a publication; • Authoring Bridge, when loading the content of a folder; • Baseline operations like autocomplete and freeze; • API25 based customization. Most optimizations were in the data source layer. Result set handling of queries that return 500+ rows received a major boost. Some loops and lists were optimized with dictionary lookups for bigger amounts of data. Also the logging engine setup changed: it now relies more on static instances. [TS-8889]Restriction: The boost has limited effect on the web client, publish service, translation management, and anything that is not rewired to API 2.5 yet.MetadataBinding25API consumers don’t know if a field is metadata bounded to an issue tracker, or a wiki, or a taxonomy system, or some ontology system. The following API functions have been added to let you build the controls in a Properties screen. These endpoints allow generic handling of data coming from metadata bounded fields: • MetadataBinding25. ResolveIds resolves the tag IDs for each field into labels/descriptions. • MetadataBinding25. RetrieveTags retrieves a list of tags for the specified field and applies filter logic like hierarchical structures.48 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2• MetadataBinding25. RetrieveTagStructure retrieves a hierarchy of tags – so including relationships – for the specified field and applies filter logic. • MetadataBinding25.Validate [internal] validates the tag IDs of the specified fields against the filter field values.DocumentObj20, DocumentObj25 and PubliciationOutput25All read functions, like for example DocumentObj25. RetrieveMetadata, let you retrieve the labels of metadata bounded fields. ishvaluetype psXMLRequestedMetadata psOutXMLObjList(default) <ishfields><ishfield <ishobjects><ishobject ...="">< name="FCITIES" level= ishfields><ishfield name="FCITIES "lng"/></ishfields> "level="lng">Moscow, Copenhagen, Brussels</ishfield></ishfields></ ishobject></ishobjects> value <ishfields><ishfield <ishobjects><ishobject ...="">< name="FCITIES" ishfields><ishfield name="FCI- level="lng" ishvalu- TIES" level="lng" ishvaluetype=" etype="value" value">Moscow, Copenhagen, /></ishfields> Brussels</ishfield></ishfields></ ishobject></ishobjects> id <ishfields><ishfield <ishobjects><ishobject ...="">< name="FCITIES" ishfields><ishfield name="FCI- level="lng" ishvalu- TIES" level="lng" ishvaluetype=" etype="id" id">524901, 2618425, 2800866</ /></ishfields> ishfield></ishfields></ishobject> </ishobjects> element <ishfields><ishfield <ishobjects><ishobject ...="">< name="FCITIES" ishfields><ishfield name="FCI- level="lng" ishvalu- TIES" level="lng" ishvaluetype=" etype="element" element">524901, 2618425, 2800866 /></ishfields> </ishfield></ishfields></ ishobject></ishobjects>Tip: Example on internal managed fields: value Admin, ID 4484 and element VUSERADMIN as readable unique identifier. It is managed externally, so metadata-bounded fields will return the same value for ID and element as @ishvaluetype attribute.All find functions, like for example DocumentObj25. Find, require the identifier to be passed. The actual value or label is not saved in the repository and is always looked up just-in-time in the metadata bounded source repository.All write functions, like for example DocumentObj25. SetMetadata, require the identifier to be passed. The actual value or label is not saved in the repository. Furthermore the label is not guaranteed to be unique enough to allow lookup in the metadata bounded source repository. PublicationOutput25. Find and DocumentObj25. Find with a filter on metadata using @ishop- erator like now can filter on values over 255 characters in length. The earlier rootword-length filter limitation has been removed. Performance has been improved for these functions as they take the Status Filter (FISHSTATUSTYPE) restriction into account from the start. [SRQ-3393|TS-9866] We fine-tuned several behaviors, most notably: • When submitting a blob as non-administrator, you were blocked if the object was released. Now you are blocked only if the object is part of a released publication output with the current language.SDL Knowledge Center Release Notes 49 2 Release Notes - SDL Knowledge Center• When updating the status, you must select a valid status transition. Moreover, if the object is part of a frozen baseline, you could not move from released back to a draft status. Now you can do both actions as long as the object is not part of a released publication output, making it easier to work statuses on translated objects.DocumentObj20. StartTranslationMgmt is obsolete and can be replaced by TranslationManagement25.CreateTranslationFromVersion [internal]. DocumentObj20. TerminologyUpdate is obsolete.EDT25All documents and publications in the database are linked with an Electronic Document Type (EDT) which specifies the file extension and the mime type of the document. We introduce an API which allows remote management, aligns with OutputFormat, User, UserGroup, ... • EDT25.Create • EDT25.GetMetadata (single) • EDT25.RetrieveMetadata (plural) • EDT25.Update • EDT25.Delete • EDT25.Find EDT25.GetList is deprecated and should be replaced by EDT25.Find which matches our naming convention.Restriction: EDT create and retrieve is no longer possible using TriDKXmlSetup. The way EDTs are stored in the repository has changed, for example the introduction of a list of value called DEDTNAME. Theauxiliaryscriptsin\App\Database\Common\DatabaseIndependent\Examples\CreateEDT\are still present and adapted to no longer rely on TriDKXmlSetup but use the web services over a Trisoft. Automation library which has been made available for this purpose only. [TS-10135|TS-10368]Fixed issuesIssues that were fixed from Content Manager are described.Fixed issues in version 12.0.4An overview of bug fixes and issues that were addressed in Content Manager 12.0.4, compared to the previous version of the product.50 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Fixed Issues in 12.0.4 Web ClientThe following Web Client issues are fixed in Content Manager 12.0.4 compared to 12.0.3.Web Client • Not wellformed HTML in a logical-level form prevented custom metadata fields addition to the database. The HTML has been fixed in this form. [TS-12396|TS-12368|SRQ-6347] • When previewing a topic or map in the Web Client, and using a link in this object to open another object's preview in another tab, the version selection dropdown list (for comparison) was absent in the second preview tab. That selection list is now available. [TS-12328|TS-12329|SRQ-6381] • For some user roles with no access to the Inbox tab of the Web Client, some actions on content stored in the Repository such as Check Out, didn't work because Inbox is the selected tab by default in the Web Client. This has been fixed and the Repository action now have the expected effect in this case. [TS-12519|SRQ-6719] • The behavior of the disable attribute for publication search has been aligned with the behavior of disabled for standard search. [TS-12533|TS-12534]Fixed Issues in 12.0.4 Client ToolsThe following client tools issues are fixed in Content Manager 12.0.4 compared to 12.0.3.Client Tools and XML • Several DPI scaling issues appearing when the display is zoomed in at 125% have been fixed. Verified across various supported Windows versions (bitness, language,...) and using different GPU hardware. [TS-12153] • The properties window now fits the screen size and the scroll bars appear normally. • The date picker controls now appear normally at this scale [SRQ-5247]. • The display size of dropdown lists now corresponds to the size of the working space.Publication Manager • Changing the baseline will now reload the publication avoiding a restart of the Publication Manager instance. [TS-12520|SRQ-6683] • When using the Search functionality in client tools, the selection of the None option in the calendar from the Advanced options prevented the search to run. [TS-12525|SRQ-6431] • When setting a condition in XMetaL, the focus no longer switches to the previous Windows application, typically Publication Manager [TS-12530|SRQ-6623]SDL Knowledge Center Release Notes 51 2 Release Notes - SDL Knowledge CenterFixed issues in 12.0.4 Content EditorThe following Content Editor issues are fixed in Content Manager 12.0.4 compared to 12.0.3.Content Editor • Packaged the Chinese translations as part of build 5.4 - 5672 [TS-12481]Fixed issues in 12.0.4 Web/App/Db serverThe following issues are fixed in Content Manager 12.0.4 compared to 12.0.3.PublishServiceBy default PublishService retrieves metadata over API20 which does not handle IMetadataBinding (so taxonomy integration), toggling TRISOFT_INFOSHARE_PublishService_UseMinimalRequestedMetadata does, but the registry key was not used for the Publication and publicationOutput metadata retrieval which is now corrected. [TS-12361|SRQ-6428]When publishing the metadata is retrieved over API20 by default. Unless TRISOFT_INFOSHARE_ PublishService_UseMinimalRequestedMetadata is enabled because then API25 is used. There is a difference in behavior between API25 and API20 RetrieveMetadata file (fields not present on a card type are not returned with API25) no longer cause publish to DITA XML to fail. [TS-12407|TS-12464]OtherFor the ExportObjects BackgroundTask handler implementation of events like INBOXEXPORT or PUBLICATIONEXPORT. The algorithm for reducing the size of titles for exported files has been modified to adapt to cases when the file extensions have different sizes. For example, .met files that are created when .ai files are exported have a title longer by one character. This no longer generates errors. [TS-12500|SRQ-6677]Fixed issues in version 12.0.3An overview of bug fixes and issues that were addressed in Content Manager 12.0.3, compared to the previous version of the product.Fixed Issues in 12.0.3 Web ClientThe following Web Client issues are fixed in Content Manager 12.0.3 compared to 12.0.1.Web Client • The conflict that prevented the web client's search date picker from working when metadatabinding is enabled has been resolved [TS-11743]. • Now the publication search feature accessed from the Web Client benefits from metadata binding with taxonomy (only the main search the main search benefitted from it before) [TS-11701]. • The AddVersion dialog reappears in the Web Client when you do a Checkout operation on an object with a Released type of status [TS-12006].52 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2• We replaced state by status in Settings > Initial Status and error messages whenever we referred to statuses [TS-11702|SRQ-5321].Fixed Issues in 12.0.3 Client ToolsThe following Client Tools issues are fixed in Content Manager 12.0.3 compared to 12.0.1.Publication Manager • Trying to invoke XML Attributes of an object just added in a publication, therefore not yet part of the baseline, resulted in an error "Cannot resolve link text for topic reference GUID#. A version is required. " This has been fixed [TS-11650|SRQ-5269]. • Publication Manager no longer returns "Cannot resolve link..." and "The XML attributes of [] could not be changed..." errors when trying to select a one verison topic through Browse in the XML Attributes dialog [TS-11789|SRQ-5500]. • Publication Manager no longer hangs when several objects that include mandatory properties (property="required") are imported or copied. This issue appeared when images were imported in Publication Manager using the file system (through the Browse Repository dialog for example) or when multiple topics were duplicated: after the last object was displayed as imported/copied, the progress dialog hanged then the application was reported as not responding and had to be shut down. This occurred when objects had mandatory properties such as showmode for images or reviewer for topics [TS-11785|SRQ-5491;SRQ-5578]. • The issue preventing Publication Manager from supplying a navtitle when an object was added using drag&drop, copy-paste or the Add Within and Insert Before commands has been fixed [TS-11811|SRQ-5628]. • When drag&dropping or copy-pasting groups of topics from one publication to another in Publica- tion Manager, the versions for the dropped/pasted topics were not assigned. No further actions would be possible on these topics unless a version was selected. This issue has been fixed and versions are now automatically assigned to the dropped/pasted topics [TS-11897]. • When changing properties for a group of selected topics, Publication Manager could return one DragDrop registration did not succeed exception dialog for each selected topic, then the operation completed when you click Continue for each of these dialogs. This has been fixed: the operation now completes without error [TS-12019].Fixed issues in 12.0.3 Content EditorThe following Content Editor issues are fixed in Content Manager 12.0.3 compared to 12.0.1.Content Editor • It is now possible to edit a topic from the Inbox, or in any other case when the Repository ribbon is hidden [TS-11984|SRQ-5713].SDL Knowledge Center Release Notes 53 2 Release Notes - SDL Knowledge CenterFixed issues in 12.0.3 Web/App/Db ServerThe following Web/App/DB Server issues are fixed in Content Manager 12.0.3 compared to 12.0.1.TranslationOrganizerTranslationOrganizer now has a more precise reporting of issues caused by files sent back by WorldServer. The RetrieveTranslationJobItems API now includes two new fields that help finding the exact files containing DTD-invalid XML: The ERROR and EXTERNALSTATUS fields [TS-10304|TS-10305|TS-11557|TS- 11558|SRQ-4069]. The log files now contain the precise statuses that are dynamically detected by TranslationOrganizer during the run. The statuses are printed at the beginning of the log [TS-12057].Other• We don't log method enter/exit or anything from Trisoft.InfoShare.COMAPI in order to avoid NLOG.config changes causing deadlocks [TS-12034|SRQ-5807]. • Improved recovery for IIS Application Pools that failed to re-initialize because the database was unavailable during their first initialize attempt [TS-12134|TS-12157|SRQ-6051].Fixed issues in version 12.0.1An overview of bug fixes and issues that were addressed in Content Manager 12.0.1, compared to the previous version of the product.If you are upgrading from a release prior to Content Manager 12.0.0, refer to the release notes for the relevant versions in-between.Fixed Issues in 12.0.1 Web ClientThe following Web Client issues are fixed in Content Manager 12.0.1 compared to 12.0.0.Web Client • The breadcrumb trail is now correctly updated when displaying a topic from search results. [TS-11173|TS-11172|SRQ-4847] • Unicode encoding using Classic ASP's Server.HTMLEncode no longer interferes with our anti-XSS upgrades. Unicode (Japanese) characters used in labels no longer return errors. [TS-11049|TS-11048| SRQ-4661] • The statistics section and statistics details are now loading correctly in the translation report. This was blocked because an obsolete xpath expression was used. [TS-10868|TS-10950|SRQ-4557| SRQ-4778] • Remove OutputFormat Skin used option from configuration which is passed to LiveContent as trisoft.outputformat. fsdllivecontentskin as this future not implemented parameter causes confusion. [TS-10907|TS-10869|SRQ-4400] • The issue preventing a user to cancel publish from the Web Client has been solved by making sure the user label was used instead of the element name for permissions. [TS-10747|SRQ-4431]54 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Fixed Issues in 12.0.1 Client ToolsThe following Client Tools issues are fixed in Content Manager 12.0.1 compared to 12.0.0.Client Tools and XML • The 'New...' dialog initially shows an editor template selection screen where the horizontal tabs are matching the folder of your content type you created in the special EditorTemplates folder. The current tab size is hardcoded to around 90 pixels which in turn means you'll only see around 13 characters of your folder name. Now current hardcoded value 90 can dynamically become around 420; still leaving room for left/right arrows to appear. So in practice the folder name will still be cut off, but the tab can be almost as big as the dialog allows it to be. [TS-11348|TS-11347|SRQ-5037] • Xml Editors initial load and refresh action for images and conref libraries has been tuned to use less web service calls (like superfluous DocumentObj25. GetDataObjectInfoByIshLngRefs) to get to the same information. [TS-11326|TS-11315|TS-11316|TS-11327|TS-8879] • Using the F2 keyboard short cut to rename a folder in a Browse Repository window would not respect the DEL button. In stead of removing folder name characters it would ask to delete the whole folder with a message like The folder '<folder-name>' will be deleted permanently, including all its objects and subfolders. [TS-9095|TS-11466|SRQ-4187]Publication Manager • If you close Publication Manager when it was not maximized to full screen, the next session would load the program around 200 pixels down. A first click however would move the window to the originally saved location. [TS-10564] • In Publication Manager, when a map is checked out, the delete of a <topicref> is always recursive. There was no delete warning message that you are deleting nested <topicref>s as well. Upon delete an improved message reading The selected object contains # topics that will also be deleted from the publication. is shown. [TS-11464|TS-10918|SRQ-4580] • Publication Manager is now able to show comments created before the topics were published to the Review & Collaboration site. This issue had a major impact on aggregated comment server situations. [TS-11104|SRQ-4234].Restriction: Note that this requires a hotfix on Review & Collaboration (Reach) for 7.4.0, see SRQ-4234.• The publication version numbers are now listed in the right order in the Differences with version drop-down list in Publication Manager. That parameter is located in the properties dialog for PDF outputs in the Output tab. [TS-11245|TS-11246|SRQ-4934] • The modal dialog appearing at each refresh in Publication Manager, stating The object 'FTITLE' has been changed by another application, and the new content has been loaded, now appear only once every Publication Manager session [TS-11441|SRQ-3032].SDL Knowledge Center Release Notes 55 2 Release Notes - SDL Knowledge CenterContent Importer • Content Importer no longer translates trailing spaces into an invalid @ishcondition condition value. For example otherprops="A B " will now convert to ishcondition="otherprops in (A,B)" instead of ishcondition="otherprops in (A,B,)" with a superfluous comma and null value. [TS-11176|TS-11248|SRQ-4845]Fixed Issues in 12.0.1 Authoring BridgeThe following Authoring Bridge issues are fixed in Content Manager 12.0.1 compared to 12.0.0.General Authoring Bridge • Client Tools Check In fails in EditingContentResolverWorker when the xml holds a 0x0B control character with error Unable to reach the repository '...'.. Often control characters like 0x0B come from copy pasting out of Microsoft Office applications. The issue was caused by the transformation of the error message (containing that control character) returned by the web services. Control characters will now silently be removed from the returned error messages to make sure that errors containing control characters reach the clients correctly. [TS-11467|TS-10591] • When submitting new editor templates the EDITORTEMPLATE. REMOVE.ALL.IDS plugin made sure that template xml files are stripped from any @id attributes, so when they are instantiated they all get newly generated identifiers. The Admin.XMLWriteObjPluginConfig. xml, which needs a matching submit in Settings > IWrite Plugin Xml, is now tuned to also strip comment identifiers (@cid) from the submitted template xml file. [TS-10659|TS-11476|SRQ-4257]JustSystems XMetaL • Using XMetaL 11 Reposistory > Check Out Document will no longer close other documents in their multi document user interface. [TS-10673]<oXygen/> XML Author/Editor • Publication Manager's Check Out with or Open With towards Oxygen shows Unhandled exception on DragDrop registration when asking for the password. The same error could occur when opening recent documents. [TS-11224|TS-11223|TS-10547|SRQ-4787]Fixed Issues in Content EditorA description of the issues we've fixed with this release.Copy/paste fixes We are now able to track content removed by a Cut The change tracking did not work sometimes when deleting selections within a single element. Specifically, when using Ctrl+X or the "Cut" button in the UI, the deletion was not tracked properly. These changes (deletions) are now tracked correctly, regardless whether using Backspace, Delete, Ctrl+X or Cut. Note that changes to selections that cross element boundaries are not tracked yet. Copying inline elements between documents works as expected When copying between different documents, spaces around inline elements were unexpectedly removed. This is no longer the case, and content is pasted in the same way it was stored in the original document.56 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Copying placeholders between documents works as expected When copying from one document to another, placeholders were pasted as text. Placeholders are now copied and pasted correctly, as-is, and the placeholders in the target document function properly. Copying multiple paragraphs between document works as expected There was a problem where the first two paragraphs were merged together when pasting multiple paragraphs from one document to another. Now multiple paragraphs are copied and pasted correctly from document to document. This fix is a result of the new method where content is copied and pasted in the same way it was stored in the original document; that is, as XML. Cut would not work the first time if the Clipboard extension was not installed When the Clipboard extension was not installed, and you tried to use Cut for the first time, the editor would not put the removed content on the clipboard. Now cut content is put on the clipboard, you can used Cut regardless of whether the Clipboard extension is installed or not. Cut content could not be pasted after undo After pressing undo, the editor also incorrectly removed any content on the clipboard. For this reason, after an undo, users could not longer paste content in the document. This is fixed so that undo has no effect on the clipboard. In Firefox, pasting an empty clipboard broke copy/paste functionality When no text was available on the clipboard, for example after trying to paste an image from Word, attempting to paste broke copy/paste functionality in Firefox. This is now fixed and while there are still situations where there is no content that can be pasted, trying to do this will no longer break the copy/paste functionality. In IE, pasting code into space-preserving elements resulted in extra unwanted empty lines When pasting content such as code into a space-preserving element such as a code block, the editor pasted the content incorrectly by adding a blank line after every line break in the source document. This is no longer the case. In Chrome, you could not paste HTML content properly into space-preserving elements When copying content such as code from Word, HTML content used to be placed on the clipboard including tags. The HTML content included tags that were not visible in Word but did come from Word. When pasting this content into a space-preserving element such as a code block, the editor pasted the content incorrectly by including the extra unnecessary tags from Word. This problem is fixed in all browsers so that we only paste the text. In Firefox, only the first line of code would be pasted properly into space-preserving elements When pasting code from HTML or Word into Firefox, only the first line would be pasted into the code block (or other space-preserving element). The rest of the content would follow in paragraph elements. With this fix, if you were to paste when the cursor is in a code element at the moment of pasting, then all content will be pasted into that element. In Document View, you could not cut text from an attribute It was not possible to select text from an attribute in the main document view and cut it. For example in the XML view, or when the attribute is displayed in the main document display using XSLT. With this fix, you can now select and cut text from an attribute. In IE, we placed tags from the Tags-on View on the clipboard When copying content from the Tags-on View not only the content was put on the clipboard but also text from the tags as well. With this fix, we copy just the content and nothing extra.SDL Knowledge Center Release Notes 57 2 Release Notes - SDL Knowledge CenterXML snippets copied from a text editor were interpreted as XML When copying XML content from a text editor, this was sometimes (when the copied structure was valid) pasted as XML. From now on, text copied from a text source is always pasted as text, regardless of its contents.Other fixes Applying an inline element to an entire cell could break table structure Before this fix, you could break the table structure when trying to paste an inline element into a specific table selection. The table structure was broken if you selected all the content in a cell, then pressed Shift+Right to expand the selection slightly over the cell boundary and then tried to paste an inline element into this selection. Inserting inline elements into all types of table selections now just changes the selected element only, and will not longer break the table. Text deleted in Word could be pasted later When the Word change tracking functionality was on and you started to copy, then all the content would be put on the clipboard including changes such as content deleted earlier in Word. Then you would be able to paste this already deleted content. With this fix, already deleted text cannot be pasted later. When pasting or adding content with the API, we were preserving too many spaces. When content was pasted or added with the API, we used to keep too many unnecessary spaces. The criterion is that when using xml: space= "preserve" then we intend to preserve the space. Other- wise spaces ought to be removed/cleaned up. In this bug the extra, "not preserved" spaces weren't removed. This fix ensures that extra spaces are cleaned upon when pasting and also when using the API to insert content. Setting UI language did not change the language in one view nor in the API When using the API method for setting the UI language, Editor.setUILanguage(), the language in most of the UI was updated, but not everywhere. In particular, the language was not set in two places: in the Tags-on view and in the API method for getting the language ( Editor. getUILanguage()). Setting the language with the API now has the same effect as changing the language manually using the UI, and all parts of the product are updated after changing the language. Find/Replace was not able to search for the "]" and "\" characters When searching a document for either of the "]" and "\" character, neither character could be found even when part of the document. Tables with a merged cell copied from Excel could not be pasted When a selection from an Excel table contained a merged cell, then this could not be pasted. Crash after deleting a row in between merged cells The editor crashed in certain circumstances when editing a table. This would occur for example, when a document contained a table with 5 rows, where row 1 and 2 had some cells merged together, and row 4 and 5 had some cells merged together. If you tried to delete the third row of such a table, the editor could crash. We've fixed this problem. Crash on right-click when using a schema with xs:unique When using a schema with xs:unique in the definition of an element, the editor could crash when using right click or the delete menu. The editor could crash in combination with certain xslt stylesheets When using an XSLT stylesheet that outputs html elements that are not related to a specific xml element (a script tag for example), this could crash the editor. This used to occur for example when using the spell checker and scrolling down in the document.58 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2The XopusNode.getPrettyName method did not work as expected on attributes The XopusNode.getPrettyName method did not work as expected when used on attributes. It would not return the "pretty" name specified in the configuration for an attribute, instead the name defined in the XML Schema. This has now been fixed, and this method returns the name defined in the configuration as expected. Links could not be copied from one document to another With the change to copying XML structure also when copying between documents, this bug does not apply any more. It is now possible to copy/paste links between different documents.Fixed Issues in 12.0.1 Web/App/DB ServerThe following Web/App/DB Server issues are fixed in Content Manager 12.0.1 compared to 12.0.0.Secure Token Service - Authentication and Authorization • Improved error messaging/handling for ISHSTS, ISHCM and ISHWS when the certificate thumbprint is not found avoiding generic errors Exception type: InvalidOperationException and Exception message: Sequence contains no elements. [TS-11468|TS-10632]Installing and Upgrading • In some situations, the command line InstallTool ended with an interactive mode Press any key to continue message. [TS-10910] • Admin.XMLBackgroundTaskConfiguration. xml configuration for ISHSYNCHRONIZETOLIVE- CONTENT event will now only synchronize Low resolution images out-of-the-box, matching the OutputFormat configuration. So in Settings > Background Task Xml the entry <plugin name=" ISHSYNCHRONIZETOLIVECONTENT" handler="SynchronizeToLiveContent"> is advised to be tuned to <plugin name="ISHSYNCHRONIZETOLIVECONTENT" handler="SynchronizeTo- LiveContent" ishcondition="FRESOLUTION='VRESLOW'"> which in turn means less objects will be synchronized which increases throughput. [TS-11478|TS-11046|SRQ-4709]BackgroundTask • Reducing the size of logs for BackgroundTask. exe and BackgroundTaskIso. exe by raising the default NLog.config level from Debug to Info. In practice the spinning wheel polling log entry will be avoided. [TS-10911|TS-11477|SRQ-4584].PublishService • When a publication was published to PDF with the Compare functionality activated, any failure in a comparison (either engine or result is not xml well-formed) between versions of specific objects made the whole publish process fail. Now only that specific comparison is skipped and the specific object is displayed in the final result as having been entirely changed. The publication itself completes. [TS-11365|SRQ-5060|SRQ-4837] • PublishService PrepareForExport function didn't always receive a properly wrapped xml validation error when the origin type was System.Xml.Schema.XmlSchemaException. [TS-10917|TS- 10862] • The length of publication titles can lead to exceeding Windows file path length limitations. Long titles are now truncated instead of failing the publication with errors like Following error occured: 76 - ???????????. [TS-10639|TS-11474|SRQ-4340] • More extensive handling of the DITA-OT log file makes potential errors and warning visible through EventMonitor, so without server access. The end result of publish is still the same, so whenSDL Knowledge Center Release Notes 59 2 Release Notes - SDL Knowledge CenterDITA-OT.log contains a BUILD FAILED, the status of the publish becomes Failed. More log file content will become available through EventMonitor. Everything starting from the first [Fatal Error] or XML document structures must start and end within the same entity. message - so more than the last 20 lines of DITA-OT.log. Unfortunately, the errors generated by the various DITA-OT versions are not consistent enough to generically fine tune the publish status result of Release Candidate or Draft - it is different per type like CHM, PDF, etc. [TS-10788|TS- 11475|SRQ-4972|SRQ-4201|TS-11601] • The internal EDT conflict that made some PDF publish fail whenever Content Manager was upgraded from 10.0.X or earlier to 12.0.X has been solved by code changes in PublishService, ISHPublUtil. vbs and publish.wsf. [TS-11317|TS-11419|SRQ-5249]Translation Organizer • Translation Organizer is now more resilient regarding imperfect network setups causing the occasional HTTP status 502: Bad Gateway error. In the past this caused Translation Jobs to move to a manual recovery status requiring user action. Now safe (idempotent) calls like retrieving items or status moves will be retried; but for example an actual second submit of a job to the translation management system could incur double costs which is a conflict that still requires manual handling. [TS-11096|TS-10422|TS-11090|SRQ-4195|SRQ-4714] • Some transmission issues have also been fixed, such as the processing of Logical Identifiers having GUIDs with dots (.) as separators. An issue which was introduced on 2016/12.0.0. [TS-11273|TS- 11269|SRQ-4960] • Added example uri of SDL WorldServer and SDL TMS into the TranslationOrganizer. exe. config. [TS-11473|TS-10789|SRQ-4464]Other • In some upload and prepare situations, cancelling a publish process from Content Manager failed to unlock the publication in Content Delivery. This has been fixed. [TS-11398|TS-11399|SRQ-5088].Fixed issues in version 12.0.0An overview of bug fixes and issues that were addressed in Content Manager 12.0.0, compared to the previous version of the product.If you are upgrading from a release prior to Content Manager 11.0.0, refer to the release notes for the relevant versions in-between.For your convenience, bug fixes implemented in Content Manager versions 11.0.3, 11.0.2 and 11.0.1 are included in this document as well, by order of recency.Fixed Issues in 12.0.0 Web ClientThe following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.60 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Web Client • The change Tracker preview always toggles a version x to y (x > y) to a y to x comparison, while in the Client Tools you have full control over the order. [TS-10447|SRQ-4210] • Microsoft Internet Explorer 11 can suddenly take up 20% CPU resources even though the web client is idle. This was caused by the setInterval function from the menu which was triggered for every menu while Google Chrome and Mozilla FireFox don't do this. [TS-9742] • Rendering a decimal displayed via the Maps folder list view (MasterDisplay. xml) performs a decimal round up. For example a value 7.6 is rendered as 8. [TS-10234|SRQ-3992] • The filename which was generated while downloading content objects from the web client contained + (plus) instead of (space) due to UrlEncoding. The newly suggested filename is TestIm- age2=GUID-17F48625-E148-486E-9186-1B3B9BC11874=1=aa, ab, af, am, ar, as, en=Low.png, while it previously was TestImage2=GUID-17F48625-E148-486E-9186-1B3B9BC11874=1=aa,+ab,+af,+am,+ar,+as,+en=Low. png. [TS-9719|TS-9718|SRQ-3234] • When requesting the file/blob details of an EventMonitor entry, you could end up with Error executing child request for handler 'System.Web.Mvc. HttpHandlerUtil+ServerExecuteHttpHandlerWrapper' caused by ID confusion and a double Byte Order Mark (BOM) encoding. [TS-9138|TS-9163] • Uppercase all field names in StatusTransitionsandInboxesConfiguration. xml to avoid error messages such as The field FMasterType does not exist. [fe:"FMasterType"]. [TS-9177|TS-9167| SRQ-2640] • The Context Builder section Saved contexts has been removed from the standard dialog as it relied on obsolete API functions and card type CTCONTEXT. [TS-9212|TS-9205]Fixed Issues in 12.0.0 Client ToolsThe following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.Client Tools and XML • When you have multiple accounts, and at startup you get prompted for your credentials, but you Cancel this operation, it resulted in a cosmetic unwanted error Microsoft .Net Framework - Unhandled exception has occurred in a component in your application. [TS-10440] • While in edit mode of a tree node or a list view in the Client Tools - like for example Folder rename - all keyboard short cuts are blocked or don't do what is expected. For example during a folder rename the Del key will remove characters and not ask to delete the folder. [TS-10556] • When doing a Batch Metadata operation, the resulting Update window does not always show the information. For example it could end with a window stating Update Completed with 3 Errors but you had to click the Refresh button to actually see the entries. [TS-9545|SRQ-3233] • Client Tools will no longer allow a protocol handshake using the SSL3 protocol. This change should avoid a vulnerability known as the POODLE attack where it is possible for an attacker to forcefully downgrade the SSL/TLS protocol used by a client/server connection until the peers choose to communicate over SSL3. This allows an attacker to eavesdrop on information exchanged between the parties over SSL connection using SSL3. The attack is identified by CVE-2014-3566. By default the .NET framework runtime (System.Net.ServicePointManager. SecurityProtocol) allows a handshake using protocol SSL3 or TLS (1.0). By configuration we force a handshake among protocols: TLS (1.0), TLS11 (1.1) and TLS12 (1.2). [TS-9114|TS-9428] • Configuration change in file metadataconfig. xml to avoid that the FDESCRIPTION field isSDL Knowledge Center Release Notes 61 2 Release Notes - SDL Knowledge Center emptied when creating new versions. The configuration now separates new version by the introduction of the Properties_NewVersion_* forms from Check In As or Duplicate operations. [SRQ-2942|TS-9450|TS-9469] • Some list view title fields are cut off and shown as ... in Search results/Repository folder content while they have a proper title available. The most likely cause of this were CR/LF in the metadata field. Those are now normalized for rendering purposes to a single space. [TS-8703|TS-9045] • Browse repository version selection should be cleared if no object is selected in the list view. [SCTS-756|TS-8828] • Check out (In Context Edit) from Publication Manager doesn't refresh the publication's resource libraries for variable inserting. [SRQ-2098|TS-8558|TS-8967] • Additional checks in Client Tools browse repository result in errors and in the folder not being opened, showing warnings such as The conref range “xxx" is invalid!. [SRQ-2404|TS-8790|TS-8938] • The multi value assist, configured on fields such as fall back languages didn't respect the order. The assist on the FallbackLanguageField field is now configured in MetadataConfig. xml to no longer do sorting on its values. [TS-8934|TS-9046] • Inserting a <topicref> to a Library Topic now sets @format attribute to dita and not to typical file extension xml which confuses DITA-OT downstream. This was altered in MetadataConfig. xml by adapting the <script> block in <ishfrmfield id="HRefField".... [TS-9091|TS-9086| SRQ-2548] • Offline working from local storage was interrupted by a message stating An error has occurred while opening external DTD 'file:///.... [TS-8796|TS-8969|SRQ-2260] • When having more than one account configured, it could be that Authoring Bridge actions Set Condition, Insert Image, Insert Conref and Update Conref unintentionally use the default account instead of the account connected to the open document. [TS-9228|TS-9218]Preview • Preview resolving link text will no longer render a superfluous Link text cannot be resolved if the <xref> holds an image. [TS-9781] • Space between <tm> tag and <ph> tag is not displayed in the preview. [TS-9284|SRQ-2747] • When a user requests to Cancel a Preview, the cancel action will message the ContentResolver which in turn cancels redundant web service calls so that a long-running preview or preview switch reacts faster. [TS-9691|SRQ-3190] • Preview does not resolve @conref having a case-sensitive @conref/@id combination. This can happen when you switch the default configuration of BlobExtractMetadata IWrite plugins parameter DocumentUpperCase to No for ISHSYSTARGETSTOMETADATA and ISHSYSFRAGMENTLINKSTOMETADATA. [TS-10079|TS-10080|SRQ-3770]Search • Number of hits found for the same search query in Web Client and Client Tools differs. This problem only occurs when images with LanguageApplicability (also known as multi-lingual) are part of the result set. The full text index query is now optimized so that this problem is avoided when searching with one language. The problem is a lot less frequent when searching with search criteria holding multiple languages. [TS-7646|TS-9044|SRQ-1972] • Navigating search results suddenly shows You have reached the maximum number of hits '4998' allowed by a search. while there are more pages available according to the search results control. The search results was hardcoded to 5000 hits spread over a maximum of 50 pages using the default page size of 100. Because of LanguageApplicability you even got less pages causing the 499862 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2 vs actual 5000 difference. Now the search can go beyond this hardcoded value allowing you to browse the full result set if desired. The initial result set retrieves enough information to fill up the first 3 search results pages. When you request page 4, the search will be re-issued requesting for 3 times the earlier total hit size. So the initial 3 pages of 100 results (300) will trigger a search of 3 times 300 results (900) when requesting page 4, and so on. [TS-8490|TS-9055|SRQ-1970] • The order in the result lists of Client Tools and Web Client is different. This has been corrected. [TS-8664|TS-9042]Publication Manager • Query Folder containing Publications fails with Parameter 'name' or 'text' is required. [TS-10562] • Improved behavior when moving expanded nested topics in the tree view. This could cause the application to freeze. [TS-10502|SRQ-4236] • Autocomplete using options Candidate for baseline or Baseline is fine tuned regarding non- recursive and recursive version calculation. [TS-10038|TS-10039|SRQ-3736|TS-10053|TS-10074] • the message for circular references Warning: The object x is mentioned within the object itself, creating a circular reference has been removed. The preview will render a This conref is not defined. [TS-3449] • When using Remote Desktop Services (mstsc/rdp), you could run into hte error System.Runtime. InteropServices.ExternalException (0x80004005): A generic error occured in GDI+. when navigating the tree view. This cosmetic error is now handled appropriately. [TS-8933] • The Variables listing doesn't show all variable assignments (@varid) and variable references (@varref) present in the publication. So some This variable is defined 2 times. and This variable is not defined. are potentially missing. [TS-9822|TS-9802|SRQ-3359] • Creating new publication version ignored the account's default language setting but used the user's language. We adapted MetadataConfig. xml ishfrmfield name="PublicationSourceLanguageField by switching from variable currentuserlanguage to defaultlanguage. This is typically noticed on environments that rely on multiple source languages for editing. [TS-9725|TS-9723|SRQ-3227] • When creating a branch 1.1.1 of publication version 1, the baseline is not duplicated, it picks up the recent available version rather than mirroring the baseline of the branched version. The fix consists in a Publication Manager change and a server-side change on API call PublicationOutput25.Create.[TS-9618|TS-9617|SRQ-3133] • Publication Manager freezes with an unresponsive dialog asking for The local storage contains a writable copy of <name>. Do you want to Leave the local file. Actually the local storage was locked, which also affected the Authoring Bridge in your XML editor, resulting in messages warning you that you should wait or even Server Busy messages. [TS-8886|SRQ-2294|TS-8615] • Status messages such as Retrieving objects (2700 of 24474)... that were suppressed because of multi threading changes are now restored. [TS-8863] • Unexpected revision. A more recent revision was expected when retrieving the content. is shown in Publication Manager preview after a Checkout with... to the XML editor and when you immediately do a Checkin again (within 30 seconds). The 30 seconds cache value is now lowered to 5 seconds and the routine of retrieving the file from the repository, saving it, previewing it, checking it in and saving the final result after plugins has been tweaked. [TS-8827|TS-8678|SRQ-2418] • While previewing images of type 3DXML or SWF (Adobe Flash), the preview actually rendered an HTML statement starting with <!DOCTYPE html PUBLIC ... instead of triggering the plugin that is capable of rendering the provided image binary. [TS-8966|TS-8944] • The commenting Refresh button was disabled, now it is always enabled. [TS-9040|TS-8685] • Refreshing a Publication Manager session could result in Object reference not set to an instance of anSDL Knowledge Center Release Notes 63 2 Release Notes - SDL Knowledge Center object when the root DITA map of the publication was replaced in another Publication Manager session meanwhile. [TS-9013|TS-9088] • Adding a newly created topic to the tree can result in warning Cannot resolve link text for topic reference '<logicalid>'. A version is required to use this operation.. This issue is caused by a timing conflict between the refresh of the preview and the automatic version selection process (autocomplete). [TS-9087|TS-9027]Content Importer • When using re-GUID-ize on lower-cased filenames, the initial lower-cased guid was not replaced. [TS-9883] • <xref> elements won't pull the target title text from an element within a topic like <figure>, <table>, etc. It will show TopicGUID#TopicGUID/ElementID instead. The xml_code_fragments. txt file contains a specific topic that failed to be imported due to the fact that it includes the comma-space character sequence in its <title> element. [TS-9275|TS-9274|TS-9276] • When using ContentImporter. xsl to give the DOC-LANGUAGE field multiple values like da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR to import images, you received the error The LovValue da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR does not exist. [label:"da-DK, de-DE, en-GB, en-US, fr-FR, it-IT, pt-BR"] [102001;InvalidObject]. The rewritten, faster DocumentObj25 API offer a DocumentObj25. TryGetMetadata which returns the above error when submitting multiple languages. When language applicability is used, Content Importer will now use DocumentObj25. RetrieveLanguageMetadata to decide if it needs to Update existing or Create new content objects. [TS-9480|TS-9489|SRQ-2957] • Double clicking on a row makes the application crash with Application not found. [ST-8424|TS-9119] • Content Importer prepares the title metadata field (FTITLE) for import but will now strip any carriage return (CR) characters that it extracts from the XML <title> value. [TS-7997|SRQ-722|TS-9116] • The filemap.xml is built recursively by first inserting all files of a folder in alphabetical order, starting with the to-be-imported root folder, then the folders in alphabetical order. Content Importer now imports files according to the filemap.xml file. [TS-9120|TS-7657|SRQ-1036] • The status of imported objects can be changed by using the Post conversion XSL where you specify a metadata XSL file like for example ContentImporter. xsl. Content Importer can now also use @valueType on <ishfield>. [TS-9129|TS-7053] • Importing multiple image resolutions (e.g. carwash.png and carwash.eps) resulted in two different logical objects in the repository when the wizard's Back button was used or when you used the re-GUID-ize option. When moving through the wizard the image resolutions will be imported into the same logical object identifier. [TS-9110|TS-9109|TS-9111|SRQ-2544] • Content Importer is unable to resolve non-XML objects on <xref>, <link>, <longdescref>. Following the OASIS DITA specification on http://docs.oasis-open.org/dita/v1.2/os/spec/common/theformatattribute.html the @format attribute can be used to determine to which object type an @href is referring to. [TS-8091|TS-9131] • Content Importer hangs after conversion when there is an apostrophe ' in a folder name. [TS-7203| SRQ-695] • Content Importer does not update or create the import.status after an import. File import. status will be adapted when importing pre-converted files. [TS-9170|TS-9169|SRQ-2610]64 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Fixed Issues in 12.0.0 Authoring BridgeThe following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.General Authoring Bridge • When a browse dialog is opened to select an object, and the selectable object types are set to all types (Topics, Maps, Library Topics, Images and Other (Word, PDF, ...)), the filter is set to XML object types (Maps, Topics, Library Topics) on initialization. The default filter in this case will now have Objects of type specifying (All) allowing Other (CTTEMPLATE) selection. [SRQ-3265|TS-9825] • When attempting to insert a @conref to a section of a document that contains @varref definitions, the yellow rectangle selection extends to the end of the document, instead of including only the current block. Replacing the tags <ph varref="productname"/> with <ph varref=" productname"></ph> corrects the problem so that the selection tool only selects the current block by default. The technical issue is that browser don't like self-closing <div/> elements. [TS-9752|SRQ-3271] • When you want to update an existing <xref> element that references an element in a topic with bookmark, the selection is set to the Select bookmark dialog, but the selection is not shown in the preview. [TS-8622] • When you update an image with a new image binary, therefore with different content, then the new image is now displayed in the XML editor. Depending on timing, it requires the user to trigger a Refresh F5 request. [TS-9768|TS-8879|SRQ-3069|SRQ-2132] • Access keys for our SDL Knowledge Center menu in all XML editors are altered in a way that they are all unique now. [TS-8972|TS-7995|SRQ-1340] • Some ja-jp translation corrections have been done in Authoring Bridge, such as WhereUsed, batch metadata Current Values, etc. [SRQ-2460|SRQ-2496|SRQ-2374] • When you check out a topic while the preview window is still loading, it may crash the application with a stackoverflowexception caused by the XULRunner preview engine. [TS-8928|TS-8929|TS- 8930|SRQ-2294]JustSystems XMetaL • *[ishcondition]: before in infoshare-base-override. <a href="/tags/CSS/" rel="tag">css</a> does not work for <topicref> in a map because conflicting styling exists in map-base.css. When you have an @ishcondition on a <topicref>, the <topicref> is shown in gray and the condition text is also shown in the preview. [TS-9542|SRQ-3036] • A topic cannot be associated with a key definition file when it is not checked out (read-only). [TS-10468] • The behavior of JustSystems XMetaL 9 and 10 is now fine-tuned together with XMetaL engineering and usability changes on our AuthoringBridge implementation. When inserting an <xref> or <link>, the dynamic text resolving of XMetaL wasn't triggered. This meant that you had to do a manual Edit > Refresh all references (F11). Our common efforts are packaged in this release. [TS-9780|TS-9779|TS-9784|TS-9790|SRQ-3272]Important: By default the dynamic resolving behavior of XMetaL is not enabled. To activate this go to Tools > DITA Options > Update Content tab and select the checkbox in front of xref/ related-links.• When opening a topic in read-only, and then checking it out using the editor's menu or toolbar, a subsequent check in command on this object would fail with Following error occurred whileSDL Knowledge Center Release Notes 65 2 Release Notes - SDL Knowledge Center checking in: The object 'xxx v. y - language' is currently in use. [TS-9754|TS- 9753|SRQ-3289] • A failed Check in will now attempt to reopen the file if you get an exception triggered by the IWrite* plugins like Following error occurred while checking in: The plug-in "CHECKREVIEWERFILLE- DIN" returned the following error: "Plugin 'CHECKREVIEWERFILLEDIN' reports that field 'FREVIEWER' is empty for object 'GUID-8C8F01ED-9785-47DE-9A00-1F8AAFD94E7D' and should be filled in when field 'FSTATUS' is changed from 'In progress' to 'To be reviewed'". [TS-8742|TS-8968] • When having an object open in the XML editor in View mode (read-only), you can Check out that object in Publication Manager. The XML editor is now notified that the object has changed. [TS-9149| TS-8962|TS-8960|TS-8630|SRQ-2344]<oXygen/> XML Author/Editor • A file that contains a single quote (') in its title, hence its file name, remains checked out after a Check in action. [TS-9944] • When you check out a topic in Publication Manager on a Japanese OS, oXygen hangs. It does not hang when the system locale is set to another locale (e.g. Dutch Belgium). This fix contains an adaptation that will trigger an open using a new thread instead of waiting for the main thread. This change was made after validating with the oXygen support team. [TS-9908|SRQ-3581] • The repeated checking out a map leads to error The object is already in use by another program. [TS-9884|TS-9714|TS-9695] • Closing oXygen and canceling all save requests crashes with java.lang.NullPointerException in com.sdl.trisoft.triab.AuthoringBridge. getConfigurationManager. [TS-9512| SRQ-3013] • oXygen 16.1 - An error message Value can not be null raised by GetWorkItemByPath appears after any URL is opened, when the Authoring Bridge is installed. [TS-9665|TS-9620|SRQ-3034] • The editor hangs when multiple files are opened from the Browse Repository dialog or from an external program like Publication Manager. The workaround is to use the tool bar which is resolved within the application while the right-click-menu are resolved over the operating system. The fix is that the multiple files are queued and opened when the editor allows it. [TS-9324|TS-9467|TS- 8688|SRQ-2800] • When checking in a topic, depending on timing, you could occasionally see an editor dialog displaying Could not save the document due to: C:\Users\...\InfoShare\...... =en=.xml (Access Denied). This is a cosmetic error without data loss. Behind the scenes the file is handled and refreshed by multiple application threads. The file system read-only attribute is used to indicate that a file is no longer writable which can cause the generic Access Denied to appear from the other application threads. [TS-9409|TS-9468|SRQ-2632] • Refreshing using the SDL Knowledge Center > Refresh menu occasionally messes up resolving of images and conrefs. [TS-8745|TS-8596]Arbortext Editor • When having a DITA Map open in the XML editor in View mode (read-only), you can Check out that object in Publication Manager. The XML editor is now notified that the object has changed. [TS-9041|TS-8661]66 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Fixed issues in 12.0.0 Content EditorA description of the issues fixed in the Content EditorEditing issues Prevent two consecutive spaces This editor does not allow two consecutive spaces. Multiple spaces are not handled well by the editor and would for example cause cursor problems. The editor already prevented multiple spaces when pressing the spacebar. However there are other situations that can result in multiple spaces in the document and these are now fixed.Cannot insert a link in some other elements than paragraph The Insert link button was not enabled in situations where there are multiple elements that have the hyperlink role, for example in a code block.Error when saving document with conref to xref When creating a conref to an xref element, an empty href attribute was created on the xref element. Template will overwrite existing attribute for empty children When an element is applied on a selection, empty elements in that selection have their template applied again as well. When such an element has a template for an attribute, the template value would overwrite the value in the document. Now the template is applied only to elements with content.Copy/Paste issues Links are not pasted when pasting from Word 2013 into IE11 With certain HTML structures, links were stripped out of the content when they were pasted. This was the case when copying HTML structures in Word 2013. Now the links are maintained and can be pasted from Word 2013 into IE11. Copy and cut do not place content on system clipboard when using the buttons in the UI Content was copied and correctly pasted when pasting within the same document, but it was not available for pasting to external applications. Now the content is placed on the system clipboard and available to external applications. Cut from the breadcrumbs sometimes leaves structure behind Cut would not cut the exact element, but a selection which in some cases did not include the entire element. This now fixed. Incorrect cursor behavior after pasting a table from external source After pasting a table from <a href="/tags/Microsoft_Word/" rel="tag">Microsoft Word</a> for example, the cursor behavior in the editor would not be correct, and required several key presses instead of one to move from one cell to another.TypeError when pasting some types of lists from Microsoft Word into Chrome When a list with items with multiple paragraphs was pasted, this could not be processed correctly. Now you can even paste lists that include paragraphs.SDL Knowledge Center Release Notes 67 2 Release Notes - SDL Knowledge CenterAPI/Config issues addEventListener does not accept an object as second argument The addEventListener function was documented to accept both a function and an object as the second argument. Using an object was not working, and this option is now removed completely. hideStatusbar configuration option was ignored This configuration option can now be used to disable the breadcrumb bar.Other issuesIME command is available when no document is loaded The IME command (and any button for the IME command if configured for the toolbar) was always available even if no document was loaded. When it would be pressed in that situation, the editor would crash. Now the command is only available when there is a document loaded. Find/replace becomes very slow in IE when a lot of results are found A somewhat slower response for longer documents is expected, but in IE the response time became unacceptable with more than 100 results. The speed is now reasonable for up to 1000 results, similar to the performance in Chrome and Firefox. Navigating away on error When an error occurred, the message would be shown for moment before navigating away to another screen. The editor is now no longer navigating to another screen when an error happens.No support for nextCatalog in the XML Catalog An error was shown when loading a catalog that points to another catalog using nextCatalog. Now this is supported. XML view collapses completely In some situations the XML view would collapse to the root element. This no longer happens. Inline SVG is not displayed in IE9+ Inline SVG is now supported again in Internet Explorer. Incorrect reference stays stuck in loading state When for example an xref tried to display it's title from another location, and that failed, the display would keep showing loading. Now an error message is shown instead. Maps in search results Browsing for content reuse will now return DITA Maps (ISHMasterDoc) similar to search results when the selectedtargettype is set to conref, link or hyperlink. [TS-5782|TS-8973]Fixed issues in Content Manager version 12.0.0 Web/App/Db serverThe following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.68 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Secure Token Service - Authentication and Authorization • Brute-force attacks, also known as exhaustive key search, systematically check all possible key or password combinations until the correct one is found. To protect unauthorized system access through this type of attacks, the default value of the registry key AuthTriesBeforeLockout has been set to 30. A value of 0 disables the locking feature. All components of Content Manager use this registry value at login time. With the default value, after 30 unsuccessful login attempts a user account is locked. Only a system administrator can reset the password of a locked user account. [TS-8909] • Logging in on ISHCM ends in error ID3206: A SignInResponse message may only redirect within the current web application: '/InfoShareAuthor' is not allowed. due to a trailing slash (/) misalignment. [TS-10050|TS-10055] • When using a web browser to ISHSTS (Content Manager) as your identity provider, the system returned the message Incorrect credentials or no authorization when really your password was expired. This expiration is controlled through registry entry AuthMaximumPasswordAge expressed in days which defaults to no expiration. In the web client you will now receive a more distinct message reading Your password has expired. Please enter a new password or contact your system administrator. [TS-9465|TS-9433]Restriction: The Client Tools rely on the active protocol (WS-Trust) for authentication where we cannot easily distinguish between a regular no access or a no access because your password is expired like we could do for the web client which is based on the passive protocol (WS-Federation).• ISHSTS will now always show a Change Password hyperlink that you can use to change your password, even when expired. [TS-9440|TS-9466|SRQ-2882] • A successful login with an account part of the AuthExemptAccountList registry setting negates all successive password expiration rules of other users until the process recycles. AuthExemptAc- countList is typically only used by customers that have built a Content Delivery on top of Content Manager. [TS-9442|TS-9432] • Code base UserContext. Authentication throws a Object reference not set to an instance of an object. if the incoming token doesn't contain our name claim (http://schemas.xmlsoap.org/ ws/ 2005/ 05/ identity/ claims/ name) for look up through USER field FISHEXTERNALID.The generic application error is replaced with a RequiredParameterNotFound error where we made sure it is explicitly logged as well. [TS-9097|TS-9154] • You need an external id (FISHEXTERNALID) entry on a user profile to allow matching with the name credential on an incoming token, typically for external STS systems like ADFS or Windows Authentication enabled ISHSTS. When adding an entry using DBUpgradeTool (DBUT) using option (1) Maintenance (System integrators only) then (8) Append an user's externalid for initial STS logon, the entry was always added with sequence value 1. In other words the tooling didn't keep into account that it was the second, third,... external id on the user profile. DBUT didn't report any error. It is only after logging in, when entering the Settings > Users section that you got an error An unexpected system failure occurred. An entry with the same key already exists. where the code essentially trips over a duplicate sequence identifier. [TS-9604|TS-9591| SRQ-3100]SDL Knowledge Center Release Notes 69 2 Release Notes - SDL Knowledge CenterAPI • Consider the tree structure of objects - typically called the publication - where publications link to maps, maps to topics, topics to libraries and then to images. The Delete function will use this order to delete, as nobody references the publications they will still be deleted. When doing a Delete on a folder in the Client Tools, the Client Tools will recursively Delete all of the complete objects in full by specifying a PublicationOutput25. Delete and DocumentObj25. Delete call only using the logical identifier (e.g. GUID-A as identifier, no version information, etc). To be able to block an expanded object delete we introduce two registry keys which are disabled by default: • TRISOFT_INFOSHARE_DocumentObjDelete_DenyExpandedLogicalObjectDelete: When true, it block a delete of a Logical object if there are children such as version and language objects. Note that the Logical object delete is allowed if there are no children. • TRISOFT_INFOSHARE_PublicationOutputDelete_DenyExpandedLogicalObjectDelete: When true, it blocks a delete of a Logical object if there are children such as version and language objects. Note that the Logical object delete is allowed if there are no children. The blocked action will result in error -25 in the line of: A method call is invalid for the object's current state: Deleting the object including version and language objects is not allowed (TRISOFT_INFOSHARE _DocumentObjDelete_DenyExpandedLogicalObjectDelete). [TS-10087|TS-10096|SRQ-3834] • When updating fields of type NUMBER with a value between 0 and 1 such as 0.6, you receive the error Value "0.6" is invalid for the "..." field of object "...". Attempted to divide by zero. [c: ce: ct: f:1014 fe:FTESTNUMBER ft:Number fmin:0 fmax:1] [TS-10209|TS-10210|SRQ-3992] • The data layer (Core.FieldValue) will recognize an undo of a field change within one request. Suppose the status field (FSTATUS) of a content object holds To be reviewed, the first IWritePlugin implementation changes the value to Reviewed, but later because of business logic the initial value To be reviewed is restored for saving in the repository. The system then expects a status transition to be in place from original value To be reviewed to new value To be reviewed which is typically not present. So technically the FieldValueStatus will now revert to original as well if you reset the value to the original. [TS-9517] • API enumeration conversion, like for example ISHLevel, is more specific when the conversion fails. Before it would return the message There is no parameter 'value'., now the message will read The parameter '...' with value '...' is invalid. The value '...' cannot be converted to an '...' object.. [TS-9299] • The DocumentObj25. Update doesn't purge all <preTranslation> tags. As a result the IWritePlugin VALIDATEDTD will block your update with a message similar to The element '...' has invalid child element 'preTranslation'... [TS-9681|TS-9677|SRQ-3108] • The PublicationOutput25. Create call when creating a branch 1.1.1 of publication version 1 did not find the original baseline. [TS-9618|TS-9617|SRQ-3133] • API performance improvements are coming from refactored Contains operation on classes UniqueLongList and UniqueStringList, revisited query processing of InformationSet, nullable TableFieldValues, enumeration conversion and more. [TS-8889|TS-8792|TS-7451|TS- 8794|TS-8459|TS-9048] • For a baseline still in use by a publication, the delete failed with: An item with the same key has already been added. This is changed for a message saying that the baseline object is still in use. [TS-8808] • You were unable to delete an image configured as Thumbnail resolution when linked to the logical Thumbnails preview overview. This resulted in The object cannot be deleted, because it is still used by one or more objects. Please generate a report or a full-text search to see where it is used.. [TS-8936|TS-9018|SRQ-2405] • API calls to submit Unicode information to EventMonitor and BackgroundTask will now make sure that a Byte Order Mark (BOM) is part of the submitted string. [TS-9106|TS-9126]70 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2• The PublicationOutput25. SetMetadata calls and the deprecated PublicationOutput20. Publish calls will no longer trigger an Export4Publication event to trigger publishing when moving the PublicationOutput from status Pending to Pending. This avoids the situation where an unintentional double-click in Publication Manager triggers multiple publish operations. [TS-8528| TS-9155] • TranslationJob25. UpdateTranslationJob3 throws invalid status transition error -134 The object "{object}" cannot be moved to the selected status because it is not allowed by the current workflow. when unchanged status information is provided in metadata. [SRQ-2637|TS-9166|TS-9189]Installing and Upgrading • InstallTool (IT) GenerateInstallPlan will add <copyaction>replace</copyaction> for text file extension .Master. [TS-10550] • InstallTool (IT) installplan on 2014/11.0.x copied the plugin DLLs like Trisoft.InfoShare. Plugins.dll into #!#installtool:DATAPATH#!#\ AppCore, so when the DATAPATH and APPPATH input parameters are different the plugins are not in the App folders. This was changed to using #!#installtool:APPPATH#!#\ AppCore. [TS-10549] • DBUpgradeTool (DBUT) on Oracle ends with ORA-01013: user requested cancel of current operation in ISOURCE.DBUT_CHECKISHADMIN due to slow network connection. The default 60 seconds timeout is now raised to our StandardCommandTimeOut value (600 seconds). [TS-9107|SRQ-2587] • DBUpgradeTool (DBUT) on Oracle has an optimized FullAnalyze relying on new Oracle code to gather statistics. [TS-9115] • DBUpgradeTool (DBUT) scenario file named Trisoft.Setup.DBUpgradeTool. Plan.xml received a new section named Database Validation to optimize getting errors/warning earlier on large databases. [TS-10083] • Several COM+ classes such as DocumentObj20, PublicationOutput20, Publication20 and TranslationMgmt have their transaction requirements reduced from RequiresTransaction to UsesTransaction. This avoids database locking problems and contributes to improved performance. [TS-8832|TS-8831] • DBUpgradeTool (DBUT) running a Microsoft SQL Server database re-index operation could end with a System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. after 1 hour. The crindex.sql was adapted and now configured as a <upgradeFile> in the Trisoft.Setup.DBUpgradeTool. Plan.xml giving it theoretically unlimited runtime. [TS-8807] • DBUpgradeTool (DBUT) connecting to Microsoft SQL Server using integrated security (Windows account) stops with System.NullReferenceException: Object reference not set to an instance of an object. during ProjectConfiguration disposal. [TS-8946|SRQ-2536] • DBUpgradeTool (DBUT) is failing on Microsoft SQL Server when using integrated security (Windows account) and without sysadmin privileges. More precisely when executing CheckMinimalUserRoles. sql which results in Could not obtain information about Windows NT group/user 'DOMAIN\USER', error code 0x6e. (ErrorCode= 15404). The reason is that Microsoft stored procedure xp_logininfo throws. Code was rewritten. [TS-9098|TS-8961] • InstallTool (IT) warns about Error while removing private queues: System.InvalidOperationException: Message Queuing has not been installed on this computer. when uninstalling an 11.0.0 version which out-of-the-box doesn't rely anymore on Microsoft Message Queuing (MSMQ) technology. InstallTool will check for presence of parameter QueuingEnabled in installplan. xml before attempting a queue uninstall. [TS-8978|TS-8725]SDL Knowledge Center Release Notes 71 2 Release Notes - SDL Knowledge CenterDatabase Layer • When rebooting an Oracle database server it can cause active client processes on the web/app server to return Establishing a connection to "..."failed after 15000ms with: Connection request timed out [errNr:-1000]. In case client processes - such as our IIS Application Pools, TranslationBuilder, Crawler, BackgroundTask, ... - notice a misbehaving Oracle connection, they will append "Validate Connection"=true to the connection string to force connection validation. When it happens, the logging will show a warning reading in the line of Trisoft.InfoShare.Configuration.Database. DatabaseConfigurationOracle.GenerateConnection Switching to a connection string with 'Validate Connection' enabled to enforce valid connections in the connection pool. Potentially caused by unre- sponsiveness of the environment/network/database. [TS-9527] • In case of missing or incorrectly installed Oracle.DataAccess components, you could end up with a generic System.TypeInitializationException near Trisoft.InfoShare. Configuration resulting in empty message and missing ORA-number information. A more descriptive SystemFailureException will be logged now. [TS-9457|TS-9456] • When running Translation Management on the Other content object type - also known as Template (CTTEMPLATEL) - you could run into errors stating that you are not allowed to attach a USER object (card) to the Translator (FTRANSLATOR) or Reviewer (FREVIEWER) fields. The specific error looks like <resource resourceid="InvalidMember" number="-2147220240" classname=" ModActionList" method="ValidateActionList" severitylevel="6"><desc>InvalidMember(c: -91919300 p: 7694 f: 708)</desc>.... The fix is to introduce the required memberdefinition on the CTTEMPLATEL card type so the USER card type can be assigned to the FTRANSLATOR and FREVIEWER fields. [TS-4657|SRQ-4179] • For Microsoft SQL Server installations, we aligned the order of the ISH_TOINDEX_1_I1 index to match up with the more performing Oracle RDBMs version. Indices ISH_EVENTPROGRESS_I1 and ISH_EVENTPROGRESS_I2 were optimized in order to improve EventMonitor performance. [TS- 10290|TS-10291] • The Oracle data layer CARDINALITY hints at indicating the number of expected results are no longer supported and replaced by OPT_ESTIMATE. [TS-10175] • The Oracle data layer is optimized for the query that marks entries as deleted in the ISH_* tables. [TS-10152] • The Oracle data layer received a performance boost when handling larger LONG STRING fields, such as FISHREVISIONLOG, through an optimized change detection check. [TS-10015|TS-10030|TS- 10057] • The SQL Server database job no longer includes a DBCC CHECKDB command to perform a SQL database integrity check. The task has been removed from the standard InfoShareJob to improve performance on large databases running on SQL Server. [TS-8822] • Creation script ISH_CreateTables. sql for new Microsoft SQL Server databases is now updated to be on par with the upgrade scripts. [TS-9273|TS-9477] • Oracle Data Access Client (ODAC) was raised from 11.2.0.4 to 12.1.0.1.2. This version offers better transaction handling. For .NET components even less distributed MSDTC-promoted transactions. [TS-8889|TS-8749] • DBUpgradeTool (DBUT) running on a large database (around 6 million objects) ended prematurely with the message System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. This typically happens during Creating the database tables indexes (crindex.sql). [TS-9777|TS-8807] • Oracle connection strings are shared between the COM+ and .NET code base. The incoming COM+ connection string (Provider=OraOLEDB.Oracle.1;Password=isource;User ID=isource; Data Source=ISH.WORLD) was typically converted to .NET (Password=isource;User ID=72 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2 isource;Data Source=ISH.WORLD), thereby dropping any other parameter name/value combination. From now on the connection string convertor will transform parameters like HA Events, Pooling, etc. The transformed .NET connection string will keep everything except the Provider. [TS-8819|TS-8151|TS-8926] • On an Oracle database you could get an error while creating or deleting folders, stating The object is used by another user. The internal retry mechanism will upon an ObjectInUse reattempt the operation outside of the running transaction. [TS-8870|TS-8877] • Database Access Layers for EventMonitor, TranslationBuilder and TranslationOrganiser are merged. [TS-4721]BackgroundTask • Our plugin system caused memory blocks holding configuration to remain referenced. At some point so much memory is referenced that the next requester of memory receives the dreaded Out-Of-Memory message. Note that the process who eventually logs an Out-Of-Memory message is not always the cause of the memory consumption. [SRQ-4197|TS-10346] • The service lease recovery could fail when having multiple services running with System. InvalidOperationException: Nullable object must have a value. This was caused by the data layer now allowing nullable values. [TS-8935] • When requesting the service BackgroundTask. exe or its isolated child process BackgroundTaskIso. exe to stop, a warning message could show during the ServiceMustClose function reading Default principal object cannot be set twice. [TS-8979|TS-8791] • The BackgroundTask plugin ISHPlugins.cNotification which implements comIEventHandler is extended to support multi-value user fields as email recipients. The internal communication message XML generated for multi-value user fields did a look-up using a direct XPath expression instead of looping over the potential multiple values of the field. [TS-9608|TS-9607|SRQ-3110]Plugins • The function SetMultiStringFieldValue(string name, PluginsSDK.IshLevel level, List<string> value) on PluginContext is now less strict. It used to only accept strings, now it can also be used for the value representation of CardReference (e.g. Admin) or LOV (e.g. en-US). The function SetMultiStringFieldValue(string name, PluginsSDK.IshLevel level, List<string> value, PluginsSDK.IshValueType valueType) on PluginContext can now also accept strings by specifying PluginsSDK.IshValueType. Value. [TS-9487|TS-9518] • Improved logging for Trisoft.InfoShare.Plugins.Host.PluginFactory where our Managed Extensibility Framework (MEF) potentially hides the true error due to a ReflectionTypeLoadException. [TS-9584|TS-9445] • Managed Extensibility Framework (MEF) composition entries were added using XML comments in the .config files of BackgroundTask, BackgroundTaskIso, TranslationBuilder, ISHWS and Trisoft. InfoShare.Web. Enabling those entries will allow to identify MEF issues more easily - similar to WCF/WIF entries we already had. [TS-9583|TS-9570] • Logging was enhanced, in our WebActionLayoutRenderer we made sure that the errors that were thrown during HttpApplication. Init are no longer suppressed. [TS-9769|TS-9745] • All Settings XML configuration files are required to have a version allowing more control on our legacy configuration files in the future. The system will only run if the configuration files have a business code supported version number. If not, you will receive an error in the line of The object "Trisoft.InfoShare.Components.Settings.Status.PublicationOutputStatusConfiguration" contains invalid XML. The version '' differs with the expected version '1.0' which indicates that the system administrator missed some upgrade steps. [TS-9156|TS-9124]SDL Knowledge Center Release Notes 73 2 Release Notes - SDL Knowledge Center• To prevent that the title in the XML content is overwritten with the metadata title during BatchIm- port or Content Import, we added an extra <?ishreplacetitle?> processing instruction check to the out-of-the-box SetTitle plugin in Admin.XMLWriteObjPluginConfig. xml. This does require that your Editor Templates in your repository have the required processing instruction. The altered templates are provided on \Websites\Author\EnterViaUI\System\Editor template. [TS-8996|TS-8793|SRQ-2266] • Capitalization of @conref attributes was not consistent, as it only uppercased the first and last part. Now it also uppercases the middle part. Before, an XML after plugins would contain GUID-XXX#guid-yyy/ ELEMENTID, from now on it will contain GUID-XXX#GUID-YYY/ ELEMENTID [TS-8993|TS-7704|SRQ-1066] • Section GENERATE.LINK.ENDS in Admin.XMLWriteObjPluginConfig. xml is enriched to now also generate @id attributes on <ul> just like on <ol>. [TS-8707|TS-8995] • Section ISHSYSHYPERLINKSTOMETADATA in Admin.XMLWriteObjPluginConfig. xml has enhanced ExtractXpath expressions so <topicref> and <navref> in a <reltable> are handled as hyperlinks. This improves PublishService link validation. [TS-9133|TS-9123] • When submitting a file with electronic document type (EDT) of type EDTXML in an IShTemplate object type and having no IWrite plugins configured, a message A method call is invalid for the object's current state: Object stream is empty after plugin execution. is displayed. [TS-9168|TS-9165]Preview • Restructured the preview files to make it easier to integrate custom extensions like MathML. [TS-7855|SRQ-1138]Security Enhancements • Web applications ISHSTS and ISHCM XSS issues are avoided through .config changes near <httpProtocol>. [TS-9615|TS-9564] • The file SearchViaFindResultNew. asp was adapted to fix XSS issue. [TS-9511|TS-9614] • The web client pages delivered in Classic ASP were reviewed for various security vulnerabilities like cross-site-scripting, proper encoding of HTML, JavaScript and URLs. [TS-8637|TS-9287|TS-9362|TS- 9286|TS-9294|TS-9295|TS-9296|TS-9297|TS-9358|TS-9359|TS-9360|TS-9361|TS-9363] • A cross Site Scripting (XSS) vulnerability was found on the login page of ISHSTS. The problem is fixed in SignIn.cshtml. [TS-9183|TS-9174]PublishService • ChangeTracker comparisons of single files could cause a full publication compare to fail repeatedly. In case of a failing file comparison because of XML well-formed-ness, the PublishService will first mark the topic selected in the highest version of the publication as completely new. In case even that fails then the system will mark the topic as being deleted in the highest version of the publication. So the system will no longer restart the complete publication export. There will be warning entries in EventMonitor. [TS-10323] • The publish (FeedSDLLiveContent. ps1) and synchronize (SynchronizeToLiveContent. ps1) code responsible to upload and prepare material in the Content Delivery stack have been enriched with retries. In their matching .config files you can configure the number of retry attempts (livecontentrequestretries defaults to 1 retry and livecontentprepareretries defaults to no retries) and time between retries (livecontentrequestwaitbetweenretries and livecontentpreparewaitbetweenretries default to a 30 seconds timespan) for regular and prepare calls. End result is that a single failing file upload because of network glitches will not fail the complete EXPORTFORPUBLICATION event handled by the BackgroundTask service. [TS-10242]74 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2• PublishService can handle various event types, not only EXPORTFORPUBLICATION. [TS-9305] • We adapted \ ASP\ XSL\ EventMonitorMenuBar. xml to group some expected new publish event types under the Publish grouping. [TS-9305] • Publish to Content Delivery now normalizes the incoming boolean flag FPUBINCLUDECOMMENTS when publishing. This should allow Display draft comments in publication. [TS-8303|TS-9475] • Publish to Content Delivery for a publication with a branched version number (e.g. 1.4.1) used to result in a Content Delivery identifier like LiveContentPub-v1. 4.1. On 11.0.0 and 11.0.1 more strict character filtering was done to avoid Content Delivery encoding problems, therefore publishing resulted in an identifier without dots like LiveContentPub-v141. We restored the earlier branch version number behavior with dots. To avoid legacy conversion problems where you potentially loose comments, the system will re-use existing Content Delivery publications created with both identifier system by verifying its metadata. The following characters will be filtered out: / (slash), \ (backslash), : (colon), * (star), ? (question mark), ' (single quote), < (less than), > (greater than), | (pipe), & (ampersand), + (plus), # (hash), % (percent) and " (double quote). [TS-9484|TS-9452] • Publish post processing received a fix for better local <xref> handling in file ISHPublUtil. vbs. An <xref> with landing point inside the same file will no longer result in TopicId#AnchorId but only #AchorId. [TS-9282|TS-9478|SRQ-2709] • Publish post processing received a fix in file FeedSDLLiveContent. ps1 to stop potential infinite looping when publishing a single topic to Content Delivery. On most environments Content Delivery is not set up to handle single topic publish requests, which resulted in a configuration error like Remote::GetPublicationMetadata -> gave error: Exception calling "GetMetadata" with "2" argument(s): "The parameter lngRef with value "0" is invalid. Zero is not allowed as valid value." at line 538 position 5. With this fix, such a request should now end with error number -20005 which holds the message Publishing command raised error: Configuration error, missing publication information. Remember that content object publishing is not configured for this output format. [TS-9486|TS-9476] • PublishService with Keep default attributes enabled results in Attribute 'ishlabelxpath' has a value which does not match the fixed value defined in the DTD/Schema. The introduction of Keep default attributes in 10.0.1 allows to only load XML objects once and merges the DTD default attributes such as @class, @ishtype, @ishlabelxpath, etc. Therefore expensive load times can be avoided. This issue is that XML engine - .NET's System.Xml and COM+ MS XML - are handling a multi-line default attribute as different. The DTDs are adjusted to have single-line default attributes. [TS-8917] • PublishService OASIS DITA configuration was corrected to match the IWrite* plugins configuration. The corrections in XMLBackgroundTaskConfiguration. xml will allow PublishService to correctly generate a link report which is essential to decide if a publication becomes a Release Candidate or not. [TS-9112|TS-8897|SRQ-2175] • If you configured many <ishfield> fields for PublishService exporting in ReqMetaDataExportForPublication. xml, you could end up with error The length of the SelectPart is too long (max length = 15000). PublishService relies on API 2.0 calls for its metadata retrieval; this means that it relies on TriDK's big query architecture. A new code path was added which needs to be activated through a registry key TRISOFT_INFOSHARE_PublishService_UseMinimalRequestedMetadata= true that will retrieve the requested metadata fields over API 2.5 which uses a different architecture to retrieve many fields. [SRQ-2581|TS-9137|TS-9130]Attention: The new code path adds @xml: space= "preserve" attributes to every <ishfield> in every .MET file.SDL Knowledge Center Release Notes 75 2 Release Notes - SDL Knowledge CenterImportant: Out-of-the-box the previous code path is active. You need to set the registry key TRISOFT_INFOSHARE_PublishService_UseMinimalRequestedMetadata=truein HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\ InfoShareAuthor...\ to make PublishService use the new code path.• The post processing of a single-topic publish often resulted in ERR ISHPublUtil::RenameOutputFile -> File [C:\InfoShare\Data...\PublishingService\Data\DataExports\GUID-...\1\en\out\GUID-....PDF] not found. The RenameOutputFile function of the post processing will now also check for target file ending with .xml.PDF when publishing types ISHModule, ISHMasterDoc, ISHLibrary or ISHTemplate. [TS-8994|TS-8089] • ISHLanguageLabelResourceFile. xml contains better verified translations. [SRQ-1128|TS-7784] • Publish with Differences with version option fails with reason End tag 'p' does not match the start tag 'li'. [SRQ-2583|TS-9176|TS-9175|TS-9187]Translation Organizer • Removed TranslationBuilder dependency to ServiceUser when using Windows Authentication. So when the ServiceUser is configured, he will be used. When the ServiceUser is not configured, the system will switch to the current WindowsIdentity. As a reminder the StartConsole. bat shows an extra reminder that a Run as might be required. [TS-10482] • TranslationOrganizer service stops with unexpected service termination following error Value cannot be null during TemplateSyncronzationStep fatal error lookup. [TS-10279|TS-10282| SRQ-4049] • The TranslationJob entity relies on a lease concept. If a service like TranslationBuilder or Translation- Organizer becomes unavailable for some reason, the system should recover all expired leases. TranslationJobs in status in translation were not recovered by TranslationBuilder. [TS-10141] • TranslationOrganizer doesn't allow an additional @ishvaluetype as requested metadata resulting in errors such as The entry 'FTRANSLATOR lng' has already been added. A configuration holding two entries like <ishfield name="FTRANSLATOR" level="lng" ishvaluetype="value" /> and <ishfield name="FTRANSLATOR" level="lng" ishvaluetype="element" /> is now allowed. [TS-9878|SRQ-3510] • Translation Organizer - Translated content (EDTXML) retrieved from WorldServer is assumed to be encoded in UTF-16, LittleEndian. In some cases content retrieved from WorldServer is encoded in UTF-16, BigEndian. In this case the code is not able to process it correctly and is not removing the processing instructions, that contains the source language. When submitting the content to Content Manager, it checks the processing instruction and rejects the content, because the language is still indicating that it is the source. This fix contains an adaptation of the TranslationOrganizer Retrieving step to detect the encoding (UTF-16 LittleEndian or UTF-16 BigEndian) and handle it correctly. [TS-9793|TS-9794|SRQ-3355] • The code that parses the language codes in a TranslationJob workflow does not work properly for languages containing an underscore (e.g. zh_CN). As a result, the selected language with underscore (_) was always considered as not being selected, although the user did select it. [TS-10081|TS- 10082|SRQ-3746]76 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Other • Mailer.exe does not write errors to console anymore because of missing NLog.config and assembly files. [TS-10587|SRQ-4308] • Several API calls on a repository holding more than 10 million card IDs, could potentially fail with An unexpected system failure occurred. An entry with the same key already exists.. This issue was introduced in 11.0.1. [TS-9660|TS-9646|TS-9605] • When there are 2 or more Crawlers running on the same database for 2 different SolrLucene collec- tions, reducing (~deleting) a language from an illustration with language applicability will result in ObjectStillInUseException. The ReduceLanguageAction is no longer a fatal action for the Crawler service. [TS-10075|TS-10076|SRQ-3788] • Complete dllhost.exe deadlock occasionally occurs on systems that connect to Oracle databases. In practice it means that the 'Trisoft-InfoShare-Author' COM+ Server Application has to be killed to resolve the deadlock. After analysis the deadlock was traced down to the usage of the wsock32.dll library in the SDL and Oracle code base. In the SDL code base we removed the whole wsock32.dll dependency to avoid a DLL loading deadlock problem. We contacted Oracle support to indicate that their Oracle Client libraries are also affected. [TS-9603|TS-9601|SRQ-3084|Oracle--SR3- 10429198871] • On Microsoft Windows 2012R2 system (then running Internet Information Services (IIS) 8.5) you could run into the error cannot load create-toolbar.xml, internal server error when launching Quality Assistant in Create. Resolved by explicitly calling a <remove fileExtension =".json" /> on the <staticContent> element of \ ASP\ Editors\ Xopus\ SDL-Enrich- Plugin\web.config.[TS-9807|BL-4266] • SolrLucene running in either 32-bit or 64-bit mode runs out of resources (memory, transaction timeout, ...) when the Crawler service passes an XML file of size 5Mb for XML-aware indexing. Out-of- the-box SolrLucene is configured to parse any incoming XML using SolrLucene field XMLCONTENT for XML-aware queries. To improve stability and performance, the Crawler service received an optional setting that will make the service no longer pass XML files over a certain size to the XMLCONTENT field. You will still have metadata searching, also the text of the XML file will be searchable - you will only no longer be able to query using the XML-aware syntax (e.g. -<indexterm>). To enable the skipping of XML having a size greater than 1000000 bytes, activate HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trisoft\Tridk\TridkApp\ InfoShareBuilders\ CrawlerCatalogMaxCharsXMLCONTENT expressed in bytes (e.g. 1000000) and restart the Crawler service(s). [SRQ-2696|TS-9292|TS-9320|TS-9321] • Log files of TrisoftSolrLucene, TranslationOrganizer, SynchronizeToLiveContent and FeedSDLLiveContent contain entries such as 13:16:50.8560 Warn NLog.LoggerImpl.Write ... where NLog.LoggerImpl.Write should actually state the class/method that logged the line. We've upgraded from NLog 2.1 to NLog 3.0. [TS-9157] • SynchronizeToLiveContent and FeedSDLLiveContent logging received extra information like process ID and thread ID to allow correlation/merging of the various log files. [TS-6759|TS-9150| TS-9151] • Status configuration update: the Out of date and Out of date draft status values in the InfoShareStates section of the Admin.XMLStatusConfiguration. xml file have been removed. Publications cannot be assigned an out-of-date status. Obsolete publications, as opposed to released ones, can take the Expired status definition. [TS-8648]SDL Knowledge Center Release Notes 77 2 Release Notes - SDL Knowledge CenterFixed Issues in 12.0.0 DocumentationThe following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.Online Documentation • Revisited the Configuring hosted systems to use a customer's ADFS task. [TS-10119] • autoCompleteBehavior is now explained. [TS-10031|SRQ-3763] • Our Oracle RDBMs and Microsoft SQLServer database jobs that allow the system to work properly are now documented in Content Manager Database Job, Standard Oracle Database Job and Standard SQL Server Database Job. Note that these jobs do not contain regular maintenance like database backups. [TS-10216] • Updated getting started API Samples: Using .SVC Web Service in C# ADFS/ISHSTS' samples for Visual Studio 2013. [TS-8224] • The Settings XML configuration files documented in Repository configuration files received a change log section per configuration file. [TS-9125] • All parameters and verbs of the ExternalPreview endpoint are now documented in the reference section. [TS-8748] • Various small improvements. [TS-8774]Architecture and RequirementsWe now have a cross component description of functionality, architecture, scaling and requirements. The audience in mind was prospects, customers and sales.Known IssuesThe following are known issues in this version. Web/App/DB Servers • The ISHSTS (ThinkTecture IdentityServer) user interface allows selection of certificates by subject name. If however you have multiple certificates in your certificate store with the same subject name but with different thumbprint, the code will simply resolve this to the first hit provided by the certificate store. So in case of a certificate roll over, it could be that you are unlucky and select the expired certificate instead of the fresh certificate. Workaround exists in removing the conflicting certificate from the certificate store. [TS-11686|SRQ-5424] • API read functions like PublicationOutput25. RetrieveMetadata can handle element name retrieval for controlled fields through the @ishvaluetype attribute. The CTPUBLICATIONOUTPUT field FISHPUBLNGCOMBINATION is a special field, that is linked to the DLANGUAGE field on the application level, while most other fields are linked in the database. So you cannot retrieve something like VLANGUAGEEN+VLANGUAGENL+VLANGUAGEFR, you will get the label en+nl+fr and you'll have to parse it yourself if required. [TS-10382] • API write functions like DocumentObj25. SetMetadata will save an incoming entry like EUR, AFR, EUR, ASA, EUR, EUR to a multi-value string field as EUR, AFR, ASA because a unique filter is applied before persisting in the database. [TS-9560] • This warning Trisoft.InfoShare.BackgroundTask.Entities.NewProcessTaskHost. SendForceShutdown Calling ServiceMustClose resulted in exception System. ServiceModel.EndpointNotFoundException is logged if the parent process is asked to stop (either console CTRL-C or service panel). The parent BackgroundTask.exe communicates to all78 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2 its running tasks to stop. In case a running task is handled through a new process, so a child BackgroundTaskIso.exe, it can happen that the BackgroundTaskIso.exe process is already stopped when the disposal of the newproc task happens, resulting in the above warning. [TS-9037] • Light weight Windows Authentication based on ISHSTS is not Network Load Balancing (NLB) ready. We only describe the steps to set up a single FrontEnd Web/App server when using our ISHSTS for Windows Authentication. The reason is that making ISHSTS NLB-friendly requires a big investment to something we do not consider our core business - there are free alternatives like Microsoft Active Directory Federated Services (ADFS) provided as a free role with a Windows Server. • When using a web browser to ISHSTS, therefore using Content Manager as your identity provider with registry entry AuthMaximumPasswordAge enabled, the system can return the message Your password has expired. Please enter a new password or contact your system administrator. The Client Tools rely on the active protocol (WS-Trust) for authentication where we cannot easily distinguish between a regular no access or a no access because your password is expired like we could do for the web client which is based on the passive protocol (WS-Federation). So when a user has a doubt about password expiration, he should use his Web Client where he will also find a Change Password link on the login page. [TS-9465|TS-9433] • We strongly advise to redirect your custom integration to DocumentObj25/ PublicationOutput25 instead of using the deprecated classes DocumentObj20/ Publication20/PublicationOutput20. When throughput is important, the 2.0 code base might throw timeout errors like Trisoft.InfoShare.API25.InfoShareException: Tim- eout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. If you use both the 2.0 and the 2.5 code base, you might also see errors like System.Data.SqlClient.SqlException (0x80131904) : Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel. Win32Exception (0x80004005): The wait operation timed out. The main reason is that the COM+-based 2.0 calls force Serializable on the transaction, potentially making all calls wait. This problem is solved when you switch your custom code to the 2.5 API calls. This is what we did for all of our client tools (Publication Manager, Authoring Bridge, Content Importer, etc). [TS-8739] • Failed transactions block any further update on locked content objects (DocumentObj) or publication outputs (PublicationOutput) requiring manual actions to roll back the transaction. The following characteristics identify the problem: • ORA-01591: lock held by in-doubt distributed transaction trans_id or ORA-02049: time-out: distributed transaction waiting for lock in the log files. • The Microsoft Component Services panel holds entries marked with (only failed to notify) in the Distributed Transaction Coordinator > Local DTC > Transaction List. For example ISAuthor.CPublicationOutput (only failed to notify) or ISAuthor. CDocument (only failed to notify). All environments having this problem have the Oracle password expiration options set for our designated database user - typically isource. Usually near expiration time you'll see the messages appear like ORA-28001: the password has expired or ORA-28002: the password will expire within x days. We advise you to contact your DBA on this, the following statements are provided for convenience only: 1. First check which profile ISOURCE is using: SELECT profile FROM dba_users WHERE username='ISOURCE'; 2. Optional query to show all the limit settings of this profile: SELECT resource_name,limit FROM dba_profiles WHERE profile='DEFAULT'; 3. Change the default profile to set the password lifetime to unlimited: ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;SDL Knowledge Center Release Notes 79 2 Release Notes - SDL Knowledge Center4. After setting the password lifetime you have to reset the password again. You can set it to the same password as it was: ALTER USER isource IDENTIFIED BY isource; 5. We advise you to restart the database and any web/app server. • In case of network stability or connection problems (such as ORA-03113 end-of-file on communication channel) we advise you to setup the Oracle Microsoft Transaction Server (MTS) Recovery Service as documented on http://docs.oracle.com/cd/E11882_01/win.112/e26104/recovery.htm#NTMTS003 . This service resolves in-doubt Microsoft Transaction Server transactions. [TS-7822] • The EventMonitor logging system potentially shows the wrong final status FAILED in the overview when it actually was a SUCCESS. A failure is logged, but then the generic or the PublishService retry mechanism is started, that potentially results in a success. The EventMonitor logging system then CALCULATEs the result in the overview. [TS-8560] • The automated shut down of the Trisoft-InfoShare-AuthorIso failed application sometimes results in Invalid syntax. You can ignore this message. • Renaming languages in settings area will not adapt @xml:lang and language combinations. Avoid changing the label of a language (for example, from en to EN or en-us) when it is in use, because the following problems can occur [TS-6472]: • When changing the label of the language, the existing files in that language are not automatically adapted, and therefore become invalid. This happens because the @xml:lang attribute and the processing-instruction no longer match the label of the language. In this case, you have to resubmit each file. • The publication outputs that have a language combination containing the modified language become invalid and must be recreated. • The Trisoft InfoShare Crawler service is responsible, among other things, for keeping the full-text index up-to-date. The service submits updated content to the full-text index, and it deletes outdated records from the full-text index, as well as from the database. At least one instance of the Trisoft InfoShare Crawler service should always be running to avoid issues with deleted objects. If the Trisoft InfoShare Crawler service is not running or if it lags, removing and then adding again the same language to an illustration with multiple languages can throw the following exception: Violation of PRIMARY KEY constraint 'ISH_CONTENTOBJECT_PK'. Cannot insert duplicate key in object 'dbo.ISH_CONTENTOBJECT'.... This issue may occur when the service has already deleted the language record from the full-text index, but it has not performed the same operation on the corresponding database record yet. [TS-9089] • Remember, some of the content in the full-text index are labels from list of values (e.g. status,...) or referenced objects (e.g. users, EDTs, ...) which are used as metadata on the objects. Whenever the labels of those objects (e.g. users) or list of values (e.g. status,...) are changed, a reindex of the full-text index should be triggered manually, otherwise the full-text index will not find objects using the new label. In order to trigger a full reindex you should stop the Trisoft InfoShare Crawler service, run StartReindex. bat and restart the Trisoft InfoShare Crawler service. Non-Western Language Searches • Solr uses the Boolean OR operator when multiple words are detected in a search. Note also that for non-Western languages, Solr uses language analysis features to break down terms into smaller components, so if you enter a Japanese search for Solr breaks it into two words: and . In this case, the default behavior��匿 is to search for OR . This may not ��return the expected鍑匿 results. �� 鍑匿 • Therefore, when you search in non-Western languages such as Japanese, Solr can be configured to use the Boolean AND operator between words instead of the default OR operator. • To specify the Boolean AND operator in these instances, add <str name="q.op">AND</str> in80 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2 the <lst name="invariants"> part of the requestHandler section in the \ TrisoftSolrLucene\SolrLuceneCatalog\conf\solrconfig.xmlfile. • If this is done, when Solr uses its language analysis features to break down a term into smaller components, the Boolean AND operator is applied instead of the OR operator. However note that this does not affect words entered with a space between them as the search criteria. A whitespace between words still assumes use of the default Boolean OR operator. [TS-6497] Client Tools and XML • When creating a folder you can assign a UserGroup where the current user has no access to. The folder will be created, but any refresh action afterwards will not show you that folder and potentially can trigger an error message such as The object does not exist. [c:"894969 "] [TS-8652] • When the Browser Repository dialog is opened from a third party XML editor, the clipboard keyboard shortcuts (CTRL-C, CTRL-V, ...) cannot be used in the search field of this dialog's Search tab. The Del key cannot be used either in that field [TS-11221|SRQ-4898]. • When conreffing a glossentry which is part of a glossgroup topic, a glossentry is created with an incorrect value in the conref attribute. Publish warns that there is an unresolvable conref during publish because the conref value is incorrect. [TS-4630]Note: glossentry is derived from topic, so the conref value should be the same as when you conref a complete topic. Instead of creating a conref with topicid#topicid/ elementid, it should be topicid#elementid• The @id attribute cannot contain OASIS DITA control characters like slash (/) and hash (#) - even on the <resourceid> element as the parsing engine cannot distinguish it anymore when using the OASIS DITA linking system (e.g. LOGICALID#TOPICID/ ANCHORID). If you use this construct, it could give unexpected results in the Publication Manager tree list views like Baseline, Folders, WhereUsed, etc. [TS-10488|TS-10540|TS-10553|SRQ-4015] • Depending on your content architecture, the feature Dynamic Link Text resolving can have a negative performance impact to show you the accurate values in a preview. A safety mechanism will avoid infinite recursion. [TS-5966|SRQ-1200] • Refresh operations might function incorrectly if the content object in question is created in multiple phases. Typically all content objects are created with logical-version-language levels in one go. Technically it is possible to create each level on its own, which can confuse the refresh operation. The advice is to adapt the routines that perform separate level creation. [SRQ-2432] • You cannot connect with a second user to the same data source if the first user was already connected to the same data source. You can have two accounts, so two usernames, pointing to the same repository. You just cannot be connected at the same time. Switching accounts requires a client tools restart. [TS-8656] • When using the <stylesheet> element in StyleSheets. xml at <download> time, you are actually forcing an XSLT processor to handle the file from the repository. The XSLT processor will always add default attributes - like @class, @domains, @ishlabelxpath, etc - to the resulting XML file. Our typically configured Filters/ Dita11ToDita12. xsl which takes care of automated @navtitle attribute to <navtitle> element conversion immediately removes these unwanted default attributes. This stripping does not affect the @processing-role attribute on the <keydef> element. You can either disable the <stylesheet> or tweak the XSLT file to your needs. [TS-8692] • Although multiple third-party XML editors are supported in this release of Content Manager, use of a single third-party editor is recommended. SDL is not responsible for how the third-party editors handle XML and DITA and the behavior might differ for each XML editor. As a result, if you use more than one, you may find cross-compatibility issues with the way the different editorsSDL Knowledge Center Release Notes 81 2 Release Notes - SDL Knowledge Center handle DITA. If you decide to use multiple third-party XML editors and find cross-compatibility issues with DITA, SDL recommends that you interact with the vendor of the XML editor to resolve the issue. [ TS-4957|TS-5260] • Only 32 bit versions of the XML editors are supported. • Uninstalling the Authoring Bridge for XMetaL causes a problem when you then try to upgrade to the new installation. You must first uninstall XMetaL then you can uninstall Authoring Bridge. Reinstall XMetaL then upgrade or reinstall the Authoring Bridge. [SCTS-380] • Although not supported, when installing Client Tools 10.0.3 on a Server 10.0.0/10.0.1/10.0.2 you might run into a compatibility issue. The reason is that the Trisoft.Utilities.ServiceReferences. dll assembly has been extended with a new class to do WCF http compression in the .NET 3.5 world. The Client Tools MSIs are not always allowed to overwrite the server-side's older version of the assembly. This results in messages in the line of Unable to establish a connection with the web services on or Could not load type 'Trisoft. Utilities.ServiceReferences.WebClients.CompressibleHttpRequestCreator' [TS-7169] • Search > Advanced options; searching on a version is always done on AllVersions [TS-4222] • Only references to DITA topics and DITA maps are supported. References to images and other formats (for example, PDF, DOC) are not properly supported or not supported at all. [TS-5731] • In ServiceReferences there is no check about the ability of a user to enter the application. So the authentication works but Content Manager or Content Delivery might still block authorization by a ProfileMismatchException. [TS-4292] • Client Tools using SSL might crash when using a URL that doesn’t match the certificate. [TS-571] • Client Tools cannot handle Content Manager accounts that contain a slash (/) or backslash (\) because it confuses them while handling other authentication requests coming from Secure Token Services or Proxies that potentially require NTLM/Windows authentication. [TS-8312] • When using a secured proxy, the client tools browser component could popup an extra authentication dialog. [TS-4680] • Avoid opening multiple instances of editors (so there is only one process of the editor running) to prevent possible locking of files in the profile folder of the Gecko renderer component. [TS-4682] • Where Used Report [TS-7037] known issues. When doing a where used on an object in the client tools, be aware that the shown publications are determined by performing a PublicationOutput25.Containing API method. This means: • The PublicationOutput25. Containing first calculates the baselines in which the logical object is present (see Baseline.Containing). These baselines are used to retrieve the publication versions (see PublicationOutput. UsingBaseline). As a consequence, when the baseline is shared between multiple publications, the result can contain publications in which the topic is not used. • Selecting a specific version of a map forces version selection for all referenced topics. Changing the version of a map can give less referenced topics, but those topics could still be in the baseline. This can result in publications shown in the report where the topic is no longer used. • If a library contains @conrefs with illustrations or links to other topics, all referenced objects will be returned as part of the publication even if they are not used. • If a library contains variable definitions with illustrations or links to other topics, all referenced objects will be returned as part of the publication even if they are not used. • Conditional filtering is ignored! • The current list of elements explicitly resulting in resolved link text in the Client Tools preview82 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2 are: <xref>, <link>, <topicref> and their basic @class attribute based specializations. Many other elements like the <mapref>, <topicsetref>, <anchorref>, <topicgroup>, <topicset> elements or <navref> will not be resolved while previewing. [TS-8298] PTC Arbortext Editor • The SDL Knowledge Center menu and the Insert Markup action to insert elements works and will trigger the necessary Authoring Bridge dialogs. All other functionality such as the direct Insert menu items cannot properly be redirected to the RepositoryAdapter and pops-up with Arbortext Editor's file system integration. • Conrefend attribute is not displaying in the Modify attributes window. The conref attribute was removed from the Modify Attributes dialog. Use the menu option, SDL Knowledge Center > Conref > Insert Conref in the editor to insert a conref or a conref range. [TS-5593] • The conref attribute was removed from the Modify Attributes dialog when you have a Content Manager document opened in the Arbortext Editor. Users must use the menu item, SDL Knowledge Center > Conref > Insert Conref, to insert a conref or a conref range in their document. JustSystems XMetaL • When using XMetaL Resource Manager on a DITA Map holding an equal sign (=) in its metadata title field (FTITLE) functionality like opening and saving might return unexpected results and throw messages in the line of 'mapApp' is null or not an object or A Dita Map was not selected or A specialized map was selected. As a workaround, use the full editor view. [TS-10541] • Using the ALT-TAB key combination to another application while doing a checkout/checkin/ keep checked out of an item with (con)keyref blocks XMetaL. The XMetaL Configure Key Space Association dialog pops up when (re)opening the item, but the focus is on the main XMetaL window, which makes it impossible to close the Configure Key Space Association dialog. When trying to close XMetaL, it detects that there is still a script/dialog running and it cannot close. Using Microsoft WindowsTask Manager you can kill the Configure Key Space Association dialog; you can also disable that dialog in XMetaL's Tools > DITA Options on the tab named Update Content: Uncheck the checkbox marked Prompt if the document is not associated with a key space when refreshing references. [TS-5641] • Dynamic Link Text Resolving of <related-links> are sometimes not resolved from the referenced document if no text was given, although DITA Options > Refresh xref/related-links is enabled. This is caused by unwanted whitespace, it can be worked around in the .CTM files by disabling the pretty print options. [TS-9788] • Publishing from within XMetaL is not supported. The following menu items are not fully supported (may not work): • File > Generate Output for DITA Map... • File > Generate Output for DITA Topic... • File > View Output Log... • File > Preview in Browser... • Local Publish with a Topic/task etc. which has an xref inside it does not work. [TS-5182|TS-5184] • The Page Preview view is not supported (may not work). [TS-5526] • Page Preview produces an error null is null or not an object when a xref topic contains unresolved references. [TS-4438] • Do remember that like in SDL LiveContent Architect 2013 when installing the Authoring BridgeSDL Knowledge Center Release Notes 83 2 Release Notes - SDL Knowledge Center for XMetaL on Windows machines you have to have full access to folders C:\Program Files (x86)\Common Files\XMetaL Shared and C:\Program Files (x86)\XMetaL x.y before performing the installation. • XMetaL will show the value of an ishcondition attribute that contains the following special characters ", <, >, & in the Tags On View and Normal View with their corresponding XML predefined entities ", <, >, &. Note that all other characters should not be shown as XML character entities. For example the following ishcondition value: Department='R&D' and version > 3.1.1 will show up as: Department='R&D' and version > 3.1.1. [TS-8004] • Inserting a conref to a multimedia object is not always resolved correctly. Either it shows you the object twice or it shows a blue outlined diamond. [TS-8458|TS-8663] • If the Authoring Bridge is uninstalled, the SDL Knowledge Center menu will remain in the menu bar, with all menu options greyed out. The user must start XMetaL while pressing the CTRL key in order to have XMetaL clean up the menu bar and remove the SDL Knowledge Center menu. [TS-10128] <oXygen/> XML Author/Editor • Multi select insert via Topic Ref isn't working as the XML editor's InputURLChooserCustomizer can only handle one. [TS-9449] • Issues may arise with Find and Replace when used on a DITA map. A common error made when doing a find/replace on map is setting the wrong filter in the Include Files field of the UI. When performing a find/replace on a map, users should change the filter to the asterisk wildcard character, *. The default is *.*. (Only on 15.2) • The Add account window does not disappear after pressing Cancel. This is a known issue when using remote desktop technologies. [TS-5654] • <oXygen/> XML Author/Editor performs a save operation on all your open files when you access an Authoring Bridge menu, which allows you to CheckIn or CheckOut. This issue is caused by a difference in threading paradigm between the JAVA based XML editor and the .NET-based Authoring Bridge SDK components. • <oXygen/> XML Author/Editor is only available on a Microsoft Windows platform because the Authoring Bridge SDK is made of .NET libraries • <oXygen/> XML Author/Editor menu items and buttons do not get disabled when a document is visible in the editor but not checked out. The user can still access the dialogs and perform actions, which can be confusing because the document is locked and cannot be edited. [TS-5140] Content Editor • Inline elements are not pasted into codeblocks, or other space-preserving elements. Only the text, and not the accompanying inline elements are pasted when you are pasting into a codeblock or other space-preserving elements. For example if you were copying a code sample that includes an inline b (bold) element and then tried to paste this, the result is only the text of the code sample will be pasted. We do not paste the bold or other inline elements. • Selecting a range of contiguous conref targets is not supported in Content Editor. [LCDE-385| LCD-2229] • When copying content in the tags on view in Internet Explorer, the text of the tags is copied to the clipboard as well. • Processing instructions for placeholders (xm-replace_text) inserted using the API after loading the document are not recognized as placeholders.84 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Publication Manager • When a conref is made to an image in the same topic, an erroneous message is displayed for circular references: Warning: The object <x> is mentioned within the object itself, creating a circular reference. [TS-3449] • When you change the Review End Date of a publication output in Publication Manager or Web Client after the output was already published, the status is changed to Out of date (working as designed). Note that when any metadata field is changed on the publication output, the status of the publication output is changed to Out of date. This happens because the metadata (in this example, the Review End Date) may have been used in the publication (e.g. on the front page), therefore the published result can now be out of date. [TS-3093] • Find option (CTRL+F) in Publication Manager for the current document no longer has the option to Match whole word. The find on a whole word functionality was dropped; it is not supported by the new browser component (Gecko). [SCTS-469] • After checking in topics, there is a delay before the changes can be found by the search. When using the scope Current Publication it will be asked to check in the topics, but even then changes might not be part of the search results. There is a delay between checking in and the indexing into the full text index. A refresh of the search result pane will resolve the problem after the index is generated for the checked in topics. [TS-8322] • There is no cursor when adding or replying to a comment in the Publication Manager. Typically happens when you switch to another application and then move back to Publication Manager. The issue is caused by a bug in the Gecko renderer component. • Comments pane title in Publication Manager does not resize correctly. For screen resolution settings 1024x768 and lower, the Comments pane display in Publication Manager may have display issues. [SCTS-168] • Inbox gives an error when one of the files in the list has a conref - conrefend pair that don't refer to the same document. The error is: Begin and end id require to be in the same document when a bookmark is given. [TS-2207] Content Importer • The user interface shows a possibility for Default resolution which never gets used because the system always expects a mapping from file extension to Electronic Document Type (EDT) to be configured. Unconfigured file extensions will simply be ignored. [SRQ-3216] • In Content Importer, changing the resolution of a selected image is not available. For setting a new resolution, you need to delete the image and reload it with the new resolution. [TS-7705] Web Client • List Of Values entries holding a single (') or double (") quote could cause unexpected behavior in some locations. In general we suggest to avoid these characters in values for readability. For example a single quote in a status will make the Initial Statuses page return HTTP 500. [TS-10462] • The Translation Job user interface will show duplicate entries in the Added Items section, such as for example two times the same publication version. This is a cosmetic issue, the repository only holds one entry. [TS-10476] • You can create a logical ID with spaces. However, when you try to use a template to create the initial document, this will return errors in the line of The object "JIRA TS 2031" contains invalid XML or Multiple names found in attribute value when only one was expected.The OASIS DITA document types specify the @id attribute as a true identifier, blocking spaces in the identifier. In a future version we will completely forbid usage of spaces in identifiers. [TS-2110] • The sorting result on Inbox items is not correct. Uppercased letters come before lowercasedSDL Knowledge Center Release Notes 85 2 Release Notes - SDL Knowledge Center ones, which is the typically ASCII sorting order based on their numerical (not alpha) representation. [TS-2933] • Actions triggered through the web client don't allow to update baseline entries. A triggered web client will reuse any existing baseline and initiate an auto complete action when required. For example, creating a publication in the web client and trying to get it to status Released will not work because at no point in time the baseline received version entries. [TS-8633] Preview • The image files of type SVGZ are not rendered. You can submit and use them throughout the application. The only exception is that the client tools will render an embedded SVGZ in the preview. Web client preview of SVGZ results in an XML parsing error. The XML parsing error is caused by the mime type. The mime type for both SVGZ is text/xml+svg. The text/xml portion of the mime type enables SDL product components to process the content as XML. However, the SVGZ content is actually a zip archive of SVG content. That is, the format is not XML, but a zip archive of XML text. The zip archive of XML content causes the parsing or loading error. [SCTS- 532|TS-7667] • WMF and TIFF files are not displayed in the preview. They cannot be rendered by any client tool or the web client. Publishing • Using PublishService with options Keep DTD system ID off and Keep fixed attributes off will not work because post processing is not resolving the DTD when loading the XML. This causes exceptions such as loading and converting file: C:\...\PublishingService\Data\DataExports\GUID-...\... \en\workset\...=GUID-...=1=en=.xml ERR ISHPublUtil::ResolveFileNames -> Unable to load file [C:\... \PublishingService\Data\DataExports\GUID-...\...\en\workset\...=GUID-...=1=en=.xml] into a DOM document for converting the link statements. Following error occured: -2146697210 [TS-10431] • All PublishService output formats are delivered as examples. We expect all customers to skin and apply company layout and logos. We package improvements on a best effort basis without guarantees. [SRQ-3139] • The Web Help output format might contain too many XML or image files. For example images could still be present that are part of the super-publication but might no longer be accessible through content object navigation because of conditional filtering. [SRQ-3035|SRQ-3139]Deprecated, Obsolete and RestrictionsThe 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.Important: The list provides a high level summary. The release notes will explain per version what exactly is altered (e.g. API function deprecation, etc).Since Content Manager 2016 (12.0.X) • New environments using the Oracle RDBMs should install Content Manager on Oracle RDBMs 12c. Oracle RDBMs 11g is currently in extended support and only allowed to be used to softly migrate existing environments. The documentation's Content Manager installation instructions no longer include Oracle 11g specific tasks.86 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2• 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 ISHBATCHIMPORT implemented by ISHBatchImport*. CBatchImport is 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 BATCHPERFORMACTION and RELEASETRANSLATIONS implemented by ISAuthor*.CInboxView are deprecated. • Background task implementation of handler DELETETRANSLATIONS is obsolete. • All programmer's interfaces are now fully natively .NET. In 11.0.0 we introduced IWrite* plugins as replacement for IOnDocStore and ICustomerFunction. In 11.0.1 we introduce IBackgroundTaskHandler to replace IEventHandler. This marks the IEventHandler interface as deprecated; and IOnDocStore and ICustomerFunction interfaces are obsolete as they are technically no longer available. • The FSDLLIVECONTENTSKIN field has been made obsolete. It was the database field used for the OutputFormat 'Skin used' property, which has been removed from the OutputFormat properties screen. 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 (32bit) 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 (Still available in the MSI but no longer supported) • <oXygen/> XML Author/Editor 15 (32bit) • 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]. 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 for IOnDocStore and ICustomerFunction. In 11.0.1 we introduce IBackgroundTaskHandler to replace IEventHandler. This marks the IEventHandler interface as deprecated; and IOnDocStore and ICustomerFunction interfaces are obsolete as they are technically no longer available.SDL Knowledge Center Release Notes 87 2 Release Notes - SDL Knowledge Center• Client Tools Offline working 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 FISHSTATUSTYPE field. The option Default Settings > Enable out of date has been removed. • The usage of multiple contexts on either masters or publication versions through the CTCONTEXT card 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 (32bit) • Arbortext Editor 5.3 • Microsoft Internet Explorer 8 • Reusable Objects. Please contact SDL Support to discuss your usage and legacy conversion. [TS-4673]. 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.88 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Since 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).Software compatibility across releasesInformation about third party or client software is packaged, configured and tested for a specific software version release.Version OverviewThe following table — available for informational purposes only — indicates: • The Content Manager client tools versions which should be used against a certain release of the server side components. • The Third Party software which is configured or integrated inside a certain release of the server side components. • The Third Party software such as operating systems, databases, and runtimes which we use to conduct quality assurance testing for the server side components .Attention: Exact versions indicate a version which we did regression testing; these are usually also available for download. Note that other versions may work but are not quality assured. If a problem is encountered we only accept the issue if it is reproducible on the listed versions.Note: Content Manager is qualified on an English version of our supported operating systems only. Other languages of these operational systems are not used for quality check purposes.Restriction: The relation between the Content Manager client tools and the XML editors are not defined in this table. Installation packages are not always available for all XML editor versions.SDL Knowledge Center Release Notes 89 2 Release Notes - SDL Knowledge CenterCAUTION: For the most up-to-date information you should always verify the latest installation documentation. There are other requirements than the ones listed below.Note: The names, trademarks, designs, logos, service marks, intellectual property, etc., of the products shown are exclusive property of their respective owners.Terminology used: • S: is short for Supported which means that the software was used, configured or integrated in the version. • -: means that there is no information available for this combination. Usually because one of them was not around yet during the mentioned era or because it is simply not a supported combination anymore. • D: is short for Deprecated which means the software was used/configured or integrated in the version; but you are strongly advised to not use this combination anymore.Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 SDL Trisoft Publication Manager 9.1.x S - - - - SDL Trisoft Publication Manager 9.3.x - S - - - SDL LiveContent Architect Publication --S-- Manager 10.1.x SDL LiveContent Architect Publication ---S- Manager 11.1.x SDL Knowledge Center Publication Manager ----S 12.0.x SDL Trisoft Authoring Bridge 9.1.x S - - - - SDL Trisoft Authoring Bridge 9.3.x - S - - - SDL LiveContent Architect Authoring Bridge --S-- 10.1.x SDL LiveContent Architect Authoring Bridge ---S- 11.1.x SDL Knowledge Center Authoring Bridge ----S 12.0.x Microsoft Windows XP S S D - - Microsoft Windows Vista S S D - - Microsoft Windows 7 - - S S D Microsoft Windows 8 / 8.1 - - - S S Microsoft Windows 10 - - - - S90 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 PTC Arbortext Editor 5.3 (32bit) support files DOnly DOnly DOnly -- OASIS OASIS OASIS DITA 1.1 DITA 1.1 DITA 1.1 support. support. support. PTC Arbortext Editor 5.4 (32bit) support files S S D D - PTC Arbortext Editor 6.0 (32bit) support files - - S Support S Note D Note added in that 6.0 that 6.0 10.0.1 for doesn't doesn't Arbortext support support Editor 6.0 various various M060. DITA 1.2 DITA 1.2 Note that features features 6.0 like like doesn't keyref or keyref or support conref conref various ranges. ranges. DITA 1.2 features like keyref or conref ranges. PTC Arbortext Editor 6.1 (32bit) support files - - - - - PTC Arbortext Editor 7.0 (32bit) support files - - - - S JustSystems XMetaL 5.5 (32bit) support files D D D - - JustSystems XMetaL 6.0 (32bit) support files S S D - - JustSystems XMetaL 7.0 (32bit) support files - - DSupport - - added in Replaced, 10.0.1 for hence JustSystemsremoved XMetaL in 11.0.0 7.0 - by verified JustSystems on XMetaL version 9.0 7.0.111 JustSystems XMetaL 8.0 (32bit) support files - - SSupport S - Still added in available 10.0.3 for in the MSI JustSystems but no XMetaL longer 8.0 - supported. verified on version 8.0.258SDL Knowledge Center Release Notes 91 2 Release Notes - SDL Knowledge CenterRelease ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 JustSystems XMetaL 9.0 (32bit) support files - - - SSupport D added in 11.0.0 for JustSystems XMetaL 9.0 - verified on version 9.0.45 JustSystems XMetaL 10.0 / 10.0 J(apanese) ----S (32bit) support files JustSystems XMetaL 11.0 (32bit) support - - - - S Support files added in 12.0.1 for JustSystems XMetaL 11.0 - verified on version 11.0.0.083Syncro Soft <oXygen/> XML Author 14 - - SSupport -Replaced, - (32bit) support filesSupport on Windows added in hence platform only 10.0.1 for removed Syncro in 11.0.0 Soft by Syncro <oXygen/>Soft XML <oXygen/> Author 14 XML - verified Author 16 on version 14.1, version 14.2 is also supportedSyncro Soft <oXygen/> XML Author 15.2 ---D- (32bit) support filesSupport on Windows platform only Syncro Soft <oXygen/> XML Author 16.0 ---SD (32bit) support filesSupport on Windows platform only Syncro Soft <oXygen/> XML Author 17.1 ----S (32bit) support filesSupport on Windows platform only Adobe FrameMaker 9.0 support files S Only SOnly D-- OASIS OASIS DITA 1.1 DITA 1.1 Support. Support.92 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 Adobe FrameMaker 10.0 support files - S S D - Adobe FrameMaker 11.0 support files - - - - - Adobe FrameMaker 12.0 support files - - - - - SDL Trisoft Condition Manager 9.1.x S - - - - SDL Trisoft Condition Manager 9.3.x - S - - - SDL LiveContent Architect Condition --S-- Manager 10.1.x SDL LiveContent Architect Condition ---S- Manager 11.1.x SDL Knowledge Center Condition Manager ----S 12.0.x SDL LiveContent Architect DITA2Trisoft --S-- 10.1.x SDL LiveContent Architect DITA2Trisoft ---S- 11.1.x SDL Knowledge Center Content Importer ----S 12.0.x SDL LiveContent Reach 7.0 - - - SVerified - with 11.0.0 SDL LiveContent Reach 7.1 - - - SVerified - with 11.0.1 SDL LiveContent Reach 7.3 - - SVerified SVerified D with with 10.0.4 11.0.2 and and 10.0.5 11.0.3 SDL Knowledge Center Content Delivery 7.4 - - - SA hotfix S may be required in some situations, contact Support in case of issue. SDL Knowledge Center Content Delivery 7.5 - - - S S SDL TMS 2011 SP4 CU2 - - - S D SDL TMS 2011 SP5 CU2 - - - S D SDL TMS 2011 SP6 CU1 - - - - S SDL TMS 11.0.x - - - - SSDL Knowledge Center Release Notes 93 2 Release Notes - SDL Knowledge CenterRelease ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 SDL TMS 11.1.x - - - - S SDL TMS 11.2.x - - - - S SDL WorldServer 10.1 - - S D - SDL WorldServer 10.2 - - S D - SDL WorldServer 10.3 - - S D - SDL WorldServer 10.4.4 - - - S S SDL WorldServer 11.0.x - - - - S SDL Quality Assistant 2.2.0 - - - - SVerified for Content Editor integration.SDL XPP 9.1 - - - - S Microsoft Windows 2003 R2 (32bit) SP3 D - - - - Microsoft Windows 2008 R2 (64bit) S - - - - Microsoft Windows 2008 R2 (64bit) SP1 - S S D - Microsoft Windows 2012 (64bit) - - - - - Microsoft Windows 2012 R2 (64bit) - - - S S Microsoft Windows PowerShell 4.0 (part of ---SS Windows Management Framework 4.0) Microsoft Windows PowerShell 5.0 (part of - - - - -Verified Windows Management Framework 5.0) for 12.0.1; officially version 4.0 is still recommended.Microsoft Active Directory Federated --SSD Services (ADFS) 2.0 Microsoft Active Directory Federated ---SD Services (ADFS) 2.1 Microsoft Active Directory Federated ----S Services (ADFS) 3.0 Oracle RDBMs 9.2.0.2 D - - - - Oracle RDBMs 10.2.0.4 D D D - - Oracle RDBMs 11.2.0.1 - S S - - Oracle RDBMs 11.2.0.4 - - - S D Oracle RDBMs 12.1.0.2 - - - - S94 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 Microsoft SQL Server 2005 SP3 D D - - - Microsoft SQL Server 2005 SP4 - S D - - Microsoft SQL Server 2008 SP1 S S - - - Microsoft SQL Server 2008 SP2 - S - - - Microsoft SQL Server 2008 SP3 - S D - - Microsoft SQL Server 2008 R2 SP2 - - S D - Microsoft SQL Server 2012 SP1 - - - S - Microsoft SQL Server 2012 SP2 SSupport D added in 11.0.1 for Microsoft SQL Server 2012 SP2 Microsoft SQL Server 2012 SP3 - - - - SSupport added in 12.0.1 for Microsoft SQL Server 2012 SP3 Microsoft SQL Server 2014 SP1 - - - - S DITA-OT 1.5.1 S S - - - DITA-OT 1.5.4 - - D - - DITA-OT 1.7.5 - - SSupport S- added in 10.0.2 for DITA-OT 1.7.5 DITA-OT 1.8.5 - - - - S Java Runtime 1.6.0_12 (32bit/64bit) S S DSupport -- added in 10.0.2 for Java Runtime 1.7.0_21 (32bit). Java Runtime 1.7.0_21 (32bit) - - SSupport -- added in 10.0.2 for Java Runtime 1.7.0_21SDL Knowledge Center Release Notes 95 2 Release Notes - SDL Knowledge CenterRelease ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 Java Runtime 1.7.0_21 (64bit) - - - S Support D added in 10.0.2 for Java Runtime 1.7.0_21 (64bit) for TrisoftSolrLucene service. Java Runtime 1.8.0_60 (64bit) - - - - S Java Runtime 1.8.0_91 (64bit) - - - - S Java Runtime 1.8.0_112 (64bit) - - - - S Java Development Kit 1.6.0_18 (32bit/64bit) S S D - - Java Development Kit 1.7.0_21 (64bit) - - SSupport SD added in 10.0.2 for Java Development Kit 1.7.0_21 (64bit) Java Development Kit 1.8.0_60 (64bit) - - - - S Java Development Kit 1.8.0_91 (64bit) - - - - S Java Development Kit 1.8.0_112 (64bit) - - - - S OASIS DITA 1.0 DTD/Catalog configuration DThe DThe DThe DThe DThe public public public public public identifier identifier identifier identifier identifier of OASIS of OASIS of OASIS of OASIS of OASIS DITA has DITA has DITA has DITA has DITA has no no no no no version, version, version, version, version, so when so when so when so when so when we we we we we introduced introduced introduced introduced introduced OASIS OASIS OASIS OASIS OASIS DITA 1.1 DITA 1.1 DITA 1.1 DITA 1.1 DITA 1.1 we had to we had to we had to we had to we had to redirect redirect redirect redirect redirect the the the the the version-lessversion-lessversion-lessversion-lessversion-less identifier identifier identifier identifier identifier to this to this to this to this to this latest latest latest latest latest fully fully fully fully fully backward backward backward backward backward compatiblecompatiblecompatiblecompatiblecompatible version in version in version in version in version in our our our our our catalog catalog catalog catalog catalog files. files. files. files. files.96 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 OASIS DITA 1.1 DTD/Catalog configuration DThe DThe DThe DThe DThe public public public public public identifier identifier identifier identifier identifier of OASIS of OASIS of OASIS of OASIS of OASIS DITA has DITA has DITA has DITA has DITA has no no no no no version, version, version, version, version, so when so when so when so when so when we we we we we introduced introduced introduced introduced introduced OASIS OASIS OASIS OASIS OASIS DITA 1.2 DITA 1.2 DITA 1.2 DITA 1.2 DITA 1.2 we had to we had to we had to we had to we had to redirect redirect redirect redirect redirect the the the the the version-lessversion-lessversion-lessversion-lessversion-less identifier identifier identifier identifier identifier to this to this to this to this to this latest latest latest latest latest fully fully fully fully fully backward backward backward backward backward compatiblecompatiblecompatiblecompatiblecompatible version in version in version in version in version in our our our our our catalog catalog catalog catalog catalog files. files. files. files. files. OASIS DITA 1.2 DTD/Catalog configuration S S S S S OASIS DITA 1.3 DTD/Catalog configuration - - - - - IBM DITA 1.3.2 DTD/Catalog DWe DWe DWe DWe DWe configurationWe strongly advise to change strongly strongly strongly strongly strongly to OASIS DITA. The provided IBM DITA setup advise to advise to advise to advise to advise to is only for backward compatibility. No new change to change to change to change to change to features will be implemented on these DTDs. OASIS OASIS OASIS OASIS OASIS DITA. The DITA. The DITA. The DITA. The DITA. The provided provided provided provided provided IBM DITA IBM DITA IBM DITA IBM DITA IBM DITA setup is setup is setup is setup is setup is only for only for only for only for only for backward backward backward backward backward compatibility.compatibility.compatibility.compatibility.compatibility. No new No new No new No new No new features features features features features will be will be will be will be will be implementedimplementedimplementedimplementedimplemented on these on these on these on these on these DTDs. DTDs. DTDs. DTDs. DTDs. AntennaHouse XSL Formatter 3.3 - - - - - AntennaHouse XSL Formatter 4.1 - - - - - AntennaHouse XSL Formatter 4.2 - - - - - AntennaHouse XSL Formatter 4.3 - - - - - AntennaHouse XSL Formatter 5.1 S - - - -SDL Knowledge Center Release Notes 97 2 Release Notes - SDL Knowledge CenterRelease ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 AntennaHouse XSL Formatter 5.3 - S - - - AntennaHouse XSL Formatter 6.0 - - S - - AntennaHouse XSL Formatter 6.2 - - - S S PTC Arbortext Publishing Engine 5.3 D - - - - Microsoft Internet Explorer 8 S S D - - Microsoft Internet Explorer 9 - S S - - Microsoft Internet Explorer 10 - - S Support SD added in 10.0.1 for Internet Explorer 10. Microsoft Internet Explorer 11 - - - S S Microsoft Edge - - - - - Google Chrome (release update channel) - - SSupport S Verified S Verified added in on on 10.0.4 for version version Google 35 45 Chrome - verified on version 30 Mozilla FireFox (release update channel) - - SSupport S Verified SVerified added in on on 10.0.4 for version version Mozilla 30 41 FireFox - verified on version 25 Acrolinx Plug-in for Oxygen - - SVerified SVerified S Verified on 10.0.5 for for for oXygen oXygen oXygen 14.2 and 17.1 14.2 15.2 using using using Acrolinx Acrolinx Acrolinx 3.4.0 3.3.0 3.3.0 build build build 4179 3325 332598 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Release ... supports ... 9.0.x / 9.2.x / 10.0.x / 11.0.x / 12.0.x / 2011 2011R2 2013 2014 2016 Acrolinx Plug-in for XMetaL - - SVerified SVerified S Verified on 10.0.5 for for for XMetaL 8 XMetaL XMetaL 8 and 8J 10 using and 8J using Acrolinx using Acrolinx 4.2.0 Acrolinx 3.2.0 build 3.2.0 build 882 1153 build 882 Verified for XMetaL 11 using Acrolinx 4.7.0 build 5 SmartLogic Semantic Enhancement Server - - - - SVerified 3.7.3 for IMetadata- Binding integration.Content Manager API compatibility across releasesOverview about which web service methods are available, supported or deprecated on a specific Content Manager version.Version OverviewTerminology used: • S: is short for Supported which means that the method is fully supported. • D: is short for Deprecated which means that there is a newer version of this method and you are strongly advised to not use this combination anymore because the method can be removed in one of the next versions. • I: is short for Internal which means that the method is not available on web services and can still change in the next versions. • -: means that the method was not yet available or has been removed since.Note: Starting from ISH 10.0.x we introduced web services via WCF making the ASMX web services deprecated!SDL Knowledge Center Release Notes 99 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API.Application.ChangePassword - - - API25.User.ChangePassword Only available in ASMX web services API.Application. D D D API25Application.GetApplicationName GetApplicationName Only available in ASMX web services API.Application. D D D API20.Application.GetCurrentUserName GetCurrentUserName Only available in ASMX web services API.Application. D D D API20.Application.GetReleasedStates GetReleasedStates API.Application.GetVersion S S S API25.Application.GetVersion API.Application.Login Only D D D API25.Application.Login available in ASMX web services API20.Application. - - - API25.User.ChangePassword ChangePassword Only available in ASMX web services API20.Application. D D D API25.Application.GetApplicationName GetApplicationName API20.Application. D D D API25.User.GetMyMetadata GetCurrentUserName API20.Application. SSS GetReleasedStates API20.Application.GetResource S S S API20.Application.GetVersion S S S API25.Application.GetVersion API20.Application.Login Only D D D API25.Application.Login available in ASMX web services API25.Application.Authenticate DDD Only available in ASMX web services API25.Application.Authenticate2 III Only available in WCF web services API25Application. SSS GetApplicationName Only available in ASMX web services API25Application.GetUserRef I I I API25.Application.GetVersion S S S API25.Application.Login Only SSS available in ASMX web services API25.Baseline.CanBeFrozen S S S100 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.Baseline.CleanUp - S S API25.Baseline. -SS CompleteBaselineByCandidateAndModeAPI25.Baseline. S D D API25.Baseline. CompleteBaselineByMode CompleteBaselineByCandidateAndMode API25.Baseline. -SS CompleteReportByCandidateAndModeAPI25.Baseline. S D D API25.Baseline. CompleteReportByMode CompleteReportByCandidateAndMode API25.Baseline.Containing S S S API25.Baseline.Create S S S API25.Baseline.Copy I S S API25.Baseline.Delete S S S API25.Baseline.ExpandBaseline S S S API25.Baseline.ExpandReport S S S API25.Baseline. SSS ExtendReportByBaseline API25.Baseline. SSS ExtendReportByCandidate API25.Baseline.Freeze S S S API25.Baseline.GetBaseline S S S API25.Baseline.GetBaselineId S S S API25.Baseline.GetBaselineName S S S API25.Baseline.GetList S S S API25.Baseline.GetMetadata S S S API25.Baseline.GetReport S S S API25.Baseline.Rename D D D API25.Baseline.Update API25.Baseline.RetrieveMetadata - S S API25.Baseline.SetMetadata S S S API25.Baseline.Update S S S API.ConditionManagement. SSS CompareConditionCategories API.ConditionManagement. SSS CompareConditionListsSDL Knowledge Center Release Notes 101 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API.ConditionManagement. SSS GetConditionCategories API.ConditionManagement. SSS GetConditionMasterSet API.ConditionManagement. SSS GetConditionSynchronisation API.ConditionManagement. D D D API25.DocumentObj. SearchInDocuments ContainingCondition API.ConditionManagement. SSS UpdateConditionCategories API.ConditionManagement. SSS UpdateConditionMasterSet API20.DocumentObj. S D D API25.Folder.AddShortCuts AddShortCut API20.DocumentObj.CheckIn S D D API25.DocumentObj.CheckIn API20.DocumentObj.CheckOut S D D API25.DocumentObj.CheckOut API20.DocumentObj.Create S D D API25.DocumentObj.Create API20.DocumentObj. S D D API25.DocumentObj.TryGetMetadata CreateOrUpdate API20.DocumentObj.Delete S D D API25.DocumentObj.Delete API20.DocumentObj. SDD EvaluateDocument API20.DocumentObj.Find S D D API25.DocumentObj.Find API20.DocumentObj.GetDocObj S D D API20.DocumentObj. S D D API25.Settings.GetPossibleTargetStatuses GetInitialStates API20.DocumentObj. D D D API25.DocumentObj.GetMetadata GetMetaData API20.DocumentObj. S D D API25.DocumentObj. GetPossibleTransitionStates GetPossibleTargetStatuses API20.DocumentObj.Move S D D API25.Folder.MoveObjects API20.DocumentObj. S D D API25.Folder.RemoveShortCuts RemoveShortCut API20.DocumentObj. D D D API25.DocumentObj. RetrieveLatestVersionsInfo RetrieveLanguageMetadata API20.DocumentObj. D D D API25.DocumentObj.RetrieveMetadata RetrieveMetaData API20.DocumentObj. S D D API25.DocumentObj.RetrieveObjects RetrieveObjects102 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API20.DocumentObj. S D D API25.DocumentObj. RetrievebyIshLngRef RetrieveObjectsByIshLngRefs API20.DocumentObj. S D D API25.DocumentObj.SetMetadata SetMetaData API20.DocumentObj.StartReuse S - - API20.DocumentObj. S D - API25.TranslationManagement. StartTranslationMgmt CreateTranslationFromVersion API20.DocumentObj. I-- TerminologyUpdate API20.DocumentObj. S D D API25.DocumentObj.UndoCheckOut UndoCheckOut API20.DocumentObj.Update S D D API25.DocumentObj.Update API25.DocumentObj.CheckIn - S S API25.DocumentObj. -SS CheckInByIshLngRef API25.DocumentObj.CheckOut - S S API25.DocumentObj. -SS CheckOutByIshLngRef API25.DocumentObj. SSS ContainingCondition API25.DocumentObj. SSS ContainingLogicalId API25.DocumentObj. SSS ContainingVariable API25.DocumentObj.Create - S S API25.DocumentObj.Delete - S S API25.DocumentObj. -SS DeleteByIshLngRef API25.DocumentObj.Find S S S API25.DocumentObj. SSS FolderLocation API25.DocumentObj. SSS FolderLocations API25.DocumentObj.GetChildren S S S API25.DocumentObj. SSS GetDataObjectInfoByIshLngRef API25.DocumentObj. SSS GetMetadataSDL Knowledge Center Release Notes 103 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.DocumentObj. SSS GetMetadataByIshLngRef API25.DocumentObj.GetObject - S S API25.DocumentObj.GetParents D D D API25.DocumentObj.ContainingLogicalId API25.DocumentObj. DDD GetParentsByIshLngRef API25.DocumentObj. SSS GetPossibleTargetStatuses API25.DocumentObj. SSS GetPos- sibleTargetStatusesByIshLngRef API25.DocumentObj. SSS RetrieveDataObjectInfoByIshLngRefsAPI25.DocumentObj. SSS RetrieveLanguageMetadata API25.DocumentObj. SSS RetrieveMetadata API25.DocumentObj. SSS RetrieveMetadataByIshLngRefs API25.DocumentObj. -II RetrieveMetadataByIshVersionRefsAPI25.DocumentObj. SSS RetrieveObjects API25.DocumentObj. SSS RetrieveObjectsByIshLngRefs API25.DocumentObj. SSS RetrieveObjectsByRevisionIds API25.DocumentObj. SII RetrieveRevisionInfoByIshLngRefsAPI25.DocumentObj. SSS RetrieveVersionMetadata API25.DocumentObj. -SS SetMetadata API25.DocumentObj. -SS SetMetadataByIshLngRef API25.DocumentObj. -SS SetMetadataByIshLngRefs API25.DocumentObj. -SS TryGetMetadata104 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.DocumentObj. -SS UndoCheckOut API25.DocumentObj. -SS UndoCheckOutByIshLngRef API25.DocumentObj.Update - S S API25.DocumentObj. -SS UpdateByIshLngRef API25.EDT.Create - - S API25.EDT.Delete - - S API25.EDT.Find - - S API25.EDT.GetList S S D API25.EDT.Find API25.EDT.GetMetadata - - S API25.EDT.RetrieveMetadata - - S API25.EDT.Update - - S API25.EventMonitor. SSS AddEventDetail API25.EventMonitor. SSS AddEventDetailWithProgress API25.EventMonitor. SSS DeleteByProgressId API25.EventMonitor.EndEvent S S S API25.EventMonitor. SSS GetEventDetail API25.EventMonitor. SSS GetNextEventDetailDataChunk API25.EventMonitor. SSS GetProgressId API25.EventMonitor. SSS RetrieveEventOverview API25.EventMonitor. --I RetrieveEventOverviewByProgressIdsAPI25.EventMonitor. SSS RetrieveEventsByParentProgressIdsAPI25.EventMonitor. SSS RetrieveEventsByProgressIds API25.EventMonitor.StartEvent S S S API25.Folder.AddShortCuts - S SSDL Knowledge Center Release Notes 105 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.Folder.Create S S S API25.Folder.CreateQueryFolder S S S API25.Folder. SSS CreateReferenceFolder API25.Folder.Delete S S S API25.Folder. Exists I I I API25.Folder.FolderLocation S S S API25.Folder.GetContents S S S API25.Folder.GetMetadata S S S API25.Folder. SSS GetMetadataByIshFolderRef API25.Folder.GetSubFolders S S S API25.Folder. SSS GetSubFoldersByIshFolderRef API25.Folder.Move S S S API25.Folder.MoveObjects - S S API25.Folder.RemoveShortCuts - S S API25.Folder.Rename S S S API25.Folder. SSS RetrieveMetadataByIshFolderRefsAPI25.Folder.Update S S S API25.Folder.UpdateQueryFolder S S S API25.Folder. SSS UpdateReferenceFolder API25.ListOfValues.CreateValue S D D API25.ListOfValues.CreateValue2 API25.ListOfValues.CreateValue2 - S S API25.ListOfValues.DeleteValue S S S API25.ListOfValues.RetrieveLists S S S API25.ListOfValues. SSS RetrieveValues API25.ListOfValues.UpdateValue S S S API20.MetaDataAssist.GetLOV D D D API25.ListOfValues.RetrieveLists API20.MetaDataAssist. D D D API25.ListOfValues.RetrieveValues GetLOVValues106 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API20.MetaDataAssist. D D D API25.UserGroup.Find GetUserGroups API20.MetaDataAssist.GetUsers D D D API25.User.Find API25.MetadataBinding. --S ResolveIds API25.MetadataBinding. --S RetrieveTags API25.MetadataBinding. --S RetrieveTagStructure API25.MetadataBinding.Validate - - I API20.OutputFormat.GetList D D D API25.OutputFormat.Find API20.OutputFormat. D D D API25.OutputFormat.GetMetadata GetMetaData API25.OutputFormat.Create S S S API25.OutputFormat.Delete S S S API25.OutputFormat.Find S S S API25.OutputFormat.GetList D D D API25.OutputFormat. SSS GetMetadata API25.OutputFormat. SSS GetOutputFormatId API25.OutputFormat. SSS GetOutputFormatName API25.OutputFormat.Rename - - - API25.OutputFormat.Update API25.OutputFormat. SSS RetrieveMetadata API25.OutputFormat.Update S S S API.PublicationContext. D-- DeleteContext API.PublicationContext. D-- EnrichPublContexts API.PublicationContext. D-- GetConditionListForMaster API.PublicationContext. D-- GetConditionListForPublication API.PublicationContext. D-- GetContextListForPublication API.PublicationContext. D-- GetPublContextSDL Knowledge Center Release Notes 107 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API.PublicationContext. D-- GetPublContextList API.PublicationContext. D-- SaveForPublication API20.Publication.Create S D D API25.PublicationOutput.Create API20.Publication.Copy S D D API25.Baseline.Copy followed by API25.PublicationOutput.Create with the newly created baseline. API20.Publication.Delete S D D API25.PublicationOutput.Delete API20.Publication.Find D D D API25.PublicationOutput.Find API20.Publication.GetMetadata D D D API25.PublicationOutput.GetMetadata API20.Publication. D D D API25.PublicationOutput. RetrieveMetadata RetrieveMetadata API20.Publication.SetMetaData S D D API25.PublicationOutput.SetMetadata API20.PublicationOutput. S D D API25.PublicationOutput.SetMetadata CancelPublish with VPUBSTATUSPUBLISHINGCANCELLED API20.PublicationOutput. S D D API25.PublicationOutput. CancelPublishByIshLngRef SetMetadataByIshLngRef with VPUBSTATUSPUBLISHINGCANCELLED API20.PublicationOutput.Create S D D API25.PublicationOutput.Create API20.PublicationOutput.Delete S D D API25.PublicationOutput.Delete API20.PublicationOutput. S D D API25.PublicationOutput. DeleteByIshLngRef DeleteByIshLngRef API20.PublicationOutput.Find D D D API25.PublicationOutput.Find API20.PublicationOutput. D D D API25.PublicationOutput. GetDataObjectInfoByIshLngRef GetDataObjectInfoByIshLngRef API20.PublicationOutput. D D D API25.PublicationOutput.GetMetadata GetMetadata API20.PublicationOutput. D D D API25.PublicationOutput. GetNextDataObjectChunkByIshLngRef GetNextDataObjectChunkByIshLngRefAPI20.PublicationOutput. SSS GetReport API20.PublicationOutput. SSS GetReportByIshLngRef API20.PublicationOutput.Publish S D D API25.PublicationOutput.SetMetadata with VPUBSTATUSPUBLISHPENDING API20.PublicationOutput. S D D API25.PublicationOutput. PublishByIshLngRef SetMetadataByIshLngRef with VPUBSTATUSPUBLISHPENDING108 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API20.PublicationOutput.Release D D D API25.PublicationOutput.Release API20.PublicationOutput. D D D API25.PublicationOutput. ReleaseByIshLngRef ReleaseByIshLngRef API20.PublicationOutput. D D D API25.PublicationOutput. RetrieveMetadata RetrieveMetadata API20.PublicationOutput. D D D API25.PublicationOutput. RetrieveMetadataByIshLngRef RetrieveMetadataByIshLngRefs API20.PublicationOutput. S D D API25.PublicationOutput.SetMetadata SetMetadata API20.PublicationOutput. S D D API25.PublicationOutput. SetMetaDataByIshLngRef SetMetadataByIshLngRef API20.PublicationOutput. III SetReport API20.PublicationOutput. III SetReportByIshLngRef API25.PublicationOutput. SSS Containing API25.PublicationOutput.Create - S S API25.PublicationOutput.Delete - S S API25.PublicationOutput. -SS DeleteByIshLngRef API25.PublicationOutput.Find S S S API25.PublicationOutput. SSS FolderLocation API25.PublicationOutput. SSS FolderLocations API25.PublicationOutput. III GetDataObjectInfoByIshLngRef API25.PublicationOutput. SSS GetMetadata API25.PublicationOutput. SSS GetMetadataByIshLngRef API25.PublicationOutput. SSS GetNextDataObjectChunkByIshLngRefAPI25.PublicationOutput. III GetPossibleTargetStatuses API25.PublicationOutput. III GetPos- sibleTargetStatusesByIshLngRefSDL Knowledge Center Release Notes 109 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.PublicationOutput.Release S D D API25.Baseline.Freeze followed by a API25.PublicationOutput.SetMetadata VPUBSTATUSRELEASED API25.PublicationOutput. S D D API25.Baseline.Freeze followed by a ReleaseByIshLngRef API25.PublicationOutput.SetMetadata VPUBSTATUSRELEASED API25.PublicationOutput. SSS RetrieveMetadata API25.PublicationOutput. SSS RetrieveMetadataByIshLngRefs API25.PublicationOutput. -SS RetrieveMetadataByIshVersionRefsAPI25.PublicationOutput. SSS RetrieveVersionMetadata API25.PublicationOutput. -SS SetMetadata API25.PublicationOutput. -SS SetMetadataByIshLngRef API25.PublicationOutput. -SS SetMetadataByIshLngRefs API25.PublicationOutput. III SetDataObjectByIshLngRef API25.PublicationOutput. -SS TryGetMetadata API25.PublicationOutput. SSS UsingBaseline API20.Reports. D D D API25.DocumentObj.ContainingLogicalId GetReferencedByDocObj API20.Reports. SSS GetReferencedDocObj API20.Reports. SSS GetReferencesByIshLngRef API25.Search.PerformSearch S S S API25.Search. -SS PerformSearchInPublication API20.Settings. D D D API25.Settings.GetMetadata using the GetSystemLanguage field FMASTERLNG API20.Settings. D D D API25.Settings.GetMetadata using the GetSystemResolution field FISHSYSTEMRESOLUTION API25.Settings.GetMetadata S S S110 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Method 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.Settings.GetTimeZone S S S API25.Settings. SSS GetPossibleTargetStatuses API25.Settings.SetMetaData3 S S S API25.TranslationJob. SSS CreateExternalTranslationJobs API25.TranslationJob. SSS CreateTranslationJob API25.TranslationJob. SSS CreateTranslationJobItems API25.TranslationJob.Delete S S S API25.TranslationJob. SSS DeleteExternalTranslationJobs API25.TranslationJob. SSS DeleteTranslationJobItems API25.TranslationJob.Find S S S API25.TranslationJob. SSS GetMetadata API25.TranslationJob. SSS GetPossibleTargetStatuses API25.TranslationJob. SSS GetTranslationJob API25.TranslationJob. SSS RetrieveExternalTranslationJobs API25.TranslationJob. SSS RetrieveMetadata API25.TranslationJob. SSS RetrieveTranslationJobItems API25.TranslationJob. SSS SetMetadata3 API25.TranslationJob. SSS UpdateTranslationJob3 API25.TranslationJob. SSS UpdateTranslationJobItems API25.TranslationManagement. --I CreateTranslationFromVersion API25.TranslationTemplate. SSS Create API25.TranslationTemplate. SSS DeleteSDL Knowledge Center Release Notes 111 2 Release Notes - SDL Knowledge CenterMethod 10.0.x 11.0.x 12.0.x Replaced by... / 2013 / 2014 / 2016 API25.TranslationTemplate. -SS DeleteByTypeAndAlias API25.TranslationTemplate. SSS Retrieve API25.User.ChangePassword S S S API25.User.Create S S S API25.User.Delete S S S API25.User.Find S S S API25.User.GetMetadata S S S API25.User. SSS GetMetadataByIshUserRef API25.User.GetMyMetadata S S S API25.User.IsInRole I I I API25.User.RetrieveMetadata S S S API25.User. SSS RetrieveMetadataByIshUserRefs API25.User.Update S S S API25.UserGroup.Create S S S API25.UserGroup.Delete S S S API25.UserGroup.Find S S S API25.UserGroup.GetMetadata S S S API25.UserGroup. SSS RetrieveMetadata API25.UserGroup.Update S S S API25.UserRole.Create S S S API25.UserRole.Delete S S S API25.UserRole.Find S S S API25.UserRole.GetMetadata S S S API25.UserRole. SSS RetrieveMetadata API25.UserRole.Update S S S API20.WorkFlow. SSS GetInboxContent API20.WorkFlow.GetInboxes S S S API20.WorkFlow.PerformAction S D D112 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2What's new in Content DeliveryFor this release, Content Delivery has these new features that support SDL Knowledge Center functionality.New and changedOverview of new and changed features and functionality in Content Delivery.New and changed in version 7.5.0The 7.5.0 release of Content Delivery benefits from feature improvements as well as several performance improvements.SynchronizationThe synchronization process has been improved in a number of ways.GraphsSynchronization now relies on pre-defined graphs for updating all publications after a change. Graphs is a simplified representation of the links and relations between objects. Whenever a specific topic needs to be published for synchronization, simple queries to graphs allow for quick retrieval of all the objects referenced by this topic. This replaces the extensive time-consuming interactions with Content Manager that were used before.Graphs are built during publication.Common use of publication processThe publication process has been re-written in order to better interact with synchronization. Synchroni- zation now directly utilizes publication process steps.One single call to Content ManagerNow synchronization immediately updates the active publication, and proceeds to an update of all the other publications using the modified object only afterwards, asynchronously. This means that only one immediate call to Content Manager is needed, rather than the list of calls (one for every related publication) that were made before.GroupsCustomers using commercial certificate providers can now use a default group for user access to Content Delivery. Now, a connected user who is not specifically identified in the group list LiveContentGroups. xml are included in a Visitors group (this default name can be changed) and no longer need a previous addition in the list.SDL Knowledge Center Release Notes 113 2 Release Notes - SDL Knowledge CenterCachingCaching is a key feature for performance improvement. Server side caching has been developed in two directions for this version: • Caching the list of publications. This speeds up the loading of the main page. • Pre-caching. A publication's table of content is automatically cached when a publication is published, and all tables of content are cached when the web application server is restarted. Therefore the very first user access to the content is already speeded up. These aspects of caching can be configured.Publication processThe prepare step of the publication process has received a more detailed logging, so it can better demonstrate activity during the very long preparation of large publications (tens of thousands of topics). Content Delivery now strictly follows XML specifications issued by W3. For example, special characters (&, ", ', <, >) now need to be escaped or a 1303: failed to parse XML error will be returned.DistributionA timeout can be set for closing inactive distribution sockets, with a default value of 1 minute: distribution.timeout.SearchThe search behavior has changed: now <draft-comment> content is left out of search results by default. If you want them back in, you need to configure it in search_build_xconf. xsl.Newly supported softwareContent Delivery now supports: • Red Hat Linux 7.2 • Java Runtime 1.8.0_112 (64-bit) • Java Development Kit 1.8.0_112 (64-bit)New and changed in version 7.4.0The 7.4.0 release of Content Delivery benefits from several significant performance improvements, in addition to the changes related to the rebranding.114 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Performance: Publication speedThe publishing performance has significantly improved. The reduction in publication time allows for more frequent publishing operations.Performance: Publication sizeContent Delivery now supports the publishing and republishing of publications containing more than 60,000 objects.Performance: Navigation speedContent Delivery now uses a cache for the Table of Content (TOC). The publication opens faster on web browsers and navigating inside the publication is faster as well.Other improvements • Several changes improved global performance and stability • Better indexing of content improves the search functionality.Newly supported Java and Apache Tomcat versionsContent Delivery now supports: • RedHat Linux 6.7 • RedHat Linux 7.1 Fixed issuesAn overview of bug fixes and issues that were addressed and solved in Content Delivery product releases.Fixed issues in version 7.5.0Issues have been corrected in Content Delivery • The URL redirection leading to a white screen has been fixed. It was caused by a change in later versions of eXist database [LCD-5511|SRQ-3712] • The bug preventing access to topics from Content Delivery after a successful publish of a high number of publications has been fixed [LCD-5943]. • The loss of verbose output when using loadbd <options> loadpub in Content Delivery 7.3.0 has been corrected [LCD-6029|SRQ-4112]. • The bug preventing the -Dlc.db switch of the loaddb BACKUP command from performing as expected in latest versions has been fixed. Now loaddb BACKUP -Dlc.db backs up a specific file again (instead of backing up the whole DB like if the switch was not there) [LCD-5587; LCD-6648| SRQ-3828; SRQ-4862]. • In Content Delivery versions 7.1 to 7.4, using loaddb.bat BACKUP -Dlc.file=file.zip resulted in the creation of a file.zip folder containing zip files, instead of the creation of a simple file.zip file. This has been fixed [LCD-5898].SDL Knowledge Center Release Notes 115 2 Release Notes - SDL Knowledge Center• Content Delivery no longer returns an error when clicking on a publication name in the breadcrumb path [LCD-5806]. • In Content Delivery versions 7.1 to 7.4, some topics containing links and conrefs were displayed with 2 copies of the link. This has been fixed [LCD-5895]. • The performance drop when table content is fetched from the cache has been removed [LCD-6106]. • PDF titles are no longer replaced by GUIDs in search results [LCD-6104|SRQ-4180]. • Distribution timeouts have been adapted in order to avoid the distribution fail No buffer space available (maximum connections reached?): connect [LCD-6310|SRQ-4593]. • The cause of "500" internal server errors has been fixed: Permission to modify permissions is denied for user 'admin' [LCD-6250|SRQ-4026; SRQ-4629]. • The bug preventing table of content to load while using the development workbench, or while trying to view the cache page, or while the table of content loads in the cache whenever a custom skin is used (in place of the out-of-the-box skins), has been fixed [LCD-6327|SRQ-4576]. • The bug that caused the display of NoteColonSymbol instead of Note: for the DITA note elements has been fixed [LCD-6350|SRQ-4608]. • The bug causing he display of UNDEFINED instead of the welcome page of a publication in Content Delivery has been fixed [LCD-6407|SRQ-4600]. • The name of content elements, such as Figure, are now translated again as the rest of the content [LCD-6269|SRQ-4586; SRQ-4771]. • The skin subscription_check. xql file inherited from early versions no longer blocks the table of content load [LCD-6439|SRQ-4742]. • Content Delivery now allows Publication Manager to display comments made to publications that are not published yet [LCD-6426|SRQ-4234]. • Empty DITA element <xref/> with scope=external is no longer ignored for the HTML rendering [LCD-6575|SRQ-4815]. • PDF titles are again correctly used when referenced in a table of content: the title shows instead of the GUID [LCD-6650|SRQ-4821]. • Publication no longer fails when maps have references (conrefs or variables) or when the publication ID contains spaces [LCD-6795|SRQ-4985]. • Corrected the performance drop in table of content navigation in the Collaborative Review environment [LCD-6832|SRQ-5029]. • The access to Content Delivery through default groups is made available to 7.4 [LCD-4832|SRQ- 2593]. • The bug that forced to manually overwrite resource files when creating a new skin has been fixed [LCD-6476|SRQ-4591]. • The navigation pane (left-hand side) is back to its normal behavior of scrolling to the selected topic when the user jumps from one topic to the other in the content pane [LCD-6911|SRQ-4997]. • loaddb loadpub and loaddb loadpac no longer fail to load a package with a publication [LCD-6727|SRQ-4891]. • The bug that made Content Delivery fail to resolve reference links, displaying them with GUID information instead of the title of the topic, has been fixed [LCD-6910|SRQ-4995]. • Content Delivery no longer loads the complete list of publications when displaying the main page. The publications not present on that page don't need to be loaded at this point [LCD-6411]. • Reducing the maximum number of IDs passed in individual queries has solved the dramatic drop in116 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2Table of content load performance [LCD-6887|SRQ-5039]. • In some circumstances the title of topics that were referenced in other topics was not resolved correctly. This has been fixed [LCD-7033]. • It is no longer possible to some library topics to appear in the site map or in search results [LCD-7047| SRQ-5047]. • URLs returning binary data no longer produce parsing errors when attempting to load the table of content [LCD-7226|SRQ-5233]. • The bug that prevented image resizing for guest readers (not logged in) have been fixed [LCD-7231| SRQ-5350]. • Using context URLs without a slash at the end no longer causes errors on Internet Explorer and Chrome [LCD-7239|SRQ-5167]. • The children topicrefs no longer appear in the output's table of content when the processing- role attribute of a frontmatter is set to the resource-only value [TS-5388|SRQ-4687]. • The bug causing CRON related interruptions during the distribution of content from a distribution server to content delivery servers, has been fixed [LCD-7143|SRQ-5115].Fixed issues in version 7.4.0A few issues have been corrected in Content Delivery • The links to objects with "." (dot) in their GUID are now fully supported. • Special characters such as "]" or "[" are now supported. • The HTML generation when VARREF or CONREF are present in the topic title, have been corrected. • Loads are properly applied after logging in, when the SSO is configured. • Stopping Tomcat during specific operations no longer corrupts the database. • Group updates are now possible when using Content Delivery with ISHSTS. • The server is no longer unresponsive during synchronisation when a publication has just been deleted. • Place holders are now aligned out-of-the-box between Content Delivery and Content Manager. • The loaddb command no longer leaves temporary files behind. Known IssuesAn overview of the known issues in Content Delivery 2016 SP4 with workaround solutions, where available.Searching for some code terms (for example, period-delimited terms such as config.name) does not find a match.In Manage Publications, when validating a publication, running Delete Unused Resources sometimes fails to delete all resources in the list. Re-running Delete Unused Resources deletes the remaining unused resources.When editing a topic from Content Delivery, the topic is refreshed with new information almost immediately. However, the cid attribute values on content added during the edit session will not be present in the refreshed topic. When the topic is synchronized between Content Manager and ContentSDL Knowledge Center Release Notes 117 2 Release Notes - SDL Knowledge CenterDelivery, the cid attribute values become fully available. This problem may limit targeted commenting on new content, until synchronization completes.Restriction: Google Chrome only • Google Chrome displays XML as HTML, which is what you see when you click View XML in Content Delivery. • To display XML source markup correctly, in Google Chrome click Tools > Extensions, and then add the XML Tree and the XV — XML Viewer extensions.When entering a phrase in the type-in filter field, the Language column is ignored.Restriction: iPad devices only • It is not possible to adjust the size of the Topic and Comments panes. • It is not possible to scroll through a PDF file.Content Delivery does not accept slashes in publications' title (\ or /). Using them results in a server error: unable to complete request error.Deprecated, Obsolete and RestrictionsThe following items are deprecated, obsolete or restricted in Content Delivery.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.Important: The list provides a high level summary. The release notes will explain per version what exactly is altered (e.g. API function deprecation, etc).Since Content Delivery 7.5.X The support for the following software components is obsolete in this release: • Apache Tomcat 7 • Java 7 Since Content Delivery 7.4.X The support for the following software components is marked as deprecated in this release: • Apache Tomcat 7 The support for the following software components is obsolete in this release: • Java 7 as support ended April 2015118 SDL Knowledge Center Release Notes </div> </article> </div> </div> </div> <script type="text/javascript" async crossorigin="anonymous" src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-8519364510543070"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js" crossorigin="anonymous" referrerpolicy="no-referrer"></script> <script> var docId = '3407af64fedb0398c9bb6f33810d98e6'; var endPage = 1; var totalPage = 122; var pfLoading = false; window.addEventListener('scroll', function () { if (pfLoading) return; var $now = $('.article-imgview .pf').eq(endPage - 1); if (document.documentElement.scrollTop + $(window).height() > $now.offset().top) { pfLoading = true; endPage++; if (endPage > totalPage) return; var imgEle = new Image(); var imgsrc = "//data.docslib.org/img/3407af64fedb0398c9bb6f33810d98e6-" + endPage + (endPage > 3 ? ".jpg" : ".webp"); imgEle.src = imgsrc; var $imgLoad = $('<div class="pf" id="pf' + endPage + '"><img src="/loading.gif"></div>'); $('.article-imgview').append($imgLoad); imgEle.addEventListener('load', function () { $imgLoad.find('img').attr('src', imgsrc); pfLoading = false }); if (endPage < 7) { adcall('pf' + endPage); } } }, { passive: true }); </script> <script> var sc_project = 11552861; var sc_invisible = 1; var sc_security = "b956b151"; </script> <script src="https://www.statcounter.com/counter/counter.js" async></script> </html>