SDL Knowledge Center Release Notes
SDL Knowledge Center 13
November 2017 Legal notice
Copyright and trademark information relating to this product release.
Copyright © 2003–2017 SDL Group.
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 2.
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
Acknowledgments ...... 2
2 Release Notes - SDL Knowledge Center ...... 11
What's new in SDL Knowledge Center ...... 12
What's New in Content Manager ...... 13 New and changed ...... 13 New and changed in version 13.0.0 ...... 13 New third-party software support ...... 13 Client tools changes ...... 14 Web Client changes ...... 17 Content Editor changes ...... 17 Typical Server Vanilla Installation using ISHDeploy ...... 18 Translation management improvements ...... 19 Web Client security ...... 22 New publish flow ...... 23 Web/App/Db server ...... 24 Fixed issues ...... 25 Fixed issues in version 13.0.0 ...... 25 Fixed Issues in 13.0.0 Web Client ...... 25 Fixed issues in 13.0.0 Client Tools ...... 26 Fixed issues in 13.0.0 Content Editor ...... 28 Fixed issues in 13.0.0 Authoring Bridge ...... 30 Fixed issues in 13.0.0 Web/App/Db server ...... 30 Known Issues ...... 32 Deprecated, Obsolete and Restrictions ...... 42 Software compatibility across releases ...... 45 Content Manager API compatibility across releases ...... 52
What's new in Content Delivery ...... 68 An initial release of a new Content Delivery platform ...... 68 Known issues in Content Delivery ...... 68
What's new in the presentation environment ...... 70 A new presentation environment- the Reference Implementation web app . . . . . 70 Known issues in the Reference Implementation ...... 71
What's new in Collaborative Review ...... 73 New and changed ...... 73
SDL Knowledge Center Release Notes iii New and changed in version 7.6.0 ...... 73 New and changed in version 7.5.0 ...... 74 Fixed issues ...... 76 Fixed issues in version 7.6.0 ...... 76 Fixed issues in version 7.5.0 ...... 78 Known Issues ...... 80
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 13.
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. Acknowledgments
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/. Akka Akka is a toolkit and runtime for building highly concurrent, distributed, and fault tolerant event- driven applications on the JVM. ANTLR ANTLR is a powerful parser generator that you can use to read, process, execute, or translate structured text or binary files. AOP Alliance AOP Alliance intends to facilitate and standardize the use of AOP to enhance existing middleware environments (such as J2EE), or development environments (e.g. JBuilder, Eclipse). The AOP Alliance also aims to ensure interoperability between Java/J2EE AOP implementations to build a larger AOP community. Apache ActiveMQ Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns server. 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 applica- tions, 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. Apache Commons BeanUtils The Java language provides Reflection and Introspection APIs (see the java.lang.reflect and java.beans packages in the JDK Javadocs). However, these APIs can be quite complex to understand and utilize. The BeanUtils component provides easy-to-use wrappers around these capabilities.
2 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1
Apache Commons Codec Apache Commons Codec (TM) software provides implementations of common encoders and decoders such as Base64, Hex, Phonetic and URLs. Apache Commons Configuration The Commons Configuration software library provides a generic configuration interface which enables a Java application to read configuration data from a variety of sources. Commons Configura- tion provides typed access to single, and multi-valued configuration parameters. Apache Commons DBCP (Database Connection Pools) Many Apache projects support interaction with a relational database. Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfea- sible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally. There are several Database Connection Pools already available, both within Apache products and elsewhere. This Commons package provides an opportu- nity to coordinate the efforts required to create and maintain an efficient, feature-rich package under the ASF license. Apache Commons HttpClient HttpClient was started in 2001 as a subproject of the Jakarta Commons, based on code developed by the Jakarta Slide project. Apache Commons Lang The standard Java libraries fail to provide enough methods for manipulation of its core classes. Apache Commons Lang provides these extra methods.
Lang provides a host of helper utilities for the java.lang API, notably String manipulation methods, basic numerical methods, object reflection, concurrency, creation and serialization and System properties. Additionally it contains basic enhancements to java.util.Date and a series of utilities dedicated to help with building methods, such as hashCode, toString and equals. Apache Commons Pool Pool provides an Object-pooling API, with three major aspects:
1. A generic object pool interface that clients and implementers can use to provide easily inter- changeable pooling implementations. 2. A toolkit for creating modular object pools. 3. Several general purpose pool implementations. 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.
SDL Knowledge Center Release Notes 3 1 Welcome to Knowledge Center Release Notes
Apache Lucene, SOLR The Apache Lucene™ project develops open-source search software. Apache Tomcat, Tomcat Embed Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. Apache XBean :: Spring XBean :: Spring provides a schema-driven proprietary namespace handler for Spring contexts. 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 AspectJ AspectJ is a seamless aspect-oriented extension to the Java programming language. It is Java platform compatible easy to learn and use. AWS SDK for Amazon SQS The AWS Java SDK for Amazon SQS module holds the client classes that are used for communicating with Amazon Simple Queue Service. AWS SDK for Java Core The AWS SDK for Java - Core module holds the classes that are used by the individual service clients to interact with Amazon Web Services. Users need to depend on aws-java-sdk artifact for accessing individual client classes. CDI APIs APIs for CDI (Contexts and Dependency Injection for Java). cglib cglib is a powerful, high performance and quality Code Generation Library, It is used to extend JAVA classes and implements interfaces at runtime. 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,... DockPanel Suite .Net Docking Library for Windows Forms dom4j dom4j is an easy to use, open source library for working with XML, XPath and XSLT on the Java platform using the Java Collections Framework and with full support for DOM, SAX and JAXP. dsinfo The dsinfo library enables you to easily use Scala-side information in implementations of embedded (internal) domain-specific languages. dsinfo is implemented using Scala macros which are an experimental feature of Scala 2.10 and 2.11.
4 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1
dsprofile The dsprofile library provides general facilities to implement domain-specific profiling in Scala and Java programs. EasyLicenser EasyLicenser is a licensing module. edtFTPj/Free Free Java FTP library gives Java developers extensive FTP functionality. 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. 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. google-gson google-gson is a Java library to convert JSON to Java objects and vice-versa. Google Guava The Guava project contains several of Google's core libraries that we rely on in our Java-based projects: collections, caching, primitives support, concurrency libraries, common annotations, string process- ing, I/O, and so forth. Hibernate Hibernate is a high-performance Object/Relational persistence and query service. The most flexible and powerful Object/Relational solution on the market, Hibernate takes care of the mapping from Java classes to database tables and from Java data types to SQL data types. It provides data query and retrieval facilities that significantly reduce development time. Hibernate's design goal is to relieve the developer from 95% of common data persistence-related programming tasks by eliminating the need for manual, hand-crafted data processing using SQL and JDBC. HK2 Framework HK2 is a light-weight and dynamic dependency injection framework.
SDL Knowledge Center Release Notes 5 1 Welcome to Knowledge Center Release Notes
HSQLDB (HyperSQL DataBase) HSQLDB (HyperSQL DataBase) is the leading SQL relational database engine written in Java. It offers a small, fast multithreaded and transactional database engine with in-memory and disk-based tables and supports embedded and server modes. It includes a powerful command line SQL tool and simple GUI query tools. 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. Jackson tooling Inspired by the quality and variety of XML tooling available for the Java platform (StAX, JAXB, etc.), the Jackson is a multi-purpose Java library for processing JSON data format. Jackson aims to be the best possible combination of fast, correct, lightweight, and ergonomic components for developers. JavaBeans Activation Framework With the JavaBeans Activation Framework standard extension, developers who use Java technology can take advantage of standard services to determine the type of an arbitrary piece of data, encapsu- late access to it, discover the operations available on it, and to instantiate the appropriate bean to perform said operation(s). JavaBeans Validation Bean Validation (JSR-303) API. Javassist (Java Programming Assistant) Javassist (Java Programming Assistant) makes Java bytecode manipulation simple. It is a class library for editing bytecodes in Java; it enables Java programs to define a new class at runtime and to modify a class file when the JVM loads it. Unlike other similar bytecode editors, Javassist provides two levels of API: source level and bytecode level. If the users use the source-level API, they can edit a class file without knowledge of the specifications of the Java bytecode. The whole API is designed with only the vocabulary of the Java language.You can even specify inserted bytecode in the form of source text; Javassist compiles it on the fly. On the other hand, the bytecode-level API allows the users to directly edit a class file as other editors. javax.annotation JSR 250 Common Annotations For The Java Platform. javax.cache Caching Java API Javax Expression Language Expression Language Java API
6 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1
javax.inject Dependency Injection Java API JAXB The goal of the JAXB project is to develop and evolve the code base for the Reference Implementation (RI) of JAXB, the Java Architecture for XML Binding. The JAXB specification is developed through the Java Community Process following the process described at jcp.org . This process involves an Expert Group with a lead that is responsible for delivering the specification, a reference implementation (RI) and a Technology Compatibility Kit (TCK). The primary goal of an RI is to support the development of the specification and to validate it. Specific RIs can have additional goals; the JAXB RI is a production-quality implementation that is used directly in a number of products by Oracle and other vendors. JBoss Java Annotation Indexer (Jandex) A Java Annotation Indexer for JBoss JBoss Logging Framework The JBoss Logging Framework. jedis A blazingly small and sane Redis Java client. Jersey RESTful WS Developing RESTful Web services that seamlessly support exposing your data in a variety of represen- tation media types and abstract away the low-level details of the client-server communication is not an easy task without a good toolkit. In order to simplify development of RESTful Web services and their clients in Java, a standard and portable JAX-RS API has been designed. Jersey RESTful Web Services framework is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. Jettison Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. This allows nearly transparent enablement of JSON based web services in services frameworks like CXF or XML serial- ization frameworks like XStream. JLine JLine is a Java library for handling console input. It is similar in functionality to BSD editline and GNU readline. People familiar with the readline/editline capabilities for modern shells (such as bash and tcsh) will find most of the command editing features of JLine to be familiar. Joda-Time Joda-Time provides a quality replacement for the Java date and time classes. The design allows for multiple calendar systems, while still providing a simple API. The 'default' calendar is the http://www.joda.org/joda-time/cal_iso.html standard which is used by XML. The Gregorian, Julian, Buddhist, Coptic, Ethiopic and Islamic systems are also included, and we welcome further additions. Supporting classes include time zone, duration, format and parsing. 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.
SDL Knowledge Center Release Notes 7 1 Welcome to Knowledge Center Release Notes
jquery-cookie jQuery plugin for reading, writing and deleting cookies. jquery.datatables DataTables is a plug-in for the jQuery Javascript library. It is a highly flexible tool, based upon the foundations of progressive enhancement, which will add advanced interaction controls to any HTML table. jquery.dataTables.columnFilter Adds advanced filter capabilities to the DataTables. JS file. jQueryFileUpload File Upload widget with multiple file selection, drag&drop support, progress bar, validation and preview images, audio and video for jQuery. jquery.TypeScript.DefinitelyTyped TypeScript Definitions (d.ts) for jquery. 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 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. JTA (Java Transaction API) The javax.transaction package. It is appropriate for inclusion in a classpath, and may be added to a Java 2 installation. Kiama The Kiama test library contains a collection of examples, tests that use those examples, and useful test support code. 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 dynami- cally (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. Logback Logback is intended as a successor to the popular log4j project, picking up where log4j leaves off.
8 SDL Knowledge Center Release Notes Welcome to Knowledge Center Release Notes 1
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. OSGi Resource Locator Part of HK2 - A light-weight and dynamic dependency injection framework. Used by various API providers that rely on META-INF/services mechanism to locate providers. PATRICIA Trie in Java An implementation of the Practical Algorithm to Retrieve Information Coded in Alphanumeric (PATRICIA). 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 Scallop Scallop is a command line parser. Scala The Scala programming language fuses object-oriented and functional programming in a statically typed programming language. It is aimed at the construction of components and component systems. SitemapGen4j SitemapGen4j is a library to generate XML sitemaps in Java. SLF4J The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time. SnakeYAML YAML is a data serialization format designed for human readability and interaction with scripting languages. SnakeYAML is a YAML parser and emitter for the Java programming language. SNMP4J SNMP4J is an enterprise class free open source and state-of-the-art SNMP implementation for Java™ 2SE 1.4 or later. SNMP4J supports command generation (managers) as well as command responding (agents). Its clean object oriented design is inspired by SNMP++, which is a well-known SNMPv1/ v2c/v3 API for C++.
SDL Knowledge Center Release Notes 9 1 Welcome to Knowledge Center Release Notes
SpringFox Automated JSON API documentation for API's built with Spring. Spring Framework The Spring Framework provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform. A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. StAX StAX is a standard XML processing API that allows you to stream XML data from and to your application. This StAX implementation is the standard pull parser implementation for JSR-173 specification. Swagger Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability. TwelveMonkeys ImageIO TwelveMonkeys ImageIO is a collection of plugins and extensions for Java's ImageIO. These plugins extends the number of image file formats supported in Java, using the javax.imageio.* package. The main purpose of this project is to provide support for formats not covered by the JRE itself. ua-parser A multi-language port of Browserscope's user agent parser. 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. WiX The WiX toolset builds Windows installation packages from XML source code. The tool-set integrates seamlessly into build processes. XULRunner XULRunner is a runtime environment developed by the Mozilla Foundation to provide a common back-end for previewing.
10 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 SDL Knowledge Center
This section provides a description of the capability-level changes introduced between SDL Knowledge Center 2016 and SDL Knowledge Center 13. Release details pertaining to individual product capabilities are found in separate sections.
Overview
The SDL Knowledge Center delivery platform has been entirely reworked. For the customer-facing online distribution and presentation of your content, the old Content Delivery (formerly named Reach External) has been replaced by a new delivery platform and a presentation web application, that are collectively referred to as Dynamic Delivery. This provides more robust, scalable and fast publishing, and allows for more complete automation. Content Manager publishes to Dynamic Delivery using a new publishing process based on plugins. The external functionality of the old Content Delivery is now renamed Legacy Content Delivery and is deprecated. Its documentation has been removed from SDL Knowledge Center 13 full documentation. However when publishing to Collaborative Review, Content Manager still uses the old publishing process. Content Manager and Collaborative Review have received major improvements.
Note: External: content used by your customers. Internal: content used for internal review.
Dynamic Delivery
The Dynamic Delivery platform consists of Content Delivery and a presentation environment. For your presentation environment, our Reference Implementation is ready to use. However you can decide to implement your own environment depending on the effort you want to put in your website. The choices are laid out for you in “” on page 0
Plugin-based publish process
Content Manager uses a new, entirely modular, publish process to publish to Dynamic Delivery, through the new output format named DITA Delivery. Each step of this process is configurable and creates specific event log traces. Details about the new publishing process are available in “Publishing Process” on page 0.
12 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
Legacy Content Delivery
With the arrival of Dynamic Delivery as new delivery platform, the former platform is renamed Legacy Content Delivery and deprecated. All documentation related to Legacy Content Delivery as a delivery platform (how to install it, scale it and customize it), has been removed from the main Knowledge Center documentation and regrouped in a specific online guide: Using Legacy Content Delivery with Knowledge Center 13 . 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 in Content Manager are described.
All Content Manager API changes are described in the Content Manager API chapter.
New and changed in version 13.0.0
An overview of new features and enhancements, as well as improved or changed functionality in Content Manager 13.0.0, compared to the previous version of the product.
This includes the new and changed features and functionality for Content Manager versions 12.0.4, 12.0.3 and 12.0.1.
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.
Software component support that was added in this release
Application server • Microsoft Windows Server 2016 (64-bit) • Microsoft SQL Server 2014 SP2 • Microsoft SQL Server 2016 SP1 • Java Runtime 1.8.0_112 (64-bit) • Java Runtime 1.8.0_144 (64-bit) • Java Development Kit 1.8.0_112 (64-bit) • Java Development Kit 1.8.0_144 (64-bit) • Microsoft Server .NET Framework 4.6.1
SDL Knowledge Center Release Notes 13 2 Release Notes - SDL Knowledge Center
• Microsoft .NET Framework Visual C++ Redistributable VS2015 (64-bit) Client Software • Oracle Data Access Client 12.2.0.1.0 • JustSystems XMetaL 11 (32bit only; requires patch version 11.0.0.083 or later) • Microsoft Edge (Spartan) • Acrolinx 5.0 Integrations • SDL TMS 11.1.x • SDL TMS 11.2.x • SDL TMS 11.3.x • SDL WorldServer 11.2.x
API changes
SOAP API are deprecated in WorldServer (WS) version 11.0.X. Content Manager version 13.0.0 is able to interact with WS through SOAP API as well as REST API. However, the default API protocol for connecting to Content Manager is now REST.
MSXML4 is replaced by MSXML6
We have removed all dependencies towards MSXML4 in Knowledge Center, you are therefore no longer required to have it installed.
Client tools changes
Client Tools improvements for this version are explained.
Personalizing properties tables
In Publication Manager and in dialogs evoked from the Knowledge Center menu in XML editors, a new right-click menu item lets you • add or remove columns in properties tables, • order columns in properties tables, • revert to the default content of the properties tables. Before this version, you needed to change configuration files in order to adapt the content of the properties tables to your needs. Now this can be done directly from the interface. All changes made through the add/remove dialog persist from a session to the next, along with your column width changes.
14 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
User interface
The client tools are now DPI aware, which results in a change of display scaling whenever Windows detects that display resolution and size requires it.
Configuration
Now, when working with metadata configuration, you can use element names instead of labels (which could cause translation issues): • The ishvaluetype attribute has been added to metadata filters so it can be passed on to the server. • The out-of-the-box MetadataConfig. xml file has been adapted, all labels are replaced by element names.
This change has not been applied to a dialog, TranslationMgmtDlg, because of the client-side operations this dialog performs.
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.
Improved all Client Tools behavior for Date/DateTime properties
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.
Improved location and focus when a Publication Manager table of contents refresh happens
The usability of Publication Manager has been greatly improved, e.g. improved navigation in the publication tree (left pane of the Content tab) and optimization of the zooming results. • Checking in a topic no longer closes opened nodes. • Changing the version of topics no longer closes opened nodes. • Checking in a map containing topic groups no longer closes opened nodes. • Saving a publication no longer moves the tree regardless of the selected object. • Moving a topic with the Move commands (from the right-click menu) no longer hides the topic: the moved topic stays visible.
SDL Knowledge Center Release Notes 15 2 Release Notes - SDL Knowledge Center
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. 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.
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
We 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.
Syncro Soft
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
16 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
Improved performance when using Arbortext
The Authoring Bridge has been adapted to the way Arbortext resolves conrefs so that redundant calls have been dramatically reduced, thus improving performance when using this Editor.
Web Client changes
Web Client improvements for this version.
Properties dialogs
The properties/metadata dialogs in the Web Client are no longer based on a list of Rep*.asp files (one for each level). It is now based on the same file that is used by the client tools: the metadataconfig. xml file. As a consequence: • Web Client and Client Tools are brought closer together for metadata management and user interface. • Field creation and management in the Web Client properties dialogs is simpler. • Upgrades are easier. • Future localization of the Web Client interface are now possible. Functional enhancements: • Multiple dialog windows can now be displayed at the same time. • Better assistance is provided for user interaction: Sorting, reordering, tool tips...
Content Editor changes
A description of new and improved Content Editor behavior
Image handling and uploading from the Content Editor
You can now upload images from Content Editor. Also when working with images in Content Editor you can now do the following: • Drag and drop an image file over the library panel in Content Editor to upload the image. When navigating the repository you can navigate to an image folder, then you can drag and drop an image from your file system into the selected folder. • Rename images from Content Editor. When selecting an image from the Content Manager reposi- tory, you can now change its title. This changes the title of the object in the repository, not only the title of the image in the topic you are currently editing.
SDL Knowledge Center Release Notes 17 2 Release Notes - SDL Knowledge Center
Changes to the User Interface (UI)
We've made a few changes as follows: • The Content Editor UI is updated to align with new SDL branding. • We've added some new buttons for some commonly used elements: Code Phrase, UI Control and Filepath. In the ribbon toolbar we've grouped these buttons together with the Code Block button in a new grouping called Software. • The UI provided in Chinese is now more complete. We've added Chinese translations for several UI elements that were missing from earlier versions of the editor.
Deprecated methods and warning messages
We've deprecated a method and added better messaging for deprecated methods. • XopusText.isElementContentWhitespace method is now deprecated. This method is analo- gous to a browser method that is already obsolete, Text.isElementContentWhitespace. For more information on this method refer to: https://developer.mozilla.org/en-US/docs/Web/API/Text/isElementContentWhitespace . This method may not work in all browsers and we discourage you from using this method since XopusText.isElementContentWhitespace might be removed in future. • Added a console message for deprecated methods. We've deprecated some API methods and you can expect these methods to be removed from a future version of the editor. To help you prepare for when support for these methods is removed altogether, we now provide a message in the devel- opers' console to indicate when a deprecated method was used.
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.
18 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
ISHDeploy ISHDeploy is a separate PowerShell module that lets you literally code your configuration intentions. The name of this module is ISHDeploy xx, where xx is the version of Content Manager it is compatible with.
For example Knowledge Center 13 matches ISHDeploy 13. . This module uses cmdlets with which you can express 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 mecha- nism if the system for example detects the wrong ps_java_home parameter value.
Translation management improvements
Translation Manager, Translation Builder and Translation Organizer have been improved in this release.
New translation review flow
The translation flow has been upgraded to include a review step: rejecting translations no longer requires that you create a new job for submitting the rejected items again. The basic translation flow is now: • Send for translation. • Receive, then accept or reject the translated items. • The accepted ones are done, the rejected ones go back to translation and come back corrected. • The job can be closed when all items are accepted. All documentation about the translation flow has been updated accordingly. Check out the Deprecated, obsolete... chapter of the Release Notes for details about compatibility. Main changes: • New statuses (Translation in review, Translation rejected) and transitions have been added to the out-of-the-box set. • Translated has become Translation accepted. You need to rename this status manually if you want to use a translation system. • The interaction between Translation Organizer/Translation Builder and the external translation systems (WorldServer, TMS) have been adapted.
Note: There is a way to skip the approval step with the transition from In translation to Translation approved, in case you want to stay close to the old flow.
SDL Knowledge Center Release Notes 19 2 Release Notes - SDL Knowledge Center
Translation flow made static
The out-of-the-box list of statuses and transitions for the translation is now the reference for all users. This provides a simple and firm basis for both users and system. Main changes: • All the statuses and status transitions you need for a complete translation flow is out-of-the-box. • Statuses and transitions from the box are the recommended ones. • This reference flow can be changed/adapted: it requires a configuration operation. Complete descriptions can be found in the full documentation.
Improved cancellation feature
Main changes: • Cancellation has a stable and consistent behavior whichever system you use for your translation: file system (internal), WorldServer (extenal), TMS (external). • A cancellation rolls the items back to To be translated. • New job statuses (CancellationRequested, SkippedSending, SkippedRetrieving, ItemsRoll- backPending, ItemsRollback, ItemsRollbackFailed, JobRollbackPending, JobRollback, JobRollbackFailed) and transitions have been added to the out-of-the-box set. Complete descriptions can be found in the full documentation.
Translation procedure simplification
In previous versions you needed to add Requested languages in the publication's version properties before you could create a translation report for these languages. You also needed to manually create the export file using the report. Now when you create a translation job, the translation dialog lets you select the target languages whether or not the languages are part of the Requested languages in the properties, then the system automatically generates the export files and sends them. The system also updates the Requested languages list with any language you may have added to this translation job, this makes sure you can then generate a report for a current translation job.
Removed racing condition that sends 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
20 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
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
The status In Translation is checked again just before sending, and topics are sent one at a time. No more double sending.
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.
SDL Knowledge Center Release Notes 21 2 Release Notes - SDL Knowledge Center
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.
Other improvements
• Translation Organizer no longer returns all tasks together with the project when it ends, thus improving the performance. • We included the time in the database, taking the time zone into account. This allows for better time management by Translation Organizer.
Web Client security
Improvements specific to Web Client security
Password encryption
For ISHSTS, the password encryption has been improved and the functionality has been extended with additional fields: • Passwords are no longer limited to 100 characters. • Read-only fields have been added to the user dialog, providing information for: • last login time (FISHLASTLOGINON ), • last password modification time (FISHPASSWORDMODIFIEDON ), • lock time (FISHLOCKEDSINCE ) and • number of failed attempts (FISHFAILEDATTEMPTS ). ISHSTS relies on Content Manager being the Identity Provider for user accounts. We still recommend you use external Secure Token Services (STS) to allow more fine-tuned user management integrated with your domain.
22 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
Access to published content
In the repository, the usergroup property of three types of folders has a consequence on which user can access which published content whenever it is published to Collaborative Review. The folder types are: Publications, Topics and Maps. When these folders are set to be accessible to a usergroup, then only users in this group can see the published publications, topics or maps content when using Collaborative Review. It also filters the search results, and the comments attached to this content. This only applies when ISHSTS is used for authentication.
New publish flow
A new publish flow, resorting to post-process plugins instead of scripts, has been developed in order to enable optimal Content Manager interactions with the Dynamic Delivery. It also provides better performance, flexibility and control over the publish process. This process is used only when publishing for Dynamic Delivery (using the DITA Delivery output format).
Overview
With the introduction of a new technology for displaying the content online (Dynamic Delivery) we also replaced the technology underlying the Content Manager publish process. In this new process, the content transformation phase (from XML to HTML) is controlled by plugins instead of scripts. This gives publish more modularity, allowing for a better visibility and control. Performance and also troubleshooting capacity are improved. Moreover, it is now possible to add/remove extra steps during or after the transformation phase using optional plugins. This new technology brings about a list of changes.
New customization capacity
It is now possible to add or remove post-process steps in the publish process using plugins. The out-of- the-box plugins must remain however. All the available plugins, mandatory or optional, are described.
New output format
To publish to Dynamic Delivery, use the DITA Delivery output format. This format can be added to the available output formats using the Web Client interface, like all the other output formats. It is however recommended to use a script as described.
New publication properties
Product Family Name and Product Release Name are publication properties used by Dynamic Delivery to organize the publications: grouping them by family and ordering them inside a family by release number. The values for both these properties are selected from a list that you define beforehand in the Web Client.
SDL Knowledge Center Release Notes 23 2 Release Notes - SDL Knowledge Center
New publication output statuses
The new publish process can now display a Deploying Draft and a Deploying Release Candidate status after the traditional Publishing status and before the Draft or Release Candidate statuses. These new statuses indicate that while the publish has not completed yet, some of the new content can already be accessed by readers online. All statuses and status transitions for output formats are described. Moreover, the conditions for a publication output to receive the status Out-of-date have been extended.
New publication output property
The Remote Status property indicates whether you want the new content to be seen by readers online or not. The default value is Online (readers online have access to currently deployed content).
More detailed logs
The event log displays separate actions for each post-process plugin individually, making it easier to troubleshoot whenever an issue arises during publish.
Overall procedure
This applies only to publish to the DITA Delivery output format. Using the new publish process based on post-process plugins involves the following steps: 1. Implement additional post-process plugins for any specific publish need not covered by the out-of- the-box sequence of plugins. 2. Add the DITA Delivery output format, preferably using a script. 3. Create Product Family Name and Product Release Name values according to your needs using the Web Client. 4. When your publication is ready for publish, create the DITA Delivery output format for it, from Publication Manager. 5. Select the appropriate Product Release Name and Product Release Name for this output format's properties. 6. Check the Remote Status (Online by default). 7. Hit the Publish button and check the progress through the status changes or the publish events.
Web/App/Db server
Web/App/Db server have been improved in this version.
• The CD executable can now be created with 7-Zip. The extracting window has been adapted accordingly. • The installation of the application no longer depends on GAC. This considerably facilitates instal- lation and evolution of complex systems, especially those involving multiple Content Manager installation (with different names) in a single system. This changes the structure of the CD, for customization: Assemblies are now located next to the executables that use them, rather than all in the same place.
24 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
Fixed issues
Issues that were fixed from Content Manager are described.
Fixed issues in version 13.0.0
An overview of bug fixes and issues that were addressed in Content Manager 13.0.0, 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.
For your convenience, bug fixes implemented in Content Manager versions 12.0.4, 12.0.3 and 12.0.1 are included in this document as well, by order of recency.
Fixed Issues in 13.0.0 Web Client
The following Web Client issues are fixed in Content Manager 13.0.0 compared to 12.0.0.
• 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] • 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]. • We replaced state by status in Settings > Initial Status and error messages whenever we referred to statuses [TS-11702|SRQ-5321]. • 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
SDL Knowledge Center Release Notes 25 2 Release Notes - SDL Knowledge Center
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]
Fixed issues in 13.0.0 Client Tools
The following Client Tools issues are fixed in Content Manager 13.0.0 compared to 12.0.0.
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. • 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 '
Publication Manager • In Publication Manager it is no longer possible to drag and drop objects from the Repository to any other tab than the Content tab [TS-11222|SRQ-4788]. • The bug in Publication Manager making a publication content disappear from the left-hand navigation panel when the baseline was changed in the publication's properties, has been fixed. [TS-11237|SRQ-4850] • 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 applica- tion, typically Publication Manager [TS-12530|SRQ-6623] • 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
26 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
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]. • 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
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 27 2 Release Notes - SDL Knowledge Center
Content 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 13.0.0 Content Editor
A description of the editor fixes in this release.
List editing issues
• Improved behavior when copying from outside sources such as Microsoft Word or another HTML page and pasting into a list. When copying and pasting into a list, the content can be copied either from another a list within the document being edited or may be copied from outside sources. In the past the behavior when pasting into a list was different depending on the source of the content. Now you can expect the same behavior when pasting regardless of whether the content comes from within or outside of the document being edited. • Fixed a bug where lists defined by list role were not splitting correctly. There are standard list types such as definition, unordered and ordered. If you do not want to use one of the standard types you can use the list role to configure your lists. In this fix, users can expect to split lists correctly even if the lists were configured using the list role. For more information on list roles please refer to our API references: “ List roles” on page 0. • Improved pasting of list items. When pasting several list items rather than the whole list, they were pasted as separate paragraphs. Now they are pasted as one unit into the new list.
Pasting issues
• Fixed a regression where the “XopusAfterPaste” on page 0 event was not being fired after you pasted at the start of a textnode (just after bold, beginning of a paragraph, etc). With this fix this event will be fired regardless of where the user pastes his or her content. • Fixed a bug that caused the XML view to collapse when pasting. The XML view has a feature to show only certain sections of the document by expanding and collapsing XML elements. Pasting content into the XML view caused all elements to be collapsed. This has now been fixed so that the XML view will remain in the same state after pasting content from the clipboard. • Fixed the bug in which it was impossible to paste whitespace such as space or tabs. After changing some copy/paste behavior in the previous release, it was no longer possible to paste whitespace. This is now possible again.
Google Chrome issues
• Due to a change introduced with Google Chrome 61.0.3163.79, the cursor was misplaced after scrolling. With this fix when using the editor in Chrome from 61.0.3163.79 onwards, the cursor will be rendered in the correct position after scrolling. • Fixed a bug where scrolling by using mouse selection didn't work in Google Chrome. The bug was only reproducible in Google Chrome and the issue was that a document wouldn't scroll while selecting the text by using mouse. The behavior is now aligned with Firefox and IE. • A problem was affecting Google Chrome users in which pressing right-click sometimes modified
28 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
an existing selection. We've disabled the possibility to make or change a selection with a non- primary mouse button. Before this change users could make selections by dragging with any mouse button pressed. Now this only possible when dragging and pressing the primary mouse button. The primary button is usually the left button. The other buttons still function, but can no longer modify the selection and this is a fix so that Google Chrome users will not accidentally modify selections.
Resize and/or mouse issues
Implementers can configure the editor so that it will be easier for users to resize their tables and images by enabling resize handles. More details can be found in the section “About configuring resizing for tables or images” on page 0. • Resize handles were not show for images or tables when you used a mouse to try to resize. Now the handles appear when expected . • When dragging a resize handle to resize and letting go outside of the document iframe, the dragging operation was not finished correctly, and the mouse cursor disappeared. With this fix you can finish dragging anywhere, also outside of the iframe and the mouse cursor remains visible. • It was not possible to resize a column in a CALS table in the left direction. We've fixed this bug so that you can resize columns properly.
Various editing issues
• Fixed a bug where table structure was incorrect after certain editing actions. Because the number of columns in a table was not calculated correctly after certain editing operations such as undo, there was some unexpected editor behavior. For example it would be no longer possible to delete columns after an undo operation. This problem is now fixed. • Fixed incorrect cursor position in text rendered from right to left. When loading text in a right to left language like Arabic or Hebrew, the cursor was rendered one position too far to the left, and typing and other editing operations were happening in a different place than where the cursor was shown. This is now fixed. With this fix, edits such as typing or deleting occur in the same place as the cursor. • Fixed a bug with a jumping caret in the search panel. When modifying text in either Find or Replace fields of the search panel, the caret was jumping to the end of the string. The caret now stays where you are typing. • When previewing an image in Content Editor's library panel, image names that were long were not being wrapped and could go outside of the bounds of the preview pop-up. We've fixed this issue with the display of long image names when previewing images • When using Content Editor to edit topics from the Collaborative Review interface, and closing a topic then opening another, the task ribbon tab would appear multiple times. This issue also affected custom tabs. This has been fixed now so that task and custom tabs are shown properly.
SDL Knowledge Center Release Notes 29 2 Release Notes - SDL Knowledge Center
Fixed issues in 13.0.0 Authoring Bridge
The following Authoring Bridge issues are fixed in Content Manager 13.0.0 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]
Fixed issues in 13.0.0 Web/App/Db server
The following issues are fixed in Content Manager 13.0.0 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
30 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
PublishService
• By 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] • 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 valida- tion 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 when DITA-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]
TranslationOrganizer
• Translation Organizer: for jobs involving external systems, the job information in the log file now specifies the result of steps that completed successfully. [TS-10565] • Translation Organizer: The file system export for translation no longer creates empty archives. [TS-11504] • When the Translation Organizer is killed during an export, it no longer resets the exported file counter. [TS-10281] • TranslationOrganizer 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].
SDL Knowledge Center Release Notes 31 2 Release Notes - SDL Knowledge Center
• 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]
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].
Other
• For 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] • 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]. • In some upload and prepare situations, cancelling a publish process from Content Manager failed to unlock the publication in Collaborative Review. This has been fixed. [TS-11398|TS-11399|SRQ- 5088]. • Duplicate values are now removed from the FISHLINKS and FISHFRAGMENTLINKS fields of the ISHSYSFRAGMENTLINKSTOMETADATA write plugin whenever a topic contains the same conref multiple times or contains multiple conrefs from the same library. [SCTCM-83|SRQ-7227]
Known Issues
The 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
32 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
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 all 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
SDL Knowledge Center Release Notes 33 2 Release Notes - SDL Knowledge Center
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; 4. 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 some- times 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.
34 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
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
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
SDL Knowledge Center Release Notes 35 2 Release Notes - SDL Knowledge Center
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 auto- mated @navtitle attribute to
36 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
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 preview are:
SDL Knowledge Center Release Notes 37 2 Release Notes - SDL Knowledge Center
when refreshing references. [TS-5641] • Dynamic Link Text Resolving of
38 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
Authoring Bridge SDK is made of .NET libraries •
SDL Knowledge Center Release Notes 39 2 Release Notes - SDL Knowledge Center
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 lowercased 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]
40 SDL Knowledge Center Release Notes Release Notes - SDL Knowledge Center 2
• 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] Publishing to Dynamic Delivery
• The conversion from XML to HTML performed by the ishditadelivery plugin has the following limitations: •