SDL LiveContent Architect 11.0 Release Notes
SDL LiveContent Architect 11.0 July 2014 Legal Notices
Copyright and trademark information relating to this product release. Copyright © 2011-2014 SDL Group. SDL Group means SDL PLC. and its subsidiaries. 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/or its subsidiaries 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 LiveContent 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 89 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. 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 LiveContent Architect 11.0 Release Notes Contents
1 New and changed ...... 1 New and changed in SDL LiveContent Architect version 11.0.0 ...... 1 Terminology and Look & Feel ...... 1 New third-party software support ...... 2 Client Tools Usability Improvements ...... 3 Client Tools Stability and Performance ...... 9 Logging library mechanism ...... 11 Translation Flow and Integration Improvements ...... 12 API changes ...... 17 Programmer's Interface Changes ...... 20 Typical Server Installation Changes ...... 23 Verified Acrolynx on top of AuthoringBridge for XMetaL and oXygen ...... 25 Optimized Federated Services ...... 26 Background Task Introduction ...... 28 Light Weight Media Manager Integration ...... 31 Content Quality Rules Integration ...... 31
2 Fixed issues ...... 33 Fixed Issues in version 11.0.0 ...... 33 Fixed Issues in 11.0.0 Web Client ...... 33 Fixed Issues in 11.0.0 Client Tools ...... 39 Fixed Issues in 11.0.0 Editors ...... 45 Fixed Issues in 11.0.0 Web/App/Db Server ...... 49 Fixed Issues in 11.0.0 Documentation ...... 56
3 Known Issues ...... 59
4 Deprecated, Obsolete and Restrictions ...... 69 Software compatibility for previous releases ...... 71
5 Acknowledgements ...... 89
SDL LiveContent Architect 11.0 Release Notes III IV SDL LiveContent Architect 11.0 Release Notes Chapter 1 New and changed
New or changed features and functionality from SDL LiveContent Architect are described.
New and changed in SDL LiveContent Architect version 11.0.0
New or changed features and functionality in SDL LiveContent Architect 11.0.0 compared to 10.0.0 are described.
If you are upgrading from a release prior to SDL LiveContent Architect 10.0.0 refer to the release notes for the versions between. For your convenience, what is new and changed for SDL LiveContent Architect versions 10.0.1, 10.0.2, 10.0.3, 10.0.4 and 10.0.5 are included in this document.
Terminology and Look & Feel
Web Client and Client Tools received an updated, bringing them closer together. On top we standardized to OASIS DITA terminology for our object types. ■ Terminology in the product now adheres to DITA terminology. Since the user base of SDL LiveContent Architect is predominantly relying on the OASIS DITA standard we have adapted all user interface(s) to show the OASIS DITA terminology. We used the following mapping:
Previous terminology New terminology Master Map (Information) Module Topic Illustration, Graphic Image Template Other (Word, PDF...) Library (module) Library Topic
SDL LiveContent Architect 11.0 Release Notes 1 New and changed
Note: You will see the previous terminology in configuration files and while developing.
■ In our Web Client we introduced a navigation frame and made the styling consistent with the SDL UX style guide (Carbon 2.0). You will recognize this across all SDL products where it will provide a consistent UI design and branding. A new slide-out navigation pane was added were all SDL products in use will appear in navigation groups with navigation entries inside of them. This slide-out navigation pane will be used to approach the SDL product of your need. ■ Client Tools styling is now also consistent with the SDL UX style guide (Carbon 2.0). You will recognize the same styling from the web client. We've altered icons, the layout of the tree and list views.
New third-party software support
Support for databases, operating systems and xml editors has been updated.
Generally, SDL provides platform support for up to two versions of any given platform to provide more flexibility in how organizations incorporate vendor changes. Typically, SDL provides support for the latest and previous version of a third party platform. This previous version is implicitly marked as deprecated. The following software component support was added in this release Client Software ■ Microsoft Windows 8.1 ■ Microsoft Internet Explorer 11 ■ Google Chrome (release update channel) ■ Mozilla FireFox (release update channel) ■ JustSystems XMetaL 8 and 8 Japanese ■ JustSystems XMetaL 9
Note: There are no plans known for a 9 Japanese edition.
■ Arbortext Editor 6 ■
2 SDL LiveContent Architect 11.0 Release Notes New and changed
■ Java Runtime 1.7.0_21 (64b) ■ Powershell v4.0 (part of Windows Management Framework 3.0 )
Client Tools Usability Improvements
Some Client Tools usability improvements explained.
New installers ■ We now have .MSI installers per XMLeditor and no longer per editor version. They will detect and offer you a selection on which version you want to install. ■ All .MSI files (and assemblies) are now signed by our legal entity certificate SDL Trisoft. This avoids the yellow User Account Control (UAC) message indicating that “The publisher is unknown”. ■ The matching ClientConfig. xml was extended and also received a new condition name ClientEdition to distinct the regular JustSystems XMetaL 8 (8.0-CRCL) with the Japanese JustSystems XMetaL 8 J(apanese) (8.0-J-CRCL) XML editor as their executable file name nor version differs.
Menu option 'Duplicate'
The menu option Duplicate will show up in the folder view and allows you to make a copy of the select item(s). These items can be topics, maps, library topics, images and other (PDF, Word,...). We've also added several Locate in Repository menu options to allow easier navigation to this new functionality.
Similar to other batch functions in the Browse Repository dialog like import images, batch metadata,... the properties dialog will only be raised when required. The title of your object will be concatenated with a sequence number like (1), very similar to a New Folder experience on Microsoft Windows.
The main difference of Duplicate compared to existing functionality Check in as is that you don't have to go over a Check outor Viewoperation into your XMLeditor.
Proxy server authentication support
Client Tools render the preview and comments using a browser control. The browser control potentially used to raise an Authentication Required dialog for proxy server authentication next to the standard Client Tools control Connect to .... The credentials from the Connect to ... control are now automatically pushed into the browser control making the proxy server authentication interaction smoother and more predictable.
The Client Tools will first pick up and respect any .config configured
SDL LiveContent Architect 11.0 Release Notes 3 New and changed
Preview does dynamic link text resolving for
When browsing the repository in a Insert Hyperlink dialog the Text to display text field will be left empty. Publication Manager and the XML editors involved will try to resolve the empty
Our Client Tools' preview will do dynamic resolving for link texts on
Preview resolves @conrefs and @conref ranges
Like before, your active publication in Publication Manager will be used as context to resolve versions of the necessary referenced resources.
From now on, your XML editors integration and previews like in Browse Repository or Where Used will render dynamic content like @conref. The resource will be resolved based on the LatestVersion principle.
Restriction: Key based references like for example @varref cannot be resolved because the context of resource assignment is missing.
Preview XML pretty print
Toggling to the XML view of your rendered object will show you the XML using syntax highlighting. The Client Tools preview option to do an XML View has been standardized to use pretty printing. Before you could have a text based XML view or pretty printing depending on having commenting enabled or disabled. In case you want to see the unprocessed XML, we suggest to go to the LocalStorage on the file system. [TS-6419]
Conditions are rendered in the tree
The tree representing the resolved OASIS DITA Maps are no also color coded with a red or green background to indicate if the tree node and its children will be part of the publication or not. The calculation method is exactly the same as when looking at the color coding of a previewed map in Publication Manager. [TS-8608]
Conditions render using labels instead of identifiers
The actual value in an XML file for @ishcondition consists out of readable identifiers (Internal Names). From now on the user interface Context Builder in Publication Manager, and Condition Builder in Publication Manager and XML editors will resolve the internal names to labels (if available in your configuration through ishcondition- management) for all UI read only screens. [TS-8465|TS-8464]
4 SDL LiveContent Architect 11.0 Release Notes New and changed
Tip: Most customers set up their labels and internal names almost exactly the same upon our advise. This makes any preview - which renders what is available in the @ishcondition work quite well.
Tip: Using Condition Manager you can make sure that the labels match up with the internal names. These changes are eventually saved in ishconditionmanagement in your System area.
[TS-8464|TS-8465|SRQ-2117]
Batch metadata extended to allow append operation on multi-value fields
A commonly heard request was to allow an Append operation on multi-value fields. We introduce a placeholder that will show up in the metadata assist window when doing a group action on multiple objects. So on ListOfValue fields like for example Requested Languages, you can now add languages to your selected objects. [TS-4334]
As reminder this functionality allows you to reassign multiple topics to a different person or change the status of multiple topics.
Tip: In scenarios where order matters, you can also do a Prepend of the existing values besides an Append by moving the (Current values) entry in the text field.
Restriction: There are some limitations however: ■ The user sees a list with all possible status transitions for the selected objects. The status is always enabled, if an error occurs, the object appears in the error list at the bottom of the application. ■ The system checks if all objects are of the same object type. If not, it is not possible to change the properties in batch. An appropriate error message is displayed to the user. ■ It is not possible to change the status for multiple topics if those topics have different statuses. This has been done to prevent users from making invalid status transitions.
Publication Manager menu options 'Open...', 'Open With...' and 'Check Out With...'
Publication Manager shows you the new options Open..., Open With... and Check Out With... in the context menus.
SDL LiveContent Architect 11.0 Release Notes 5 New and changed
The tree view in Publication Manager had a Check Out menu option which will still immediately check out the selected map inside Publication Manager. The newly added option Check Out With... will trigger your operating systems Choose the program dialog. This allows you to select your favorite XML editor to start editing the OASIS DITA Map.
Menu options Open... and Open With... are added and allow you to open the selected item in your XML editor. Where Open... will use the program linked to .xml and Open With... will trigger your operating systems Choose the program dialog. If a file was already checked out before, then the file will be opened ready for editing in your XML editor.
Publication Manager menu option 'Clean Up'
When working on a publication, it can happen that the baseline overview contains lots of unreferenced objects. This can be caused by selecting different versions of maps or topics which in turn add or remove linked topics or images. Or because the baseline is shared among publications. When executing a Release of your PublicationOutput (essentially the baseline Freeze) will clean up the unused items across all publications. Users requested a manual action that forces a baseline clean-up without freezing it.
The menu option Clean Up appears in Publication Manager's baseline view. All objects not referenced by any publication using the baseline are removed from the baseline.
It is important to know that this baseline operation is executed server-side, so using the objects as available in the repository. This means that Publication Manager will request you to make every checked out object available on the server by triggering a save action.
Publication Manager menu option 'Refresh'
Publication Manager has a main menu option Refresh. This refreshes the current publication; thereby updating panes like the tree, baseline, etc.
Every pane that supports it, received a local Refresh option. So a toolbar button and context menu item on panes like Output, Preview, etc. The tool tip messaging is more clear on which area it will have an effect.
The well known shortcut key F5 will refresh the pane with focus.
Publication Manager Where Used shows 'all' publication versions upon selection of any object
When selecting an object in Publication Manager, the where used reports shows all the relevant publications based on latest version principle. In the table below you see the new information result items highlighted compared to the previous release. The default value of this report control changed from Publication to Repository. [TS-5825]
6 SDL LiveContent Architect 11.0 Release Notes New and changed
Se- Map Topic Image Library Variable Condition lected type
Result- Map, Map, Topic, Map, Topic, Map, Topic, Map, Topic, Map, Topic, ing Topic, Library, Library, Library, Library Library type Library, Publication Publication Publication Publi- cation
Restriction: Reporting on publications holding complex (OASIS DITA) linking structures could result in false positives. So it can happen that publications are shown as a result although the topic is not really used in it. This is caused by balancing performance with exactness of the result because of reasons like: ■ When the baseline is shared between multiple publications. ■ When changing the version of the map, topics referenced within the old map version can get excluded from the publication, but are not removed from the baseline. ■ If a library contains @conrefs with illustrations or links to other topics, all referenced objects are included in the publication even if they are not used in the final output. ■ 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.
Publication Manager allows a full text search limited to the Current Publication
To better support Find and Replace scenarios we introduced a heavy-lifting full text search functionality in Publication Manager. You can now make use of all full text search functionality you know off, and have your search results limited to the Current Publication. The Search Results widget then allows actions like Locate in Publication and Check Out. [TS-46]
Important to know is that search results are always sorted by ISHSCORE, so best match. The query will make use of your current publication's working language and resolution to know which objects are part of your publication. The query is executed server-side, that is why Publication Manager will prompt you to optionally save all your current edits because a simple edit to your Map could have an effect on your search results.
SDL LiveContent Architect 11.0 Release Notes 7 New and changed
Restriction: Reporting on publications holding complex (OASIS DITA) linking structures could result in false positives. So it can happen that publications are shown as a result although the topic is not really used in it. This is caused by balancing performance with exactness of the result because of reasons like: ■ When no explicit languages are mentioned, the publication's working language will be used together will all available image resolutions. Specifying an image resolution as search criteria will filter your search results to images only. ■ Fallback languages are not taken into account. ■ When changing the content of a map or topics, the newly referenced content might get included in your publication search result, although not visible yet in your publication view. An auto completion mode like LatestAvailable will try to cover this gray area of unselected items in the baseline. ■ The availability of sibling 'target' languages. The reports starts from your working language and resolution. ■ Variables, conrefs, and conditions are not expanded; similar to the regular search.
Publication Manager allows to resolve duplicate variable assignments
When multiple resources define the same variable (so same @varid), the variable reporting screen will now show you an entry for every resource that defines the variable. This allows you to resolve conflicts like “The variable is defined 2 times.”. [TS-6926]
Publication Manager system status icons
Hovering text and context menus were revisited and we introduce extra icons that indicate the status of all objects by showing: 1. Warning / Error 2. No version selected 3. Released 4. Checked in / Checked out by another user / Checked out
Condition Manager got the standard Where Used pane
With a condition select the context menu allowed you to do a Find > In Documents which now opens the standard Where Used pane. Compared to the previous pane, it offers you: ■ improved performance ■ latest version view only, so not showing all versions anymore ■ the context menu functionality you are used to
8 SDL LiveContent Architect 11.0 Release Notes New and changed
Authoring Bridge menu option 'Check In All...'
In your XML editor the SDL LiveContent menu now received an option Check In All.... The option will attempt to check in all open files to the repository.
DITA2Trisoft
DITA2Trisoft command line options to run it unattended. When you run from the command line, no user interaction is required. The actions that the tool is to perform are passed in the command line parameters. Errors and other messages are logged to a file and the program closes automatically when it is finished with the requested task(s).
Client Tools Stability and Performance
Some Client Tools stability and performance improvements explained.
General
There are various small improvements ranging from small tweaks like what happens if you press cancel when trying to check in an invalid XML file in XMetaL to bigger entries as explained here.
Overall the Client Tools are at the top of the pyramid, they inherit all improvements from the lower levels like the new API calls, redesigned interfaces, optimizations on the federated services, database and operating system improvements.
New logging library
We standardized on NLog logging library. For Client Tools this means that logging configuration moved out of the application's .config file into a dedicated NLog.config file like for example C:\Program Files (x86)\Trisoft\ 11.1\Publication Manager\Nlog.config.
Tip: Nice to know is that saved changes to the NLog.config are instantly active in the current process.
Allowed log levels are: Trace, Debug, Info, Warn, Error and Fatal. These can be configured in the
SOAP compression for slower or high-latency network
SDL LiveContent Architect 11.0 Release Notes 9 New and changed
connections
From now on out-of-the-box the Client Tools will ask the web services to respond with a compressed SOAP response. This effect is mostly visible for metadata retrieval calls (like used when opening a publication in Publication Manager) over slower or high-latency network connections where transferring less data results in a more responsive application. Technically the Client Tools will send a request header Accept-Encoding: gzip, deflate where an out-of-the-box web/app server will return the same uncompressed result as before. To have the web/app server answer with a compressed SOAP response you have to reconfigure your Microsoft IIS. [TS-6894] If your system administrator did a “Configuring IIS applicationHost.Config”, then InstallTool will have configured the remaining steps for you. Otherwise, you can configure your web/app servers as documented in section "Configure IIS to support gzip on SOAP responses".
Proxy server authentication support
Proxy server support verified and extended for the Client Tools and the GeckoFX-based preview. [TS-8001|TS-7956|SRQ-1306] ■ When proxy authentication is required, the user is presented with the login dialog from Architect. The credentials for the proxy are now pushed to the browser control. ■ A user can select Remember password, to avoid getting prompted for the proxy credentials again by the Client Tools across application restarts. If Remember password remains unselected, the value will only be kept for the session. The separate browser control will no longer prompt. ■ Overall the Internet Explorer settings are used (see Internet Properties > Connections > LAN Settings). This behavior can be overwritten by adapting the application's .config file and introducing standard .NET runtime system.net/ defaultProxy entries. This could be a full disable; a single proxy specification for the http protocol or a PAC file (Proxy Auto Configuration). All settings will be pushed by the Client Tools into the GeckoFX-based browser control.
Publication Manager showing comments
The retrieval of comments inSDL LiveContent Reach is no longer based on a shared UI but data API driven. [TS-8407|TS-8248]
We tweaked the integration that in case the SDL LiveContent Reach link is not responding that the Client Tools' preview does respond better. Any data retrieval is disabled until a refresh (F5) happens. [TS-8403]
10 SDL LiveContent Architect 11.0 Release Notes New and changed
Less, parallel or optimized calls ■ Skipping unnecessary Folder25.RetrieveMetadataByIshFolderRefs for the where used report of Current Publication and Entire Repository. [TS-7630] ■ Parallel execution of DocumentObj25. ContainingLogicalId and PublicationOutput25. Containing for the Where Used reporting. ■ Parallel execution upon Publication Manager initialization. [TS-8040] ■ Optimized group retrieval of 300 items (typically) results in faster loading of the baseline views. [TS-8457] ■ Optimized the creation of warning objects. Viewing the folder content in English when not all objects have English yet is more performant. [TS-8027] ■ Resolving @conrefs (and possibly variables, xrefs, ...) could be slow because the version check happened for every @conref. [TS-7629]
Logging library mechanism
Logging library for all .NET framework based code changed to NLOG.
All Client Tools and server side .NET framework based code changed from a proprietary log format to this open-source based log system.
This log system is based on “http://nlog-project.org/”and has various features like: ■ Changes to the configuration NLog.config are picked up immediately - no application restart required. ■ Standard logging targets can be extended in dimensions like archiving, database logging,... ■ Have a look at other options and possibilities on “https://github.com/nlog/nlog/ wiki/Configuration-file”
Client Tools logging settings moved from the application's .config like for example C:\Program Files (x86)\Trisoft\Publication Manager\11.1\ Trisoft.PublicationManager.Host.exe.config into a more dedicated configuration file like for example C:\Program Files (x86)\Trisoft\ Publication Manager\11.1\NLog.config.
SDL LiveContent Architect 11.0 Release Notes 11 New and changed layout="${fileLayout}" fileName="${environment:variable=USERPROFILE}\Local Settings\Application Data\Trisoft\InfoShare Client\11.1\ Log\Publication Manager.log" encoding="utf-8" archiveAboveSize="2000000" maxArchiveFiles="3" archiveNumbering="Rolling" keepFileOpen="false" />
Tweaking the minLevel attribute from Warn to values like Trace, Debug, Info, Warn, Error, Fatal means that this logger rule will only match if the logged statement matches up to that criteria. So simply changing this value from Warn to Trace and saving the NLog.config file will be immediately picked up by the application.
Translation Flow and Integration Improvements
The Translation Job notion we introduced last release (10.0.x) has received improvements like relocalisation flow, an ability to export to the file system and a tight integration to SDL TMS,similar to the one we have for SDL WorldServer.
General
The requested languages field of a publication version will now automatically be updated by the service. The calculation is a union of the languages already set and the languages of the Translation Job where the publication was assigned to. Now you can immediately request a report in a send out language.
The Translation Job user interface was tweaked to reduce the number of clicks again. A new control for language/workflow selection with Select All and Deselect All, where we default to all selected. The Translation template drop down values now indicate for which system and alias they are. The Job Scope section allows you to select either Regular potentially re-exporting already send out items; or Only previously rejected translation items.
The rejected translation items flow - also known as relocalisation or retranslation - is a workflow extension on the typical flow: To be translated, In translation and Translated with Translation rejected back to In translation. The actual statuses are configurable as described in the requirements section for the integration. Any Translation Job set up for rejected translations will automatically send out source languages, forcing a full translation. [TS-8159]
The Translation Organizer service will during synchronization of the translation templates calculate which target languages should be shown in the Translation Job properties based on source language and translation template.
12 SDL LiveContent Architect 11.0 Release Notes New and changed
The Translation Organizer service relies heavy on the API layer of the parties it integrates. On the SDL LiveContent Architect side, we got a considerable performance boost by switching from the old-stack DocumentObj20 to the new-stack DocumentObj25 methods. This optimization boosts throughput of one service and makes it less likely that you need to scale out your services.
Generic Flow Starting the translation process ■ The Technical Writer releases objects in SDL LiveContent Architect ■ A Translation Coordinator creates a translation job. He specifies the source and target languages, and he selects a translation template.
Note: A Translation Template is the name for a project type defined in the target translation management system. A project type defines things like the source locale, default workflow and workflows for every target locale. When a user sends the translation job, the connector creates one or more projects using the specified project type.
■ The Translation Coordinator adds publications and/or other items to the translation job. ■ When the job is sent to translation; the Translation Coordinator clicks the button Send to translation and the connector takes over, and it automatically: ■ Creates the target stubs in SDL LiveContent Architect for the objects you selected (Technically this is push translations orchestrated by Translation Builder service), ■ Extracts the content from the objects in SDL LiveContent Architect, ■ Moves the objects into In translation status, and ■ Creates the target project(s) and uploads the files. Importing translated files At regular intervals, the connector queries the translation system for all files that are translated and are ready to be imported in SDL LiveContent Architect; the connector does not wait until all files in a Translation Job are translated. Every task is imported separately. The connector changes the status of the imported files to a Translated status so there is no need to do this manually anymore.
SDL LiveContent Architect 11.0 Release Notes 13 New and changed
Limitations ■ Currently, a translation job cannot be restarted. You must create a new translation job so that you can track it separately. ■ You cannot send draft files for translation. ■ You cannot delete projects in translation management system. You can only cancel or complete projects. Project are automatically cancelled in the translation management system if the user cancels a translation job in SDL LiveContent Architect.
Server Artifacts
A Windows service named Trisoft InfoShare#!#installtool:PROJECTSUFFIX#!# TranslationBuilder One will be installed on every system. The service runs TranslationBuilder. exe that processes the initial workflow part of our Translation Jobs which mostly consists out of Push Translation Management follow-up.
A Windows service named Trisoft InfoShare#!#installtool:PROJECTSUFFIX#!# TranslationOrganizer One will be installed on every system. The service runs TranslationOrganizer. exe that processes the synchronization part among the repository and translation management systems.
Configuration of multiple translation management system instances
The TranslationOrganizer. exe.config general settings were moved to a general level, and we switched to TimeSpan based configuration, allowing more detailed configuration compared to older parameters like jobPollingIntervalInHours.
The configuration currently allows one instance for each
14 SDL LiveContent Architect 11.0 Release Notes New and changed externalJobMaxTotalUncompressedSizeBytes="5242880" exportFolder="#!#installtool:DATAPATH#!#\Data#!#installt ool:PROJECTSUFFIX#!#\TranslationOrganizer\Export" />
To allow the service to do a synchronization on the translation templates we introduced an API function TranslationTemplate25. DeleteByTypeAndAlias and a general setting in the configuration file to completely disable this feature @synchronizeTemplates.
SDL TMS
We allow configuring the export of extra metadata part of the .MET files which will be submitted to SDL TMS. This is configured through a section like:
SDL LiveContent Architect 11.0 Release Notes 15 New and changed
To allow grouping by metadata in SDL TMS (similar to ContentCollector), we allow the following configuration for job name creation. This is a limited historical functionality that will result in job names like
File System
The user experience has improved for creating and exporting translation jobs; the number of clicks needed to export translation packages has been greatly reduced. Where users had to use the Translation Statistics Report to export files and had to repeat this process for every language, they now can create a Translation Job and select a number of languages all at once. Once the Translation Job is created, users can export the files that need to be translated to the file system of the SDL LiveContent Architect server.
The resulting .ZIP file contains a sub folder per target language. [TS-7623]
We allow configuring the export of extra metadata part of the .MET files to the file system. This is configured through a section like:
Restriction: The File System integration only allows exporting, there is no option for importing. For importing files, the same process as before apply like DITA2Trisoft, BatchImport, hotfolder customizations, etc.
16 SDL LiveContent Architect 11.0 Release Notes New and changed
SDL WorldServer
You can map language-locale pairs. This is needed because in SDL LiveContent Architect you may have 2-digit codes whereas SDL WorldServer codes such as fr-fr are used.
SDL WorldServer archives its project information on a (configurable) scheduled basis (e.g. 15-30 days), several customers do this every 1-2 days. This could mean that at some point the connector tries to retrieve a completed project that no longer exists. The connector will check for step TRANSLATED CONTENT RETRIEVAL. This is now handled as a cancel. [TS-4667] SDL WorldServer locales can now easily be retrieved by triggering a new command line option on TranslationOrganizer called --checkworldserver. For your convenience this can be simply triggered by executing StartCheckWorldServer. bat which will also verify your connection parameters specified in your .config file. [TS-6317]
Translation Templates with pipe (|) will synchronized and renamed to double hyphen (--) to avoid user interface problems. So a template named T | E | S | T will now show up as one valid value looking like T -- E -- S -- T. [TS-6910] The SDL WorldServer connector only accepts files in the source language; it does not support pre-translated files from SDL LiveContent Architect.
API changes
The web services API changes.
General
The web services API are made available for integration using the Windows Communication Foundation (WCF), resulting in SOAP 1.2 services like /InfoShareWS/WCF/API25/Application.svccapableofsupporting claims-based authentication. The deprecated endpoints like /InfoShareWS/ Application25. asmx relying on proprietary authentication are still present in this release.
Typically people write their first code based on a label (e.g. statusIn translation), if you want to change the label later on, you have to adapt a lot of code. Now all API25 methods accept element names (e.g. stable id for status VSTATUSINTRANSLATION) as input for parameters making code independent from label renames. This is valid for all ListOfValue based entries like for example: language, resolution, outputformat, user, usergroup, userrole, etc. [TS-6473] No API code will allow you to create logical identifiers holding a space in them. Historically this was also the case but typically enforced by your DTDs setup for the @id attribute. The DTDs blocked your creation through the VALIDATEDTD plugin. DatabaseUpgradeTool (DBUT) will do a prerequisite check by script ISH_CheckInvalidCharactersInLogicalIds. sql to make sure there a no legacy problems by upgrading to this release. [TS-2110]
SDL LiveContent Architect 11.0 Release Notes 17 New and changed
The retrieve functions of DocumentObj25 and PublicationOutput25 will no longer throw for unwell formed logical identifiers. So these group retrieval functions will either return you a result for well formed logical identifiers and will skip unexisting logical objects or not well formed entries (e.g. HTTP://...). [TS-8470]
The FISHSTATUSTYPE calculation is no longer done asynchronously, avoiding a lot of background task Translation Managements to spin up. The FISHSTATUSTYPE field holds short cut values to identify if your object is either draft (10), released (20), out-of-date (30), etc.
"Comma Space" (, ) is now allowed in string fields. With the changed back-end, the system can now easily make the difference between a multi-value field where comma-space is the separator and a regular string field. [TS-5104] Version algorithm, the build number system changed. We will now continuously increase the build number. For example version 10.0.312.5 has build number 312 and can be read as March 12 from the year 2013. Version 10.0.1629.5 has build number 1629 and can be read as 29 April 2014 (every multiple of 1200 indicates a year). [TS-6951]
DocumentObj25 and PublicationOutput25
The introduction of full stack write functions for classes DocumentObj25 and PublicationOutput25. These optimized versions got a considerable performance improvement because of the rewrite of the IOnDocStore system, now called IWrite plugins. We fine tuned several behaviors, most notably ■ When submitting a blob as non-administrator, you were blocked if the object was released. This is refined to if the object is part of a released publication output with the current language. ■ When updating the status, you must select a valid status transition. Furthermore if the object is part of a frozen baseline, you could not move from released back to a draft status. Now you can do this as long as the object is not part of a released publication output, making it easier to work statuses on translated objects.
All DocumentObj20, PublicationOutput20 and Publication20 functions are now deprecated. They still work and even with the internal redirection to the new stack, they also got a performance improvement. Customer specific function DocumentObj20. TerminologyUpdate is obsolete. ■ DocumentObj25.CheckIn and DocumentObj25.CheckInByIshLngRef (With RequiredCurrentState field allowing a metadata state check.) ■ DocumentObj25.CheckOut and DocumentObj25.CheckOutByIshLngRef (With RequiredCurrentState field allowing a metadata state check.) ■ DocumentObj25.Create ■ DocumentObj25.Delete and DocumentObj25.DeleteByIshLngRef ■ DocumentObj25.GetObject ■ DocumentObj25.SetMetadata, DocumentObj25.SetMetadataByIshLngRef and DocumentObj25.SetMetadataByIshLngRefs (Plural, multi field update that executes one transaction per object reporting back through logobject structure.)
18 SDL LiveContent Architect 11.0 Release Notes New and changed
■ DocumentObj25.TryGetMetadata (Allows a boolean check for object existence without a potential error being thrown.) ■ DocumentObj25.UndoCheckOut and DocumentObj25.UndoCheckOutByIshLngRef ■ DocumentObj25.Update and DocumentObj25.UpdateByIshLngRef
Dedicated work flow functions like Publish (FISHPUBSTATUS = VPUBSTATUSPUB- LISHPENDING), Cancel (FISHPUBSTATUS = VPUBSTATUSPUBLISHINGCAN- CELLED) and Release (FISHPUBSTATUS = VPUBSTATUSRELEASED and Baseline25.Freeze) are now handled by the generic SetMetadata update function. ■ PublicationOutput25.Create ■ PublicationOutput25.Delete and PublicationOutput25.DeleteByIshLngRef ■ PublicationOutput25.SetMetadata, PublicationOutput25.SetMetadataByIshLngRef and PublicationOutput25.SetMetadataByIshLngRefs (Plural, multi field update that executes one transaction per object reporting back through logobject structure.) ■ PublicationOutput25.TryGetMetadata (Allows a boolean check for object existence without a potential error being thrown.)
Function Publication20. Copy is obsolete and becomes a combination of Baseline25.Copy and PublicationOutput25. Create.
Baseline25
Some extra support functions where CleanUp will shrink your baseline entries down to the ones that are actually used by all publications that share this baseline. CleanUp does a very similar routine to a PublicationOutput25. Release which internally does a Baseline25.Freeze but without the labeling effort which essentially blocks further editing.
The CompleteBaselineByCandidateAndMode functions is a building block to support server-side autocompletion in publishing scenarios where you for example always want latest material or material that has been selected as Candidate for Baseline to be used. ■ Baseline25.CleanUp ■ Baseline25.CompleteBaselineByCandidateAndMode ■ Baseline25.CompleteReportByCandidateAndMode ■ Baseline25.Copy
Search25
A special heavy lifting server-side function that will allow you to do full-text-searches but get results limited to your current publication. ■ Search25.PerformSearchInPublication
SDL LiveContent Architect 11.0 Release Notes 19 New and changed
Folder25
The single object DocumentObj20 functions are now moved to multi object functions. It executes one transaction per object reporting back through logobject structure. ■ Folder25. AddShortcuts ■ Folder25. RemoveShortcuts ■ Folder25. MoveObjects
ListOfValues25
New function ListOfValues25. CreateValue2 allows to specify an LovValueId. This makes provisioning of list of value entries easier to keep in sync as you easier map the external id with the one in the repository. This function takes the same parameters as ListOfValues25. CreateValue, the latter is now deprecated. [TS-8466] As the List Of Values management code was migrated as well. We can now allow adding a numeric value like year '2013' which used to result in an error like The parameter label with value "2013" is invalid. The parameter ’label’ must contain at least one non-numeric character. [105001; InvalidParameter].
Restriction: Numeric values are not allowed yet on List Of Values that are linked to cards like users, user roles, user groups and output formats. The same goes for languages and resolutions. On all of these types the numeric value could potentially be interpreted as a card identifier.
ConditionManagement10
Function ConditionManagement. SearchInDocuments is obsolete.
Programmer's Interface Changes
Interfaces ICustomerFunction and IOnDocStore are replaced by IWrite*-plugins.
General
In previous releases, the IOnDocStore plugins were triggered every time you submit a file (blob) to the DocumentObj20 code base write methods. Typical implementations were all kinds of link extraction, DTD validation, anchor generation, etc. The ICustomerFunction was triggered upon certain configured status transitions (only field FSTATUS) in the DocumentObj20 code base. The main reasons for introducing a replacement is performance and to have full stack .NET, so no longer relying on COM+, opening up the integration triggers.
20 SDL LiveContent Architect 11.0 Release Notes New and changed
Important: None of the DocumentObj20 or DocumentObj25 will work with a XML Status Settingsstill set to version 1.0. We intentionally require this edit resulting in a version 2.0 state, because your previous configuration will no longer offer you the desired behavior.
We introduce IWriteMetadata and IWriteMetadataAndBlob plugins with extended functionality like: ■ IWriteMetadataAndBlob runs by definition on a full logical-version-language object as you need to define up to the file (blob) level. By default the plugin has access to the following fields: VERSION, DOC-LANGUAGE and FRESOLUTION. All other fields need to be specified explicitly in the plugin configuration. ■ IWriteMetadata plugins are executed when metadata is created or changed in any way. Any metadata change can trigger a plugin. ■ IWriteMetadata is also supported on Publications. Out of the box we offer all the necessary plugins with a configuration for OASIS DITA and our standard workflow behavior through files Admin.XMLWriteObjPluginConfig.xmland Admin.XMLStatusConfiguration. xml. On top we offer some extra plugins for very typical reconfigurations like OnFieldChangeSendStateTransitionEvent, OnFieldChangeSetDate, OnFieldChangeSendEvent, and OnFieldChangeCompare. See documentation for more information.
Just-In-Time Metadata based on OnFieldChangeCompare
OnFieldChangeCompare is a new plugin that triggers code based on any metadata field change. It allows for Just-In-Time (JIT) mandatory metadata through configuration. Typically you enforce mandatory metadata through the database configuration (TriDKXmlSetup). This option allows you to setup mandatory metadata through configuration. Consider an example where you don't know your Reviewer or Translator yet, but still you don't want your objects to get lost in workflow because an assignment was missing. The following configuration will not allow the status transition to proceed because FREVIEWER is still empty.
SDL LiveContent Architect 11.0 Release Notes 21 New and changed
Plugin Mappings
When you are upgrading to this version you have to check and reconfigure all your configurations. The new configuration file \ Websites\ Author\ EnterViaUI\ Admin.XMLWriteObjPluginConfig. xml should be submitted to XML Write Plug-In Settings. There is no automatic migration effort as you need to completely migrate your earlier XML Plug-In Settings and merge it with the status transition functionality configured through XML Status Settings. 1. Review your current XML Plug-In Settings typically maintained in file \ Websites\Author\EnterViaUI\Admin.XMLPluginConfig.xml holding your IOnDocStore configured plugins and map them on either IWriteMetadata and/or IWriteMetadataAndBlob in XML Write Plug-In Settings. 2. Split your XML Status Settings, where the actual workflow configuration remains in place, but the ICustomerFunction triggers on the FSTATUS field can now be handled by the generic metadata change trigger of IWriteMetadata. This configuration is typically maintained through \ Websites\ Author\ EnterViaUI\Admin.XMLStatusConfiguration.xml. 3. Note that several configurations actually mis-used the IOnDocStore system to achieve an metadata change behavior. For optimal performance, you should reconsider your custom plugins. 4. The newly generated configuration XML Write Plug-In Settings is typically maintained through Admin.XMLWriteObjPluginConfig. xml.
Restriction: XML Status Settings are no longer allowing @customerfunction. To force this incompatibility the root version number has been raised to 2.0.
The following plugins are supported through new standard components.
22 SDL LiveContent Architect 11.0 Release Notes New and changed
Table 1: The mapping from the obsolete IOnDocStore to the new system.
IOnDocStore IWrite CDocCnvTableConditions BlobCnvTableConditions CDocCompareValue BlobCompareValue CDocExtractConditions BlobExtractConditions CDocExtractDITAConrefs BlobExtractDITAConrefs CDocExtractHyperlinks BlobExtractHyperlinks CDocExtractMetaData BlobExtractMetadata cDocExtractXPath BlobExtractXPath CDocNormalizeDitaKeyrefs BlobNormalizeDitaKeyrefs CDocRemoveXMLNode BlobRemoveXmlNode CDocSetXMLNode BlobSetXmlNode CDocValidateDTD BlobValidate CSendEvent BlobSendEvent CWordCount BlobWordCount
The following plugins are supported through new standard components. Table 2: The mapping from the obsolete ICustomerFunction to the new system.
ICustomerFunction IWrite CSetDate OnFieldChangeSetDate CRaiseStatusChange OnFieldChangeSendEvent
The following plugins are obsolete without direct replacements: CBinaryToDOM, CDocCheckConditions, CDocCheckXPath, CDocCnvFeaturesToConditions, CDocConvertValue, CDocExists, CDocExtractDITAConditions, CDocExtractIdFrom- Path, CDocNormalizeWhiteSpace, CDocRemoveFeatures, CDocRemoveWhiteSpaces, CDocSetThumbnail, CDocXMLValidation, CDocXMLWhitespaceHandling, CDOMToBinary, CDuplicateContent, CHTTPRequest, and CSVGLinkExtraction.
Typical Server Installation Changes
Things that have changed on a single web/app server setup when using InstallTool (IT) or DatabaseUpgradeTool (DBUT).
Prerequisites
For exact versions we point you to the Install or Upgrade guide. But as quick start reminder.
SDL LiveContent Architect 11.0 Release Notes 23 New and changed
1. Operating System Programs and Features ■ We added an official statement that we only fully qualify on English Windows Server Operating Systems. [TS-7891] ■ By a one-time operation to open up permissions in %WINDIR%\ System32\ inetsrv\ config\ applicationHost. config, we can now easily overwrite server settings per web site and/or virtual directory through their web.config file. See “Configuring IIS applicationHost.Config”. This will move typical settings like
While installing or upgrading
InstallTool has native support for IIS 7.5 and 8.5, so no longer relying on “IIS6 Management Compatibility”. This version will not work on a system without IIS 7.5 or higher. In that case we advise you to use the InstallTool version you installed with.
InstallTool doesn't stop or start Windows service IISAdmin anymore.
By opening up applicationHost. Config we can enable Static and Dynamic Compression for regular HTTP and SOAP messaging calls out of the box. The end result of applying our typical installation steps will result in a system where WCF SOAP messages and DTD related files that are synchronized by Client Tools are now also compressed.
DatabaseUpgradeTool and InstallTool are like all server components raised to the .NET Framework version 4.5. There is no dependancy on .NET Framework 2.0/3.0/3.5 anymore.
Certificate queries based on a @findValue query using CN=... in the .config
24 SDL LiveContent Architect 11.0 Release Notes New and changed
configuration files only work if there is exactly one certificate in the store matching the query. This means that you cannot prepare for a certificate rollover process. To allow certificate preparation you have to make use of the thumbprint in configuration files. The initial value was set in every .config file by inputparameters. xml parameter called servicecertificatesubjectname. Value servicecertificate- subjectname is now replaced with servicecertificatethumbprint in inputparameters.xml. Starting from IIS 8.x, so Windows 2012R2, InstallTool will configure every Application Pool to be always alive which will shorten first requests to an idle server. The “Application Initialization Module” feature is also available on IIS 7.5, so Windows 2008R2, but requires manual execution of documented steps.
Post installation steps
After the install is complete, none of our Windows services (including Crawler, TrisoftSolrLucene,...) will start automatically The first reason is that the database is not guaranteed to be in the right state until you run DatabaseUpgradeTool (DBUT). Or in a multi server environment you don't want all your servers to pick up the same role. For your convenience on a single web/app server setup, we've provided a simple PowerShell script that will start and mark all services as Automatic. Execute \ App\ Setup\ Manage\Enable-DefaultServices.ps1asAdministrator. Post-installation task added for configuring the extension/mimetypes to compress
Verified Acrolynx on top of AuthoringBridge for XMetaL and oXygen
Verification of the integration among the mentioned components.
Verified that the JustSystems XMetaL 8 and 8J integrations SDL LiveContent Architect Authoring Bridge works together with Acrolinx. The XMetaL server-side files were enriched with statements needed by Acrolinx in the DTD-related macro files for XMetaL 8 and 8J. 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 3.2.0 build 1017 (client_XMetaLV3. 2_SR1_B1017. msi 3.2 SR1) to verify the behavior. [TS-8002]
Attention: JustSystems XMetaL 8.0.1.052 or higher is required, otherwise you might have disappearing menus in XMetaL. The XMetaL engineering team delivered a hot fix for this issue (rebuild of xmetal80.exe with install instructions) which can be applied on XMetaL 8 and 8J. In case of disappearing menus you can reset the editor's workspace by launching XMetaL one time with the Ctrl-key pressed.
Verified that the
SDL LiveContent Architect 11.0 Release Notes 25 New and changed
Note: We installed the Acrolinx plugin using the
Optimized Federated Services
The federated services and claims-based authentication system received improvements to reduce network traffic.
General
Several scripts are added to simplify your maintenance across server nodes. We advise you to take the scripts after installation as they will have the correct parameters already set, these can be found in: ■ ForMicrosoftADFS,in\App\Setup\STS\ADFS\Scripts. ■ ForInfoShareSTS,in\App\Setup\STS\InfoShareSTS\Scripts.
Out of the box for InfoShareSTS, our setup routines will add prefixes to the relying party configuration like Architect, Reach and Enrich. This prefix will be used in our basic claims set transformation, see \ Websites\ InfoShareSTS\ Configuration\ infoShareSTS. config so they are immediately ready to go.
Documentation
New topics that describe deployment guidelines and limitations of various setups. For example: ■ An explanation on front-end certificate usage (in for example Network Load Bal- ancing scenarios) and back-end (batch) certificate usage. ■ Security flows and scaling limitations of InfoShareSTS. Customers authenticating with on-premises Microsoft ADFSv2 STS can use a LiveContent installation deployed on SDL hosted servers outside their network. The services (web sites like InfoShareAuthor, InfoShareWS, Reach, Erich, etc) can be configured to accept a token from InfoShareSTS additional to the originally configured ADFSv2 one. This configuration removes the dependancy of delegated services or even background tasks to connect to your on-premises STS installation which is usually not accessible because of your company's firewall. All clients (browsers and client tools) running from the customers network have access to both ADFSv2 and LiveContent products. The solution is based on using the internal InfoShareSTS as the STS for all back-end initiated activities. This configuration removes the dependancy on the customer's ADFSv2. Out-of-the-box InfoShareSTS (IdentityServerV2) allows delegation with tokens that were issued only from itself. All back-end activated entities are redirected to use InfoShareSTS as their issuer instead of the customer's ADFSv2.
26 SDL LiveContent Architect 11.0 Release Notes New and changed
‘How to’ information can be found in the Information Portal documentation.
Reducing network traffic
Every HTTP request to our services (web client and web services) always put a big state description on the wire in the previous release (10.0.x). The state description was required to make any server act as a big calculator, or in essence making the whole system stateless. To avoid the state description's pay load to be communicated over-and-over again, we introduce a caching mechanism. In practice, also browsers and proxy servers could cause the application to fail with HTTP 400 - Bad Request, typically caused by an overload of cookies (typically aggregating to 16KB in size, a well known limit). It is actually your Secure Token Service (STS) - for example Microsoft ADFS or our backward compatible solution InfoShareSTS- that drives the size of the claim set, hence the FedAuth cookie by parameters like: ■ Token signing certificate strength and details (e.g. CN). ■ The number of claims packaged. ■ If delegation is setup, extra bootstrap information is added.
The Relying Party (RP) - for example InfoShareAuthor or InfoShareWS - will now take responsibility to store the bigger part of the claims set. When using a single-server setup you could choose to store it in memory which offers better performance, but if the hosting process dies (e.g. ApplicationPool) you have to redo the handshake. A persistence mechanism was added and allows to support multi server setups. Our RP's web.config are out of the box configured for a combination of a memory-cache and upon cache-miss a lookup in our database. 1. The identity model configuration states to use SequencedSessionSecurity- TokenCache as follows.
2. Our cache implementation will use the current in-process memory cache for quick lookup as specified through MruSessionSecurityTokenCache. If not found, IshSessionSecurityTokenRepositor will look up the session in our database (table ISH_SESSIONSECURITYTOKEN).
SDL LiveContent Architect 11.0 Release Notes 27 New and changed
Tip: The IshSessionSecurityTokenRepositor is not optimal but does offer what we need for basic NLB support. This system is created to allow full extensibility by other vendors. Anyone can configure or implement a specific provider for distributed caching services by either implementing one on .NET's SessionSecuri- tyTokenCache or by extending our Trisoft.Utilities.IdentityModel. Interfaces.ISessionSecurityTokenRepositor.
3. Outdated sessions that were persisted in the database are regularly cleaned up as part of the ISh_StandardInfoShareJob.
Background Task Introduction
Introducing the centralized Background Task system that replaces the decentralized Microsoft Message Queuing (MSMQ) system.
Attention: When upgrading an existing database, you should submit the Admin.XMLBackgroundTaskConfiguration. xml into the XML Background Task Settings before using the system.
Attention: None of the Windows services will be automatically started after an installation. This avoids blocked database upgrades when using DatabaseUpgradeTool (DBUT) and background task pickups with the wrong configuration.
General
By introducing the Background Task system, we offer a full replacement of the previously used Microsoft Message Queuing system (MSMQ). This means we no longer require: ■ InfoShareConfig. xml and its registry entry ConfigurationFile is fully obsolete and completely replaced by a central Xml Settings database driven con- figuration file. ■ Activators for the Trisoft-InfoShare-Author COM+ server application like \Applications\Maintenance\ RestartCOMTrisoftInfoShareApp\or\Applications\ Maintenance\ WakeUpIshComponents are no longer required.
28 SDL LiveContent Architect 11.0 Release Notes New and changed
■ QDispatcher is obsolete, as the new system relies on a centralized database queue. The old system relied on a decentralized per WebApp server with only forwarding capabilities through InfoShareConfig. xml. ■ Listeners on the Trisoft-InfoShare-Author, typically set to 3. This setting was always on the conservative side as 3 megapublish operations could make your server come to a halt. But because there was no message distinction 3 listeners for simple background tasks means that your server resources potentially were underutilized at times. Some features we introduce are: ■ Database centralized Xml Settings configuration (\ Websites\ Author\ EnterViaUI\Admin.XMLBackgroundTaskConfiguration.xml),so a single point of configuration. Through Windows environment variable settings, we still allow per server changes. On top you can set extra environment variables like installation paths in \ Applications\ BackgroundTask\ Bin\ BackgroundTask.exe.config. ■ Matrix based polling with maximum executions per message type, server or server role - if desired. By default we will restrict the number of publish operations to 2 in parallel, but we will at the same time also allow 2 translation management operations, a synchronize and 2 other (customer) types. So in this example up to 7 tasks are handled in parallel allowing various message types to make progress. Configuring the number of parallel executions protects the available server resources.
Note: The retry mechanism relies on the error handling of the background task handler. If the handler suppresses the exception or makes a new background task for handling the retry, there can be more or less attempts that configured.
■ Scalability and fairness based on the central database queue. ■ The basic principle is that a background task will be leased. This allows lease refreshes, lease time outs and hence recoveries without administrator interventions.
Flow
The service picks up a background task entry from the central database queue by leasing it. A lease consists out of marking a background task entry in the database with the identifiers of the service that picked up the task (LEASEDON and LEASEDBY). This execution gets @timeout time to successfully complete the task. If the task doesn't get marked as completed and unleased within this @timeout value; any other service having
All new code - like DocumentObj25 and PublicationOutput25 - will execute a database transaction per object to minimize lock times. This means that for example a group status transition of 89 objects could trigger 89 email notifications. To allow aggregation of these background tasks request we introduced an
SDL LiveContent Architect 11.0 Release Notes 29 New and changed
Suppose only 70 of the 89 objects were submitted, then a service having
Standard HashId functionality that allows skipping of outdated background task entries. For instance when a user saves a topic x times to the master repository, it will trigger an equal amount of synchronization attempts to the slave repository. In this case only the last synchronize matters and will be executed. The HashId is chosen by the handler implementation that puts the message in the background task system - typically a plugin will use the language card id.
Configuration
Every handler can be separately set per group per service role. So it is possible to create a service role Publish which only takes the handlers required for publishing. And use this service name on certain Background Task services to make them dedicated for publishing. Out of the box we configure a service with a role named Default that is configured to execute all types per service. You will notice the role value Default on the command line that starts up the Windows service. Every service role feature can be separately enabled through configuration flags like @leaseRecovery, @poller and @aggregationRecovery. This allows to set up service roles that specifically handle recovery or polling of publish operations only, because you only have publish software licenses available on some boxes.
Out of the box we configure a service with a role named Console. If you activate this after installation on the server through \ Applications\ BackgroundTask\ Configuration\ StartConsole. bat, the command line option specifies the @role to look up in the centralized configuration. By default this is set to Console. This special setup will only do one task at a time; and it is a good start to analyze misconfigurations.
Per handler like EXPORTFORPUBLICATION you can specify various dimensions like @isolationLevel or @timeout. When errors occur you can specify how many retries (@maximumRetries) are allowed, and you can also state if it should retry for specific error numbers or immediately fail. This allows future optimization scenarios like for example a system is down when receiving error number X, when X occurs retry the execution but with a @delay or just never retry anymore.
Remember: Any chained synchronous handler executions need to be explicitly configured. For EXPORTFORPUBLICATION we expect a
Server Artifacts
A new Windows service named Trisoft InfoShare#!#installtool:PROJECTSUFFIX#!# BackgroundTask One will be installed on every system. The service runs BackgroundTask. exe that processes background tasks requests. The service can trigger auxiliary BackgroundTaskIso. exe which will host isolated execution of background task requests.
30 SDL LiveContent Architect 11.0 Release Notes New and changed
The number of COM+ applications visible in Component Services has been reduced from 3 to 2. Trisoft-InfoShare-Author no longer triggers MSMQ listeners. Trisoft-InfoShare-AuthorIso changed from a server to library application. Trisoft-InfoShare-AuthorGrp has been removed.
Light Weight Media Manager Integration
All user interfaces are validated to show external video and sound resources.
The preview of our Client Tools and Web Client are capable of showing video and sound streams.
Many of those streams only have basic version control. A suggestion to achieve some more control on this is by introducing a DITA Library per stream holding links like:
Submitting this Library topic to the repository will augment the xml with @id attributes th rough plugin GENERATE.LINK.ENDS. This allows you to @conref to the
Restriction: For the preview to work you need to point to https:// URLs. Furthermore the SSL certificate used should be a publicly recognized one, and not a self-signed or coming from a private certificate authority. In the later case the GeckoFX-based preview in the Client Tools will reject the certificate.
Restriction: We verified our example output formats to make sure they render something (e.g. thumbprint image of the video). Also the supported xml editors were tested to make sure they accept these external media.
Content Quality Rules Integration
Increasing quality of what you write from the very start thanks to this integration.
We introduce an integration with our SDL Content Quality Rules engine (SDL Enrich). The configuration is single sourced in Settings > Default Settings. The integration will become visible in SDL LiveContent Create.
SDL LiveContent Architect 11.0 Release Notes 31 New and changed
32 SDL LiveContent Architect 11.0 Release Notes Chapter 2 Fixed issues
Issues that were fixed from SDL LiveContent Architect are described.
Fixed Issues in version 11.0.0
The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0.
If you are upgrading from a release prior to SDL LiveContent Architect 10.0.0 refer to the release notes for the versions between. For your convenience, what is new and changed for SDL LiveContent Architect versions 10.0.1, 10.0.2, 10.0.3, 10.0.4 and 10.0.5 are included in this document.
Fixed Issues in 11.0.0 Web Client
The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0.
Web Client ■ The Repository lower-right pane holding version and language information has reference information to identify which object's version are currently displayed. This should avoid confusing when a user continues navigation in the top-right object lists. Below the lower button bar you'll see a Versions of... line. [TS-8032] ■ List views have been fine-tuned to do top-alignment, and use more word wrapping to allow more information to be readable on a screen. [TS-8606] ■ Packaged SDL LiveContent Create 5.2.0 which essentially fixes the Google Chrome 35 raising the message Cannot read property ’ownerDocument’ of undefined. [TS-8300|XO-2514|SRQ-1629] ■ Properties don't select the previously saved EDT value in the drop down, instead the first value is selected. [TS-7955|SRQ-1183] ■ Legacy publish option on version level was broken for maps/topics/libs. [TS-7886|SRQ-1224] ■ Preview of Image/Other binary types where the mime type is not recognized by the browser should result in a download with a proper filename. Depending on the
SDL LiveContent Architect 11.0 Release Notes 33 Fixed issues
browser brand and version an extra window will remain open holding the message Loading preview... If the format is not supported by your browser a download will be initiated. that requires manual closing afterwards. [TS-8127|TS-8128|SRQ-1379] ■ SDL LiveContent Reach 6.0.5/6.0.7 extensions for mobile support needed alignment within the preview. The isMobile method was added to the SCTServiceWrapper. [TS-8249] ■ The comparison preview based on the ChangeTracker component sorted the available versions by text (e.g. 9, 8, 7, 6, 5, 4, 3, 2, 10, 1.1.1, 1) instead of smarter version sorting. Furthermore the same text comparison was used to indicate what the newer and older version was, which reflects itself in which stretches of text were marked as inserted or removed. [TS-8033|TS-8146|TS-8215|TS-8214| TS-8166|SRQ-1529] ■ The comparison preview for none working language objects resulted in a compare between the working and non-working language versions. So for example when English (en) was your working language and you requested a Dutch (nl) compare; you would actually be comparing v2 nl with v1 en. [TS-8253|TS-8252] ■ Navigating preview hyperlinks always opens in the Foundation-cached user language (typically English) instead of the selected topic language like images. As an English user, opening a French topic preview will try to render with French images. But navigating the hyperlinks in this topic will always render the UserLanguage version of the hyperlinked object. It will not respect your initial French language selection.[TS-8125|TS-8126|SRQ-1492] ■ Workflow.asp contains a spelling error. We corrected Library topcs to Library topics. [TS-8164|SRQ-1546] ■ Clicking on a link in the preview that points to an object that does not exists gives 500 Object reference not set. [TS-8136|TS-8130] ■ Hyperlinks to Other types (e.g. Word, PDF, etc) don't work in Internet Explorer 8 preview. [TS-8123|TS-8124|SRQ-1486] ■ Internet Explorer 8 Preview fails with JQuery error when data holds empty cells. The empty cells used to be filled with
34 SDL LiveContent Architect 11.0 Release Notes Fixed issues
whitespace properly. So an Edit operation in the web xml editor could cause intentional whitespace to disappear. [TS-8337|TS-8283|XO-2523] ■ SDL LiveContent Create can now be configured with a Tags On View layout. It is possible to add a tagsonviewxsl configuration parameter in the web.config. [TS-8218|TS-8217|SRQ-1214] ■ Preview styling was adapted to align with the other components. [TS-7279] ■ Restructured the search panels to use the better matching UI controls. [TS-7348] ■ The browser cookie InfoShare is not refreshed when you are forced to re-login on InfoShareSTS. After 7 days you'll get the message Error: 401 ErrorLoadingRoles, blocking the application. [TS-6809] ■ Added a single point of configuration for the Enrich Server Uri in the Settings page (field FISHENRICHURI). [TS-7268] ■ In an Assist window, the selected values are always sorted and cannot be reordered for fields where order matters. [TS-7280|TS-7266] ■ A user with too many user groups (e.g. 160) cannot login as the cookie size makes Microsoft Internet Explorer loop indefinitely. The user groups are no longer cached in the cookie. [TS-6915|TS-6498] ■ Event Log no longer has scrolling column headers and buttons. Out of the box the EventId column was added and EventType was removed. Furthermore the Refresh option on the details will automatically scroll you down to the bottom of the list again. [TS-6592|TS-6119] ■ Event Log visually shows the active filter like Show Recent. [TS-7434] ■ Search Results should have a select all checkbox like the inbox so that you can export the search results of one page. [TS-6869] ■ Ability to delete multiple objects from the inbox and result list. Do note that all rules for a single object delete have to be met. [TS-6741] ■ Translation job management always shows progress in green. When a job fails or has warning, matching color codes will be used. [TS-7356|TS-7314] ■ Reports using options Referenced topics and images overview is now also available for Library topics. [TS-7462|TS-7536] ■ By a MetadataConfig. xml configuration change we now allow editing of the FISHUSERDISPLAYNAME in the user properties dialog. By default this field was matched with the USERNAME field but could not be edited afterwards. It is the FISHUSERDISPLAYNAME which is used in the web client welcome screen when using InfoShareSTS or an external STS like Microsoft ADFSv2. [TS-7556| TS-7528] ■ Adding a user in the Settings area will no longer auto-fill the user name field. [TS-7379|TS-7399] ■ Remember me reminds the user on the InfoShareSTS with a cookie. So even if you close the browser and come back (within 12 hours by default), the InfoShareSTS will remember you. This is considered an annoying feature for
SDL LiveContent Architect 11.0 Release Notes 35 Fixed issues
advanced users that log out to re-login with different credentials as we cannot provide a multi application log-out button. To avoid confusion, we chose to remove the option. [TS-6524] ■ The username of the InfoShareSTS log in screen will now be trimmed. Note that any user names with leading or trailing spaces need to be corrected by an administrator to avoid confusion. [TS-6343] ■ Added a Copy Link to Clipboard capability to get to the logical ids of publication object types. [TS-6742|TS-6681] ■ Web Client and Client Tools are now aligned to both request for 5000 search results, to reduce differences in search results presented by SolrLucene. [TS-7690|TS-7692] ■ Bread crumbs does not get updated when doing a "Go to location". [TS-7662| TS-7650] ■ Google Chrome opens a new tab when selecting Start import. Google Chrome no longer has this issue starting from v33 but we applied a workaround for the older versions of the browser. [TS-7570|TS-7576] ■ In Mozilla Firefox you cannot open the context editor for a publication version or map. It opens in a new tab and not in a new window. After the context is saved the value is not set because the selected context is not passed to the properties window. [TS-7277|TS-7212] ■ On Microsoft Internet Explorer 10 (IE10) the date picker in the Search tab immediately hides after it was opened. [TS-6323] ■ When expanding node in repository tree view the focus is set to the top. [TS-6631] ■ Microsoft Internet Explorer 8 downloads SVG and SWF files even when the right plug-ins are installed. [TS-7539|TS-7436] ■ List of statuses becomes empty if new status with quotation mark was added. The application will now block the creation of statuses and inboxes with a single quote. [TS-7538|TS-7439|TS-7448] ■ Thumbnails view not working if selected folder contains a '.' (dot) in it's name. The Thumbnail view is now sorted by logical title. [TS-7075|TS-4885] ■ In a publication report, it is currently not possible to compare all branches and versions. You can only compare within your branch. You need to be able to see what changes have been made to the branch as compared to the version from which the branch was made, or to any other branch. We now allow comparison with lower versions and branches. We chose to not allow all combinations as that can be very confusing as you would see a lot of removed contents instead of added contents. [TS-6812] ■ When previewing revisions in the web client, the drop down at the top potentially has extra revisions as it shows the status transition revisions (without blob change) as well. [TS-6195] ■ Availability of a /comments/ debug page to allow debugging of the commenting integration. [TS-7406] ■ Packaged the files PreviewExternal. asp, PreviewExternalTest.
36 SDL LiveContent Architect 11.0 Release Notes Fixed issues
asp and PreviewExternalTest. xml to allow easier setup of an external preview virtual directory. See SRQ-758. [TS-7365] ■ Various refresh scenarios were tweaked, like folder list views. [TS-7652] ■ Various preview layout issues like selection of rendered inline/block elements. [TS-7633|TS-7631] ■ Various visibility improvements like list views showing long titles or changes information. [TS-6680] ■ Web Clients and Client Tools configuration should both no longer show FPUBWATERMARK as this is not a system field and there is no behavior attached to this value. [TS-6868] ■ The Web Client's top tab row didn't load properly since the update to Chrome 30.0.1599.101 m. [TS-7143] ■ Can't delete shortcut to an object when there is a # character in the name of the folder. [TS-6283] ■ After deletion of an object with a # character in the folder name, you saw %23 instead of # in the deleting objects pop-up. [TS-6390] ■ Clicking from one JQuery calendar control to another, in for example Search tab, causes Internet Explorer to hang (100% CPU usage of iexplore.exe) because of too many resize events. [TS-6296] ■ Checkbox include watermark (FPUBWATERMARK) should be removed in the web client; it was removed in the client tools in a previous release since watermark requires customer specific integration. This change makes the client and web consistent. [TS-6272] ■ Cannot assign the Owner field to a Shortcut folder in the web client. [TS-6271] ■ BatchImport didn't show any error messages anymore when hovering over an error image. The mouse over event now shows the error message again. [TS-6535] ■ Filling in a 'wrong' or 'misspelled' user in the BatchImport screen resulted in a generic error Unexpected failure: Overflow, instead of the actual wrong value. [TS-6794] ■ When publishing, the title bar of the of publish (pop-up) window says cancelling a publication. [TS-6815] ■ Preview in ShowHistory fails for illustrations. [TS-5444] ■ Translation Management Dialog; Mandatory Fields message shows field name instead of field label. [TS-3012] ■ Web client Search > Object Fragments option has been removed. Use the xml-aware full text search instead, which provides a faster, better paged result set.
Tip: If desired, the deprecated Web Client Search > Object Fragments can be re-enabled in the configuration xml file, SearchMenuBar. xml. [TS-6169]
SDL LiveContent Architect 11.0 Release Notes 37 Fixed issues
Preview ■ Printing a topic from the preview failed to print the complete topic if the preview contains scrollbars in Internet Explorer, Chrome, FireFox and Publication Manager. The print from the Publication Manager only printed a portion of the preview. We will have the Client Tools preview working with one limitation/known issue however. The Print Dialog to select a printer will be skipped (print.always_ print_silent to true) and you will immediately print to your Operating System's default printer. The green suggestion is to have a PDF printer set as your default printer. Later on you can still print what you want from the generated PDF. In the next major release we will re-introduce the Print Dialog again (print.always_ print_silent to false) as we will upgrade the third-party Gecko component. [TS-7082] ■ Conditions on a table column are shifted to the right. [TS-7219] ■ When doing a ChangeTracker Compare preview with a lower version in the web client, the markup for inserts/deletes is reversed. [TS-6245] ■ When previewing reltables that have an empty relcell element, the cells shifted to the left. [TS-6248] ■ The broken image icon was no longer rendered in Client Tools. The previous renderer was Internet Explorer based which does show broken image icons by default. The new renderer is GeckoFX based (same as FireFox) which by default doesn't show broken image icons. [TS-6280] ■ Table shows empty column for selection when it is not possible to select a bookmark, conref, and so on. If there is a table in a topic, a column is added to each row in the preview. This column is used for selecting a row to use as a bookmark/conref/... This column should not be showed when it is a regular preview without selection possibilities. [TS-6284] ■ A topic with invalid conref/conrefend attribute blocks preview. In Publication Manager the error message Begin and end id require to be in the same document when a bookmark is given occurs in when in the Browse repository window. When adding a map file to the existing publication, the error message The version cannot be selected. Begin and end id require to be in the same document when a bookmark is given occurs. [TS-6766] ■ Doing a compare on a large topic with many images freezes Chrome. [TS-6464]
38 SDL LiveContent Architect 11.0 Release Notes Fixed issues
External Preview ■ The external preview is an end point that allows external systems - typically translation management systems - to submit their processed version of an xml file for previewing. The end point will take care of doing basic xml handling (@class attributes) and render the referenced images. ■ This new refactored version complies with our Single Sign On (SSO) technology stack and no longer requires a separate web site. It consists out of an IIS HttpModule called ExternalPreviewModule which is not enabled out of the box. The necessary web.config configuration entries specify the user profile to use. Any request to this end point will make use of the specified profile, even when that user was already authenticated. [TS-2455]
Fixed Issues in 11.0.0 Client Tools
The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0.
Client Tools and Xml ■ A CheckOut on a Released object in the select previous version dialog should suggest creating a new version/branch and not stop with a message box stating Checking out the object ’title v. x - language’ failed. The object ... is released.. [TS-6921|SRQ-558|SRQ-2198] ■ Long Description makes text run out of dialog of Condition Builder. [TS-6565| SRQ-397] ■ Any preview with resolving features historically resolved @conref first when an element has a @conref and @varref attribute set. The order is now corrected to match the publishing chain where @varref is always resolved before DITA-OT's @conref. [TS-8406] ■ Out of the box every client tools' .config file is configured to hold
SDL LiveContent Architect 11.0 Release Notes 39 Fixed issues
a redirect to your STS to re-login; this would recover your preview in your Client Tool session. This was however broken by a web.config configuration change introduced in 10.0.4. [TS-8330|TS-8331] ■ Inline comments on images do not align correctly. Corrected through CSS change. [TS-8304|TS-8263] ■ Using a username with the @ symbol like an email address failed. Reason was that the authentication dialog is reused for all kinds of authentication: basic (e.g. admin/admin), Windows (e.g. GLOBAL\myuser/mypassword), proxy,... In case of Windows authentication the dialog needs to split the username from the domain. Knowing that there are two styles for specifying Windows accounts: NTAccountName (NT4-style) like GLOBAL\myuser where the back slash is the splitter; and UPN (User Principal Name) like [email protected] where @ is the splitter. For now as the UPN-style is less often used, we will not parse for the domain anymore using the @ as splitter. This will allow using @ in user names, which essentially allows email addresses as user names. [TS-8212| TS-8213|SRQ-1710] ■ Conref support was added for:
In this case, an empty item (Choose an option) is added to the pull down list, and set as default value. And, (*) is appended to the label. [TS-6263|TS-6795] ■ Add Account window has http:// in the address as an example but this should be https://. [TS-6170] ■ The Last Modified On field (FISHLASTMODIFIEDON) introduced in 10.0.1 is now configured consistently in the Client Tools where possible in metadataconfig. xml. The modification date shown in Inbox, Search screen and results, property dialogs all show the last modification date of the attached file. In the past the MODIFIED-ON field was used which display the last change of the card and not the attached file. [TS-5821|TS-6839] ■ Reusable Element is available from the menu but not supported. [TS-4673] ■ New xml documents not having conditional text, the user now sees
40 SDL LiveContent Architect 11.0 Release Notes Fixed issues
■ When some content in your publication version contains @conref range constructions, the operation returned a Freeze Baseline Report’ reading ’Error: <ʜ> [TS-5083] ■ Legacy xml documents containing conditional text are rendered by Adobe FrameMaker respecting the available conditional text. If you want to remove the conditional text, open the checked-out xml document located in your Local Storage in an ascii editor (for example, NotePad) to edit the processing instructions. [TS-5283] ■ Preview in browse dialog uses working resolution EDT instead of preview resolution EDT, which blocks preview in some combinations. [TS-5468] If the options settings of an account is set to use one image resolution as working resolution and another to preview the content, this only worked when the source format resolution contained a EDT value which can be previewed. ■ Images can be marked to be valid for multiple languages allowing easier publication compilation in Publication Manager when working with multiple source languages. The LanguageApplicability concept is now by default enabled in the delivered metadataconfig. xml. The configuration shows the language field (DOC-LANGUAGE) on images as a multi value field. [TS-6732]
Publication Manager ■ The version list view doesn't refresh when a publication version was deleted. It shows an entry holding a version number but without metadata populated because that object doesn't exist anymore. [TS-8531|SRQ-1867] ■ Creating a version in the version selection control of Publication Manager could result in a KeyNotFoundException. [TS-7414|SRQ-1867] ■ Requesting a Publish on multiple publication outputs fails with “Collection was modified; enumeration operation may not execute” if you switch application focus (e.g. ALT-TAB). [TS-6838] ■ Pressing Ctrl+F in preview of a Where Used results in 2 search dialogs. [TS-6545|SRQ-399] ■ Publication > Save As shows incorrect button text on warning message for folder with unsupported type. [TS-7635] ■ Add Folder warning contains Apply To All checkbox. [TS-7588] ■ Preview confirmation message is shown twice when size limit is exceeded showing messages like "The object you are about to preview exceeds the maximum defined size limit. Loading the preview could take several minutes. Do you wish to continue?" and/or "Loading the preview could take several minutes. Do you wish to continue?". [TS-7586|TS-7608] ■ Message to re-open application after options or account changes is shown twice. [TS-7578|TS-7609] ■ Preview shows 500 internal server error when the account's default language was set to a language (e.g. de) which was unavailable in the repository for the object you are trying to preview. The server-side preview code made default
SDL LiveContent Architect 11.0 Release Notes 41 Fixed issues
language assumptions. We now pass all information required for commenting from the client. [TS-7521|TS-7467|TS-7545] ■ Conditions on a table column are not displayed properly in the preview. [TS-6932] ■ TemplateSpecification. xml has duplicate @ids forLINK-DITA-TABLELIST and LINK-DITA-TOC and figure list. [TS-7459| TS-7540] ■ A user with too many user groups (e.g. 160) cannot login as the cookie size is too big, blocking the preview. [TS-6538] ■ Paste Special does not copy correct baseline. Auto-complete does not work properly when using Paste Special with option Structure and baseline information. When no version is available for an object in the baseline, the baseline is auto-completed after insertion of the object, and before the copied baseline information is handled. Therefor, a question can be raised (when version in copied baseline information is different from the auto-completed version) to overwrite the version. This question is not expected. [TS-7628|TS-7637] ■ XPP ErrorHandling was improved. When a failure happened in the Acrobat Distiller you didn't got this information in Event Monitor of the publish [TS-7745] ■ Lock was not being released and it blocked other client tools with the following message "The configuration file 'C:\Users\username\AppData\Local\Trisoft\ InfoShare Client\x.y\Trisoft.PublicationManager.config' could not be saved. The process cannot access the file because it is being used by another process." Some configuration files and the local storage are shared between different client tools. To prevent too much interference a system-wide mutex is used to synchronize the client tools. When running client tools in parallel (for example, Publication Manager and XMetaL) a lock was not released which blocked the other client tools from using the local storage or configuration files until the lock-owning client tool closed. [TS-7048] ■ When cancelling check out repeatedly a .NET framework errors was triggered wit message “An item with the same key has already been added”. [TS-6996| TS-7202] ■ Performance was optimized when loading the tree view in Publication Manager. Resolving references doesn't go to the root node anymore but stops at the first recognized fully-expanded common parent node. Also handling circular references was checked to make sure that there weren't any issues. [TS-7090|TS-7152] ■ Recursive auto-completion is now avoided when adding a master (map). When a master is added an auto-completion is started. When the version of a node within the master is changed, it happens that a second auto-completion is started, hence, a lot of unnecessary web-service calls are executed. This is not needed in this case, because the first auto-completion handles it. [TS-7091] ■ The View XML context menu item was missing when using an SDL LiveContent Architect without an integration with SDL LiveContent Reach. This is now restored in the main preview. [TS-6920] ■ Manage Comments functionality in Publication Manager restored. [TS-6918] ■ Documentation enriched with "Search for content" topic holding more advanced search syntax. [TS-5665]
42 SDL LiveContent Architect 11.0 Release Notes Fixed issues
■ Exception Cross-thread operation not valid. is raised; this occurred when a writeable copy of the topic still exists in local storage but a more recent copy has been checked in to the repository. [TS-6512] ■ Comments not showing in Publication Manager because of language mismatch like for example: SDL LiveContent Architect language specified as en-us and SDL LiveContent Reach specified it as: en-US. The comments widget now calls a Reach check_lang function to normalize the language identifier. [TS-6435] ■ Close window on a jump list does not work when using the Windows clipboard outside of the application (e.g. copy and paste operation of a file in Windows Explorer). [TS-6178] ■ When triggering a Publish on a PublicationOutput you could get a Usage of field "CHECKED-OUT" during a "READ" action is not allowed. error. [TS-6514] ■ When changing the version of a topic in the version widget while the preview was still being loaded could result in a ArgumentOutOfRangeException error. This occurs more often on slower or more remote Web/App servers. [TS-6582| TS-6161] ■ When an item in the Baseline tab has focus, a refresh (F5) in Publication Manager refreshes the Baseline and Content tab. Also a refresh (F5), having focus on an item in the tree view of the Content tab, keeps the Baseline tab in sync. When refreshing from the Content tab, a newly added Master/DITA-Map was inserted in the tree for each refresh request. An extra confirmation text was added to explain the requirement for a Save before Refresh (F5). [TS-5360|TS-5368] ■ A Publication Manager refresh (F5) on the Output tab doesn't pick up new items [TS-5303] ■ When checking out an image that has multiple values set as language, Publication Manager responds with error "The language and/or resolution is not available". [TS-5016|TS-5307] ■ A new created map version is not displaying in the list of versions after refreshing (multiuser action). [TS-5466] ■ The option to compare a publication version with itself causes a failure in the publishing services [TS-2511]
SDL LiveContent Architect 11.0 Release Notes 43 Fixed issues
■ No preview available for EPS, WMF and TIFF files [TS-4247] File format preview is not supported in Publication Manager: EPS, WMF and TIFF. File format preview that is supported in Publication Manager: SVG, JPG, PNG, GIF, BMP, SWF, 3DXML ■ The Modified On field of the language level typically rendered in the client tools shows the last modification date - through the MODIFIED-ON field - done to any field of that card. This includes user and system fields, and blob changes. System fields like FISHSTATUSTYPE - which enumerates for every language card if it is currently the highest Draft or Released version for speedier autocomplete operations - is maintained through a background task run of Translation Management. In practice, whenever a content object reaches the Released state, Translation Management is triggered which updates the system fields of this and the prior version. For the user this meant that the 'Modified On' date changed of the prior version without having touched it. Note that the audit trail through Revision History is still showing the correct dates. Similar to the 'Last Modified By' field (FISHLASTMODIDIFIEDBY) which indicates the user who did the last write operation on the attached blob; we now introduce 'Last Modified On' field (FISHLASTMODIFIEDON). The field is initialized with the MODIFIED-ON date through a DatabaseUpgradeTool run. All client tools are configured to show the FISHLASTMODIFIEDON field under the existing 'Modified On' label through metadataconfig.xml configuration. [TS-4803]
DITA2Trisoft ■ When importing DITA documents @href value on
44 SDL LiveContent Architect 11.0 Release Notes Fixed issues
■ Catalog is not used during conversion. [TS-4971|TS-4191] ■ When you have a data set with a large number of nested folders it leads to long file paths. When this happens user may get an error message that the path is too long although this is not really the case. [TS-5447|TS-5000] ■ Hangs when saving the file; All conversions are done, but it hangs when saving the file map. No error is displayed. There are errors in the log file. [TS-4972| TS-4285] ■ Importing does not work (Filemap is missing) [TS-2169] ■ Finish button exists the application during a running import. [TS-4975|TS-4838] ■ The value of xml:lang="en" attribute is empty after importing from the commandline. [TS-5520|TS-5524] ■ An error message "startIndex cannot be larger than length of string." appears after conversion [TS-5477] ■ Application renames nested folder [TS-5480] ■ Re-GUID-ize option. You can now import topics that were exported from SDL LiveContent Architect and re-import them with new GUIDs. [TS-4976] ■ Command-line options: DITA2Trisoft can be run unattended if started from the command line. When done this way, no user interaction is required. [TS-4974] ■ Some characters are stripped from the TITLE metadata [TS-4973|TS-4351] ■ The icon of the link to PDF documentation on the desktop should match to application installed for reading PDF files. [TS-2750]
Fixed Issues in 11.0.0 Editors
The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0.
SDL LiveContent Create ■ The Save and CheckIn endpoints did not respect the preserve whitespace option. So any intentional whitespace was lost when editing with SDL LiveContent Reach. [TS-8283] ■ Users can browse folders to which they do not have read access during insertion of xref, image, conref. Note that they could not actually see and use the selected object if they didn't have the correct access rights. [TS-6033] ■ The Change Tracker feature has limitations and therefor out of the box, this feature will be disabled. [TS-7974] ■ Create doesn't display images with LanguageApplicability (multiple languages) set. Images can have multiple values in the Language field. This feature allows the user to work with multiple source languages and still see the images in the preview and during editing, however the application errors with a message that the language and/or resolution is not available and displays a red X. [TS-4867] ■ Conref selection fails when the setup is using a virtual directory name which
SDL LiveContent Architect 11.0 Release Notes 45 Fixed issues
differs from the application name causing CSS stylesheet locations to be miscalculated. The $host was set to AuthorWebsite. As such, the base url is derived from $url.base, which is populated from the
General AuthoringBridge ■ Inserting a @varref to a branched version @varid crashes with “Object reference not set to an instance of an object.” if the @varid no longer exists in the latest version. When editing out of context of a publication, any editor will try to resolve referenced content based on the LatestVersion principle. In this scenario, the resolving will fail without a error. [TS-8132|SRQ-1513]
JustSystems XMetaL ■ Inserting a within a 46 SDL LiveContent Architect 11.0 Release Notes Fixed issues ■ Inserting a variable that contains a space in the name resulted in No element was selected. Please select an element.. [TS-7895|SRQ-1220] ■ Clicking Cancel on message box showing The document is not valid. If you save, the file will contain invalid markup. will loose all your edit changes. From now on a Cancel will bring you back to editing mode. [TS-8023|SRQ-1313] ■ Close button on 'Configure Key Space Manager' cannot be clicked because the 'Configure Key Space Manager' doesn't get activated. This typically happens after the synchronize. A similar scenario is when you ALT-TAB away from the xml editor during a Check In operation with Keep Checked Out selected. When trying to close the xml editor in this state it would typically respond with The application can’t shut itself down completely because an unknown script is still running. Please shutdown the application by using the Task Manager.. [TS-7850|TS-7243] ■ XMetaL will show the value of an @ishcondition attribute that contains the following special characters ", <, >, & in the Tags On View and Normal View with their corresponding XML character entities ", <, >, &. Note that all other characters should not be shown as XML character entities. For example the following @ishcondition value Department=’R&D’ and version > 3.1.1 will show up as Department= ’R&D’ and version > 3.1.1. If a condition value contains a space, the @ishcondition will look like this ishcondition="GREETING=’Hello World’", so single quotes were added to keep the value together. If the condition value contains a space AND a single quote ('), the @ishcondition will look like this ishcondition="GREET- ING=’Hello Wayne"s World’", so single quotes were added to keep the value together and the single quote is converted to a double quote. [TS-8083|TS-8004| SRQ-1342] ■ DTD validation error because the catalog file is missing in the My documents folder. [TS-7213] ■ Attempts to insert topicref via JustSystems XMetaL map editor result in "No origin document found" error. It worked using the editor view. Now both are working. [TS-7178] ■ When using the xml preserved tokens (<, > and &) as condition operator in the @ishcondition attribute you got an exception. Conditions of Version type can't use Greater than option. Setting a condition using Version errors with the message that the document is invalid when using the option Up to not including. [TS-6755] SDL LiveContent Architect 11.0 Release Notes 47 Fixed issues Adobe FrameMaker ■ AuthoringBridge for Adobe FrameMaker 9/10: Inserting a hazardSymbol element, errors: Element ’ hazardsymbol ’ is not valid for content model ’(messagepanel +, hazardsymbol*)’ [ TS-5107|TS-2166] ■ AuthoringBridge for Adobe FrameMaker 9: adapted references so that the DITA 1.1 structapps files are no longer referring to Adobe FrameMaker 10 file. [ TS-4824] ■ AuthoringBridge for Adobe FrameMaker 9/10: The debug logging was re-enabled. [TS-4826] ■ Adobe FrameMaker 9/10 bridge - Inserting metadata and indexterm elements breaks the structured view sometimes resulting in a crash. Conditional text tags are not automatically added to prolog elements anymore, and for the same reason, conditional text tag DITA-Comment is not added to draft-comment elements. ■ When working in Adobe FrameMaker then opening a topic in another editor, colspec element results in changes and loss of data [TS-5260] 48 SDL LiveContent Architect 11.0 Release Notes Fixed issues Arbortext Editor ■ Arbortext Editor 6.0 issue when synchronizing files, the file catalog-extensions. xml exists in the general DocTypes folder and the specific one for Arbortext Editor. Because both are present the synchronize dialog stays visible when doing round robin between the Authoring Bridge and Publication Manager. [TS-7458|TS-7457] ■ When editing a big xml file (>512KB) in Arbortext Editor 6.0 the save operation which is triggered implicitly triggered within actions like a Checkin caused the application to crash with a Exception has been thrown by the target of an invocation. or a editor.exe: segment violation (signal 11). Tweaking of the undo-all and save action in Arbortext's ACL code avoids the issue, delivered in the AuthoringBridge installer. [TS-6850] ■ In Arbortext Editor 5.4 with the SDL LiveContent Architect client tools installed, when checking out a module with multiple conrefs, performance degradation is noticed. AuthoringBridge for Arbortext Editor 5.4 triggered a single conref resolving refresh for every conref link present in the document for simple editor actions. The editor does not respond when this happens. It can take up to 60 seconds before the editor can be used again. [TS-4750] ■ Arbortext Editor 6: The conref attribute was removed from the Modify Attributes dialog when you have an SDL LiveContent Architect document opened in the Arbortext Editor 6. Users must use the menu item, SDL LiveContent > Conref > Insert Conref, to insert a conref or a conref range in their document. Fixed Issues in 11.0.0 Web/App/Db Server The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0. API ■ DocumentObj25.RetrieveMetadata fails with "An unexpected system failure occurred. The combination of field, level and operator must be unique". We now allow up to 9999 filters on the same combination. [TS-4850] ■ InfoShareWS AppPool crashes with a An unhandled exception occurred and the process was terminated. because of a Object reference not set to an instance of an object. in BaseErrorHandler.LogException. This issue was about adapting the code to no longer crash the AppPool, and potentially log the originating out-of-bound exception. [TS-8046|SRQ-1395] ■ Baseline25.wcf.CompleteReportByMode cannot auto-complete an image having multiple languages. This was caused by ISHBaselineReport_Out being to strict and not allowing the reportLanguage to be multi value as required by images relying on language applicability. [TS-7790|TS-7167] ■ Developing, the exception classes from API20 and API25 over WCF were missing user info like Publishing ■ Whitespace missing when conditionalized 50 SDL LiveContent Architect 11.0 Release Notes Fixed issues ■ Publishing ended unexpectedly when empty hrefs were encountered. [TS-3367] ■ Support internal cross references in combination with DITA's copy-to attribute. One of the steps in preparing the DITA content for DITA-OT is replacing the GUIDS with filenames, this corrupted the internal defined cross-references in files which had been copied to other filenames. [TS-4849] ■ When something goes wrong during the publishing process (XML data error, Style sheet error, ...) and publishing fails, the same process may be restarted which results in a looping publication job. The job keeps running, consuming resources and affecting other jobs. [TS-5251] ■ Extended ServiceReferences UpdateContent, UpdateMetadata and UpdateProduct- Definition with filename overloads to allow ChangeTracking Compare when publishing to SDL LiveContent Reach. This allows customization to step away from the previously hardcoded filename generation in the Trisoft.Utilities.ServiceReferences assembly functions. [TS-6073] Restriction: Publishing with ChangeTracking Compare is not possible on a Reach for reviewing instance where the Architect-Reach synchronization is active. This change allows to enable ChangeTracking Compare on a downstream Reach for content delivery instances - where the Architect-Reach synchronization is not active. ■ The transtype ishhtmlhelp was added to support non-Western languages CHM generation (e.g. Japanese). To generate non-Western chm files, configure the DITA-OT transformation type of the CHM (Compiled Help) output format to use ishhtmlhelp instead of htmlhelp. Note: When using the ishhtmlhelp transformation type to generate CHM files, searching in the generated CHM file may not work properly if you search for words with special (non-ASCII) characters. This is a limitation of the Compiled Help format. [TS-5973] ■ The field, FISHKEEPFIXEDATTRIBUTES, was added to improve publishing performance. In the user interface this is seen as a new checkbox, Keep default attributes, on the output format. This option, when checked, means that the attributes which have fixed defaults in DTD are added to the XML file when they are exported during publishing. This results in the DTD not needing to be loaded again, since the needed attributes are in the XML document at publish time. SDL LiveContent Architect 11.0 Release Notes 51 Fixed issues Translation Builder and Organizer ■ Translation Organizer service table ISH_TRANSJOBITEM has columns ISHTYPE and EDT that are inconsistent in length and collation. [TS-7389|TS-7367|TS-7388| TS-7300] ■ TranslationOrganizer diagnostics improved for template retrieval allowing to trace every retrieved template, every template with/without a mapped source language, every target language (not) mapped. [TS-7222] ■ TranslationOrganizer used to print out the locale information and not the language information. This is changed now and you will see the language information when triggering StartCheckWorldServer. bat. [TS-7223] ■ Documentation received an update on the flexibility of status transitions for TranslationOrganiser. [TS-7112] ■ Translation Jobs holding a publication skipped all children of an item if that item is not available in the requested language(s). Now any target language topics are added to the translation job even if for example the parent map still isn't released in its source language. [TS-6652] ■ Translation Job Properties drop down for Worldserver Translation Templates appears to be empty, but really isn't. Box is empty but if you go through you see different values but no text. Initially there should only be one empty item in the templates drop down (if no source language selected). When selecting a source language for which there are templates, they should appear in the templates drop down. If there are no templates for a source language, there is also just one empty item shown in the templates drop down. [TS-6824] ■ All World Server Project Types were retrieved as translation template. This is now corrected to retrieve only the Project Types that are visible for the configured connecting World Server user. [TS-6754] Installing and Upgrading ■ InstallTool (IT) asks for a username/password combination for every inputparameters. xml file having a 52 SDL LiveContent Architect 11.0 Release Notes Fixed issues InfoShare object information... Cards: 330012 [deleted:21 max:387837 sequence:387837] LogicalObjects: 76773 [deleted:7] VersionObjects: 79971 [deleted:7] ContentObjects: 83372 [deleted:7] Publications: 16 [deleted:0] PublicationsVersions: 53 [deleted:0] PublicationOutputs: 84 [deleted:0] Baselines: 53 [deleted:0] Users: 144 [deleted:0] Blobs: 89114 [max:126243 sequence:126245] ■ Normalize the Issuer's certificate thumbprint. When generating the thumbprint of a certificate often the user copies the start of the value from the user interface. This results in a string in notepad that has an invalid character that notepad isn't displaying (Notepad2 and Notepad++ show this as ?) which results in an invalid certificate. [TS-5696] Database ■ Verified the Standard Edition of Microsoft SQLServer 2012 AlwaysOn Failover Cluster. [TS-8185] ■ Database locking strategy for card locking functions like DocumentObj25 revisited. The earlier 4 attempts with a random wait time between 1 and 10 seconds is now fine tuned to 10 attempts with a random wait time between 500ms (00:00:00.500) and 2000ms (00:00:02.000). The three values can be further tuned by Trisoft_InfoShare_ObjectLockRetries, Trisoft_InfoShare_ ObjectLockWaitTimeMinMilliseconds and Trisoft_InfoShare_Ob- jectLockWaitTimeMaxMilliseconds expressed in TimeSpan syntax. [TS-7561] ■ Oracle job to cleanup unused blobs/pages in ALL_PAGES table only removes 1 blob per execution. To correct the legacy, Database Upgrade Tool (DBUT) will run a script named DBUT_CleanupUnreferencedBlobs.[TS-7969] ■ The job for Oracle logs in the system_message table. The sp_jobClean was tuned to remove message older than 1 year to keep this table under control. [TS-7890] ■ The job for SQL Server databases will run faster. An update statistics of a table containing a varbinary column (e.g. all_pages) takes quite some time. The FullAnalyze. sql has been tweaked to only do full analyzes on tables that don't hold BLOBs. [TS-8009|TS-7959] ■ The Microsoft SQLServer database job triggered by SQL Server Agent is called InfoShareJob. It used to consist out of several steps, and editing the steps required system administrator rights. The job will now contain only one step pointing to stored procedure ISHCore_TrisoftInfoShareJob with a set of optional parameters. The optional parameters allow us to extend the default behavior without requiring a manual system administrator intervention. Out of the box, our job will only do minimal maintenance like rebuilding indexes with SDL LiveContent Architect 11.0 Release Notes 53 Fixed issues more than 10% fragmentation and update statistics without full scan. The name of the job has been matched up in Oracle RDBMs as well for consistency reasons. [TS-6866] ■ Enhancement to Oracle 11g: Increased cache size to improve performance (db_16k_cache_size, db_block_size) [TS-5462] ■ A new language-card-level field FISHLASTMODIFIEDON was added which automatically stores the date of the last modification to a document. The field is initialized with the MODIFIED-ON date when the DatabaseUpgradeTool is run. All client tools are configured to show the FISHLASTMODIFIEDON field under the existing Modified On label through metadataconfig.xml configuration. This resolves the issue [TS-4803] whereby when a user did an autocomplete of the baseline with latest released versions, both the selected version and the previously released version got the same timestamp (when the autocomplete was done). Change Tracker - Compare ■ Publish with compare fails in ChangeTracker with End tag 'p' does not match the start tag 'fn' (0xC00CE56D/-1072896659) [TS-8425|TS-7237|TS-8587| SRQ-1825] ■ ChangeTracking of a map results in 'There was an error formatting the content. Root element is missing.' while the web client compare works. The Secure Token Service - Authentication and Authorization ■ Certificate update assistance script added to allow updating of relying parties on AD FS v2 and InfoShareSTS like \ Setup\ STS\ InfoShareSTS\ Scripts\ SDL.LiveContent. Architect-InfoShareSTS-RP-UpdateCertificate. ps1 and \ Setup\STS\ADFS\Scripts\SDL.LiveContent. Architect-ADFSv2.0-RP-UpdateCertificate.ps1.[TS-7991| TS-7992] ■ Log in attempts on InfoShareSTS where the username or password contains special characters like &é"’(§è!çà)- failed. [TS-7311] ■ InfoShareSTS has been enriched with basic transformation types based on the relying party prefix. This way the FISHUSERDISPLAYNAME field is added to the claims set for SDL LiveContent Reach and SDL Enrich; and all applications can show the same display name when using InfoShareSTS. [TS-7555|TS-7554] ■ Version numbered the InfoShareSTS internal database files .sdf with a compatibility number. This way when upgrading the just-in-time initialization 54 SDL LiveContent Architect 11.0 Release Notes Fixed issues will work and the typical upgrade scenario will work out of the box. Any extra configuration like relying parties need to be redone anyway for incompatible database files. [TS-7634|TS-7625] ■ The InfoShareSTS is now ready to generate tokens for the Suite by having the claims transformations in place based on the relying party name which is either prefixed with Reach or Enrich. Also the InfoShareSTS scripts for adding a relying party (SDL.LiveContent. Architect-InfoShareSTS-RP-AddRelyingParty. ps1) or a node from a batch server (SDL.LiveContent. Architect-InfoShareSTS-RP-AddNode. ps1) have been adapted and areavailablein\App\Setup\STS\InfoShareSTS\Scripts\.[TS-6863] ■ The updated InfoShareSTS has received documentation to attempt the following cloud setup: a customer with an on-premises ADFSv2 instance wants to use a LiveContent installation deployed on cloud-based servers outside of their network. All web clients and client tools running from the customers network have access to both their on-premises ADFSv2 and the hosted LiveContent services. The LiveContent services can trust the ADFSv2 as an issuer through certificate thumbprint configuration. The back-end server-to-server communication among LiveContent services can however not contact the on-premises ADFSv2 setup, so they have to be routed differently. The end result is user authentication in the web client and client tools based on your Windows account. [TS-6893] SDL LiveContent Reach ■ Publishing to SDL LiveContent Reach with a publication title holding characters \/:*?’"<>|&+#.% failed. These characters will now be removed before upload. [TS-8231|SRQ-1587|SRQ-1540] ■ SDL LiveContent Reach introduced an extra call pub.xql?action= prepare_allowed that allows to verify if a scheduled backup is about to start. If so the client code can decide to postpone any write operations. Client code that has been adapted is in publishing (PowerShell scripts), background task synchronizing (PowerShell scripts) and even the browser sync (javascript) when doing a Finish Editing from SDL LiveContent Create. [TS-8460] ■ Publish to SDL LiveContent Reach through Powershell hangs when multiple publishes to SDL LiveContent Reach are running simultaneously. The three-part fix consists out of splitting the logging into a log file per Powershell process based on the process id (e.g. Trisoft.FeedSDLLiveContent. pid1628.log). Making sure that all log writers were closed. And avoiding a Microsoft problem by calling Powershell using extra parameters -inputformat none -outputformat none -file. [TS-7391|TS-7441] ■ Synchronize to SDL LiveContent Reach fails for images having multiple languages (also known as LanguageApplicability) assigned to them. The algorithm would check for language en, de which results in an error like Invalid Language Code. You must use a valid language code such as "en" or "en-GB". [TS-7670|TS-7671] SDL LiveContent Architect 11.0 Release Notes 55 Fixed issues ■ Publishing a publication to LiveContent Reach with Unicode characters in the description field results in errors like Exception while transforming node: Illegal HTML character: decimal 128. The complete support of Unicode also requires a Reach fix identified as LCD-3623. [TS-6952|LCD-3623] ■ SynchronizeToLiveContent events stay at busy state if the topic does not exist in SDL LiveContent Reach. By default the system does multiple synchronize attempts when the configured Reach system is 'temporarily' unavailable; if you don't want synchronize attempts, you should clean the LiveContent url in the Settings area and disable the OnDocStore plugin. [TS-5604] Other ■ Component Trisoft.Utilities.ServiceReferences. dll has option to override certificate validation through certificateValidationOverride which will now allow logging mismatches. [TS-8307|TS-8279] ■ Version algorithm, the build number system changed. We will now continuously increase the build number. For example version 10.0.312.5 has build number 312 and can be read as March 12 from the year 2013. Version 10.0.1629.5 has build number 1629 and can be read as where every multiple of 1200 indicates a year, so this build was created on 29 April 2014. [TS-6951] ■ JustSystems XMetaL 8 (8.0-CRCL) and JustSystems XMetaL 8 J (8.0-J-CRCL) are added to the server to support single-sourced configuration of the matching AuthoringBridge through synchronization. The matching ClientConfig. xml was extended and also received a new condition name ClientEdition to distinct the regular with the Japanese xml editor as their file name nor version differs. ■ Japanese Search has been enhanced regarding word separation and whitespace usage. Overall Japanese doesn't rely on whitespace for word breaking. In several scenarios Japanese search terms were passed as quoted terms to the search engine resulting in no tokenization and hence less search results. The quoting rules were reviewed and we also added support for the double byte characters for our search operators (e.g. AND, OR,...) and their surrounding whitespace. [TS-6439|TS-6240] Fixed Issues in 11.0.0 Documentation The following issues are fixed in version 11.0.0 of SDL LiveContent Architect compared to 10.0.0. ■ Condition name and value restrictions were opened up, but not corrected in documentation. Corrections available in topics “ Adding a condition name”, “Adding a condition value” and “ Conditions”. [TS-8599] ■ Outdated statement on autocomplete is corrected in topic “ Auto-completing the baseline”. [TS-8020|SRQ-1351] ■ Syntax to search for @ishcondition is incorrect in topic “Search for content”. [TS-8057] 56 SDL LiveContent Architect 11.0 Release Notes Fixed issues ■ InstallGuide - issuerwsfederationendpointurl contains wrong http url. Replaced /wsissue/ with /issue/. [TS-8582] ■ Fix wrong Xml string in WCF web services samples. [TS-7852] ■ Adapted the topic “Modifying the SETTITLE plugin”, typically a project setup question on what legacy import through DITA2Trisoft should do with titles. [TS-8265] ■ Several 32-bit aware registry paths were listed in the documentation without the Wow6432Node segment. For example HKLM\ SOFTWARE\ Trisoft\ TriDK\ TriDKApp\ InfoShareAuthor\ LogLevel was corrected to HKLM\ SOFTWARE\Wow6432Node\Trisoft\TriDK\TriDKApp\ InfoShareAuthor\LogLevel.[TS-7753|SRQ-1393] ■ An official statement about fully qualifying on an English Windows Server Operating System is added. [TS-7891|TS-7764|SRQ-1103] ■ WCF samples or Microsoft ADFS 2.0 mention wrong binding name WS2007FederationHttpBinding_Application which should be CustomBinding_Application or CustomBinding_Application1. [TS-7532|TS-7417] ■ Added missing PublicationOutput statuses Cancelled and Released. [TS-7611] ■ Folder name restrictions are refined. [TS-7593|TS-7565] ■ Since 10.0.0 the deprecation list is gone, this is now added to the release notes again. [TS-7224] ■ Added legal notices and acknowledgments to all publications. [TS-7442] ■ Primary/Batch server deployment guidelines graphically explained. [TS-7408| TS-7295] ■ Security Token Service protocol requirements graphically explained. [TS-7407| TS-7294] ■ Garbled characters where seen when submitting a topic through the web client when installed on a Japanese operating system. Documentation needed for Windows Server OS Requirements to fix issues with Japanese Windows. Refer to the installation and/or upgrade guide, topic Establishing a dedicated system user with formatting information located under Software and hardware requirements" > Microsoft Windows Server for information. [TS-6102] ■ The developing example Using .SVC Web Service in C# for InfoShareSTS referred to 'Microsoft .NET FrameWork 3.5' while this should minimally be 'Microsoft .NET FrameWork 4.0. [TS-3884] ■ Prerequisites section of Install and Upgrade guide have extra information regarding certificates. [TS-6518] SDL LiveContent Architect 11.0 Release Notes 57 Fixed issues ■ The topics in the PDF for SDL LiveContent Architect under Developing > Classes is missing information and in some cases, the table is formatted with an extra column. [TS-3884] ■ For the developers we've added a lab that shows you how to use JAVAto consume our claims-enabled WCF-based web services. You can find it on the CD in folder \__Resources\Code\.[TS-5989] 58 SDL LiveContent Architect 11.0 Release Notes Chapter 3 Known Issues The following are known issues in this version. Web/App/DB Servers ■ We strongly advise to redirect your custom integration to DocumentObj25/ PublicationOutput25 instead of using deprecated classes DocumentObj20/Publication20/PublicationOutput20. When throughput is important you might receive time out errors on the 2.0 code base with error looking like: Trisoft.InfoShare.API25.InfoShareException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. If you mix this up with 2.5 code, 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 for this is that the COM+ based 2.0 calls force Serializable on the transaction potentially making all calls wait. This problem is resolved when you switch your custom code to the 2.5 API calls; this is also what we did for all of our clients (e.g. Publication Manager, AuthoringBridge, DITA2Trisoft, etc). [TS-8739] ■ Failed transactions block any further update on locked content objects (Docu- mentObj) or publication outputs (PublicationOutput) requiring manual actions to roll back the transaction. The following characteristics identify the problem: ■ ORA-01591: lock held by in-doubt distributed transaction trans_id or ORA-02049: time-out: distributed transaction waiting for lock in the log files. ■ The Microsoft Component Services panel holds entries marked with (only failed to notify) in the Distributed Transaction Coordinator > Local DTC > Transaction List. For example ISAuthor.CPublicationOutput (only failed to notify) or ISAuthor.CDocument (only failed to notify). All environments having this problem have the Oracle password expiration options set for our designated database user - typically isource. Usually near expiration time you'll see the messages appear like ORA-28001: the password has expired or ORA-28002: the password will expire SDL LiveContent Architect 11.0 Release Notes 59 Known Issues 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 (like 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; although it was actually 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] ■ Upgrading from SDL Trisoft 3.8.X to SDL LiveContent Architect 10.0.X using an Oracle 10 database can cause problems with the isource.i script. The difference between scripts is: revoke ALTER USER from ISOURCE / revoke CREATE USER from ISOURCE / revoke DROP USER from ISOURCE / GRANT CREATE SYNONYM TO ISOURCE / GRANT CREATE JOB TO ISOURCE/ Note: Oracle support of version 10.2.0.5 ended July 2013. ■ At installation time, it is important to note for InfoShareSTS usage that hostname, baseurl and localservicehostname can not be the same. It is not allowed to have the same value in the hostname of baseurl and localservicehostname. InfoShareSTS fails because it creates two sets of relying parties with same identifier. [TS-4693] 60 SDL LiveContent Architect 11.0 Release Notes Known Issues ■ The automated shut down of the Trisoft-InfoShare-AuthorIso failed application sometimes results in Invalid syntax. You may ignore this message. ■ Renaming languages in settings area will not adapt @xml:lang and language combinations [TS-6472]. 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: ■ When changing the label of the language, the existing files in that language are not automatically adapted therefore they 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 would have to resubmit each file. ■ The publication outputs that have a language combination containing the modified language become invalid and must be recreated. 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 SDL LiveContent Architect 11.0 Release Notes 61 Known Issues Client Tools ■ You cannot connect with a second user to the same data source if the first user was already connected to the same data source. You can have two accounts, so two usernames, pointing to the same repository. You just cannot be connected at the same time. Switching accounts requires a client tools restart. [TS-8656] ■ When using the 62 SDL LiveContent Architect 11.0 Release Notes Known Issues ■ Translations to Japanese are missing: [TS-4696] ■ Search options in the find dialog; match case, search up, match whole word ■ cut/copy/paste in the standard toolbar ■ Search > Advanced options; searching on a version is always done on AllVersions [TS-4222] ■ Only references to DITA topics and DITA maps are supported. References to images and other formats (for example, PDF, DOC) are not properly supported or not supported at all. [TS-5731] ■ Although Microsoft Windows 8 is not supported for the SDL LiveContent Architect Client Tools, Microsoft .NET Framework 3.5 Features must be enabled on your system before installation. [TS-6428] ■ In ServiceReferences there is no check about the ability of a user to enter the application. So the authentication works but Architect or Reach might still block authorization by a ProfileMismatchException. [TS-4292] ■ Client Tools using SSL might crash when using a Url that doesn’t match the certificate. [TS-571] ■ Client Tools cannot handle Architect accounts that contain a slash (/) or back slash (\) because it confuses them while handling other authentication requests coming from Secure Token Services or Proxies that potentially require NTLM/Windows authentication. [TS-8312] ■ When using a secured proxy, the client tools browser component could popup an extra authentication dialog. [TS-4680] ■ Avoid opening multiple instances of editors (so there is only one process of the editor running) to prevent possible locking of files in the profile folder of the Gecko renderer component. [TS-4682] ■ Where Used Report [TS-7037] known issues. When doing a where used on an object in the client tools, beware that the shown publications are determined by performing a PublicationOutput25.Containing API method which means: ■ The PublicationOutput25. Containing first calculates the baselines in which the logical object is present (see Baseline.Containing). These baselines are used to retrieve the publication versions (see PublicationOutput. UsingBaseline). Consequently, when the baseline is shared between multiple publications, the result can contain publications in which the topic is not used. ■ Selecting a specific version of a map forces version selection for all referenced topics. Changing the version of a map can give less referenced topics, but those topics could still be in the baseline. This can result in publications shown in the report where the topic is no longer used. ■ If a library contains @conrefs with illustrations or links to other topics, all referenced objects will be returned as part of the publication, even if they are not used. SDL LiveContent Architect 11.0 Release Notes 63 Known Issues ■ 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: 64 SDL LiveContent Architect 11.0 Release Notes Known Issues ■ Local Publish with a Topic/task etc. which has an xref inside does not work. [TS-5182|TS-5184] ■ The Page Preview view is not supported (may not work). [TS-5526] ■ Page Preview error null is null or not an object when xref topic contains unresolved references. [TS-4438] ■ Do remember that like in SDL LiveContent Architect 2013 when installing the Authoring Bridge for XMetaL on Windows Vista/7 machines you have to have full access to folders C:\Program Files (x86)\Common Files\XMetaL Shared and C:\Program Files (x86)\XMetaL 6.0 before doing the installation. ■ Starting from version 10.0.3 we support XMetaL version 8 in English and Japanese. However when inserting an image you will experience that the @width and @height attributes are persisted potentially causing roundtripping problems if your image resolutions/renditions vary in dimensions. This issue is communicated to JustSystems. [TS-7120] ■ XMetaL will show the value of an ishcondition attribute that contains the following special characters ", <, >, & in the Tags On View and Normal View with their corresponding XML character entities ", <, >, &. Note that all other characters should not be shown as XML character entities. For example the following ishcondition value: Department=’R&D’ and version > 3.1.1 will show up as: Department=’R&D’ and version > 3.1.1. [TS-8004] ■ Inserting a @conref to a multimedia object is not always resolved corrected. Either it shows you the object twice or it shows a blue outlined diamond. [TS-8458|TS-8663] SDL LiveContent Architect 11.0 Release Notes 65 Known Issues SDL LiveContent Create ■ Selecting a range of contiguous conref targets is not supported in SDL LiveContent Create. [LCDE-385|LCD-2229] Publication Manager ■ When a conref is made to an image in the same topic, an erroneous message is displayed for circular references: Warning: The object 66 SDL LiveContent Architect 11.0 Release Notes Known Issues Web Client ■ You can create a logical id with spaces however when you try to use a template to create the initial document, it errors. For example: The object "JIRA TS 2031" contains invalid XML. 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 block usage of spaces in identifiers. [TS-2110] ■ Sort on Inbox items not correct; uppercased letters come before lowercased ones which is the typically ASCII sort based on their numerical (not alpha) representation. [TS-2933] ■ New Slide-Out Navigation pane and Dashboard page is not supported in Microsoft Internet Explorer 8 (IE8) and earlier. ■ Actions triggered through the web client don't allow to update baseline entries. A web client triggered will reuse any existing baseline and trigger 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 as at no point in time the baseline received version entries. [TS-8633] Preview ■ Web client preview of SVGZ results in an XML parsing error. The XML parsing error is caused by the mimetype. The mimetype for both SVGZ is text/xml+svg. The text/xml portion of the mimetype 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] ■ WMF and TIFF files are not displayed in the preview. They cannot be rendered by any client tool or the web client. Other ■ When conrefing a glossentry which is part of a glossgroup topic, a glossentry is created with an incorrect value in the conref attribute. Publish warns that there is an unresolvable conref during publish because the conref value is incorrect. [TS-4630] Note: glossentry is derived from topic so, the conref value should be the same as when you conref a complete topic. Instead of creating a conref with topicid#topicid/ elementid, it should be topicid#elementid SDL LiveContent Architect 11.0 Release Notes 67 Known Issues 68 SDL LiveContent Architect 11.0 Release Notes Chapter 4 Deprecated, Obsolete and Restrictions The following issues are deprecated , obsolete or restricted in SDL LiveContent Architect. Generally, SDL provides platform support for up to two versions of any given platform to provide more flexibility in how organizations incorporate vendor changes. Typically, SDL provides support for the latest and previous version of a third party platform. This previous version is implicitly marked as deprecated. Since SDL LiveContent Architect 2014 (11.0.X) ■ The legacy option to have Translation Management correct the status of all previous versions if a later version was released has been removed. This option was already deprecated since the introduction of the FISHSTATUSTYPE field. The option Default Settings > Enable out of date has been removed. ■ The following software components are marked as deprecated in this release: ■ Microsoft Windows 2008R2/x64 (all service packs) ■ Adobe FrameMaker 9.0 and 10.0 ■ Arbortext Editor 5.4 ■ The following software components are obsolete and not supported in this release: ■ Microsoft SQLServer 2005 (all service packs) ■ Microsoft SQLServer 2008 (all service packs) ■ Oracle RDBMs 10.2.x (all versions) as Oracle Extended Support ends as of July 2013 ■ Microsoft Windows XP (all service packs) as Microsoft Extended Support ends as of April 8, 2014 ■ Microsoft Windows Vista (all service packs) ■ JustSystems XMetaL 6.0/6.0J ■ JustSystems XMetaL 7.0 ■ SDL LiveContent Architect 11.0 Release Notes 69 Deprecated, Obsolete and Restrictions ■ Arbortext Editor 5.3 ■ Microsoft Internet Explorer 8 Since SDL LiveContent Architect 2013 (10.0.X) ■ Reusable Objects are marked as deprecated, Support will be removed from the code base. Please contact SDL Support to discuss your usage and legacy conversion. [TS-4673] ■ Index Terms are Obsolete [TS-1232] ■ Limited Batch Metadata Operations [TS-768] ■ It is not possible to use a comma space inside single value fields.SDL LiveContent Architect tries to insert multiple values into a single value field. ■ Client Tools using SSL might crash when using a Url that does not match the certificate ■ Authoring Bridge for XMetaL on Windows Vista/7 machines you have to have full access to folders "C:\Program Files (x86)\Common Files\XMetaL Shared" and "C:\Program Files (x86)\XMetaL 6.0" before doing the installation. Since SDL Trisoft 2011R2 (9.2.X) ■ Usage of single/ double quotes in list of values like Statuses, UserGroups and UserRoles could lead to unexpected results in the Web Client. [TS-466] ■ Object-level Access Control is not supported. Security settings can only be set on the folder level, not on the object level. ■ Size of fields is limited by the relevant data type in the database: ■ Long: unrestricted ■ Text: restricted to a length of 1333 bytes and will not allow ', ' (comma-separated) values. Since SDL Trisoft 2011 (9.0.X) or older ■ "Pre-release" Translation Management is not included in this release ■ No URN support for identifying metadata ■ Export for publication ■ Notification in the user interface if the set is not approved. This because multiple languages can be exported, and each of those can have a different status. ■ Update packages. ■ Recursive inheritance of metadata to lower levels other than labeling is not possible. ■ Pre-Translation only on document component with XML as electronic Document Type (EDT). 70 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions Software compatibility for previous releases Information about third party or client software is packaged, configured and tested for a specific software version release. Version Overview The following table — available for informational purposes only — indicates: ■ The SDL LiveContent Architect client tools versions which should be used against a certain release of the server side components. ■ The Third Party software which is configured or integrated inside a certain release of the server side components. ■ The Third Party software such as operating systems, databases, and runtimes with which we use to conduct quality assurance testing for the server side components . Attention: Exact versions indicate a version with which we did regression testing; these are usually also available for download. Note that other versions may work but are not quality assured. If a problem is encountered we only accept the issue if it is reproducible on the listed versions. Note: SDL LiveContent Architect is qualified on an English version of our supported operating systems only. Other languages of these operational systems are not used for quality check purposes. Restriction: The relation between the Authoring Bridge and the xml editors is not defined in this table. Installation packages for Authoring Bridge are not always available for all xml editors. CAUTION: For the most up-to-date information you should always verify the latest installation documentation. There are other requirements than the ones listed below. SDL LiveContent Architect 11.0 Release Notes 71 Deprecated, Obsolete and Restrictions Note: The names, trademarks, designs, logos, service marks, intellectual property, etc. of the products shown are exclusive property of their respective owners. Terminology used: ■ S: is short for Supported which means that the software was used, configured or integrated in the version. ■ -: means that there is no information available for this combination. Usually because one of them was not around yet during the mentioned era or because it is simply not a supported combination anymore. ■ D: is short for Deprecated which means the software was used/configured or integrated in the version; but you are strongly advised to not use this combination anymore. ■ P: is short for Planned which means the software is not ready to support the combination but will be in the future. Usually the other product was not released in time for our release. Depending on the impact we must postpone support for the combination until the next major release. Note: SDL Trisoft refers to previous, historical releases of SDL LiveContent Architect. SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... SDL Trisoft Publication Manager S----- 3.2.x SDL Trisoft Publication Manager -S---- 3.3.x SDL Trisoft Publication Manager --S--- 9.1.x SDL Trisoft Publication Manager ---S-- 9.3.x SDL LiveContent Architect ----S- Publication Manager 10.1.x SDL LiveContent Architect -----S Publication Manager 11.1.x SDL Trisoft Authoring Bridge S----- 3.2.x SDL Trisoft Authoring Bridge -S---- 3.3.x SDL Trisoft Authoring Bridge --S--- 9.1.x 72 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... SDL Trisoft Authoring Bridge ---S-- 9.3.x SDL LiveContent Architect ----S- Authoring Bridge 10.1.x SDL LiveContent Architect -----S Authoring Bridge 11.1.x Microsoft Windows XP S S S S D - Microsoft Windows Vista - S S S D - Microsoft Windows 7 - - - - S S Microsoft Windows 8 - - - - - S PTC Arbortext Editor 5.1 support D----- files PTC Arbortext Editor 5.2 support ------files PTC Arbortext Editor 5.3 support SSD D D - files Only Only Only OASIS OASIS OASIS DITA DITA DITA 1.1 1.1 1.1 sup- sup- sup- port. port. port. PTC Arbortext Editor 5.4 support -P SSDD files PTC Arbor- text an- nounced Arbor- text 5.4 for the second quarter of 2009. SDL LiveContent Architect 11.0 Release Notes 73 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... PTC Arbortext Editor 6.0 support ----S S files Sup- Note port that 6.0 added doesn't in support 10.0.1 various for DITA Arbor- 1.2 text fea- Editor tures 6.0 like M060. keyref Note or that 6.0 conref doesn't ranges. support various DITA 1.2 fea- tures like keyref or conref ranges. PTC Arbortext Editor 6.1 support ------files JustSystems XMetaL 5.0 support D----- files 74 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... JustSystems XMetaL 5.1 support S S ---- files Full Full Full support for the Authoring support support Bridge 3.2.1 for JustSystems for the for the XMetaL 5.1.0/5.1.1 provides full Au- Au- CMS Connector support. XMetaL thoring thoring does require a connector hotfix Bridge Bridge (crclcore_patch.mcr, 3.2.1 3.2.1 dd.20080505) and InfoShare 3.7.1 for for or higher. Just- Just- Sys- Sys- tems tems XMet- XMet- aL aL 5.1.0/5. 5.1.0/5. 1.1 1.1 pro- pro- vides vides full full CMS CMS Con- Con- nector nector sup- sup- port. port. XMet- XMet- aL aL does does require require a a con- con- nector nector hotfix hotfix (crcl- (crcl- core_ core_ patch. patch. mcr, mcr, dd.200 dd.200 80505) 80505) and and InfoS- InfoS- hare hare 3.7.1 3.7.1 or or higher. higher. JustSystems XMetaL 5.5 support -SDDD- files SDL LiveContent Architect 11.0 Release Notes 75 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... JustSystems XMetaL 6.0 support --SSD- files JustSystems XMetaL 7.0 support ----D - files Sup- Re- port placed, added hence in re- 10.0.1 moved for in Just- 11.0.0 Sys- by tems Just- XMet- Sys- aL 7.0 tems - XMet- veri- aL 9.0 fied on version 7.0.111 JustSystems XMetaL 8.0 support ----S S files Sup- port added in 10.0.3 for Just- Sys- tems XMet- aL 8.0 - veri- fied on version 8.0.258 76 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... JustSystems XMetaL 9.0 support -----S files Sup- port added in 11.0.0 for Just- Sys- tems XMet- aL 9.0 - veri- fied on version 9.0.45 Syncro Soft SDL LiveContent Architect 11.0 Release Notes 77 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Adobe FrameMaker 9.0 support --S S D- files Only Only OASIS OASIS DITA DITA 1.1 1.1 Sup- Sup- port. port. Adobe FrameMaker 10.0 support ---SSD files Adobe FrameMaker 11.0 support ------files Adobe FrameMaker 12.0 support ------files SDL Trisoft Condition Manager S----- 3.2.x SDL Trisoft Condition Manager -S---- 3.3.x SDL Trisoft Condition Manager --S--- 9.1.x SDL Trisoft Condition Manager ---S-- 9.3.x SDL LiveContent Architect ----S- Condition Manager 10.1.x SDL LiveContent Architect -----S Condition Manager 11.1.x SDL LiveContent Architect ----S- DITA2Trisoft 10.1.x SDL LiveContent Architect -----S DITA2Trisoft 11.1.x Microsoft Windows 2003 SP2 S S - - - - Microsoft Windows 2003 R2 --D--- 32bit SP3 Microsoft Windows 2008 R2 --S--- 64bit Microsoft Windows 2008 R2 ---SSD 64bit SP1 Microsoft Windows 2012 64bit ------ 78 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Microsoft Windows 2012 R2 -----S 64bit Oracle RDBMs 9.2.0.2 S D D - - - Oracle RDBMs 10.2.0.4 S S D D D - Oracle RDBMs 11.2.0.1 - - - S S - Oracle RDBMs 11.2.0.4 - - - - - S Oracle RDBMs 12.1.0.1 ------Microsoft SQL Server 2000 SP4 S D - - - - Microsoft SQL Server 2005 SP2 S - - - - - Microsoft SQL Server 2005 SP3 - S D D - - Microsoft SQL Server 2005 SP4 - - - S D - Microsoft SQL Server 2008 SP1 - - S S - - Microsoft SQL Server 2008 SP2 - - - S - - Microsoft SQL Server 2008 SP3 - - - S D - Microsoft SQL Server 2008 R2 ----SD SP2 Microsoft SQL Server 2012 SP1 - - - - - S DITA-OT 1.3.1 ------DITA-OpenToolkit 1.3.1 does not support xml processing instructions (pi) properly because it drops them during the merge step. We deliver and integrate a patched/customized DITA-OT 1.3.1 version which does proper pi handling. Our bug report and fix was included in the DITA-OT 1.4.1 release. Microsoft SQL Server 2014 ------DITA-OT 1.4.1 S - - - - - DITA-OT 1.4.2.1 - S - - - - DITA-OT 1.5.1 - - S S - - DITA-OT 1.5.4 - - - - D - SDL LiveContent Architect 11.0 Release Notes 79 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... DITA-OT 1.7.5 - - - - S S Sup- port added in 10.0.2 for DITA- OT 1.7.5 Java Runtime 1.5.0_14 S S - - - - Java Runtime 1.6.0_12 (32b/64b) - - S S D - Sup- port added in 10.0.2 for Java Run- time 1.7.0_ 21 (32b). Java Runtime 1.7.0_21 (32b) - - - - S - Sup- port added in 10.0.2 for Java Run- time 1.7.0_ 21 80 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Java Runtime 1.7.0_21 (64b) - - - - - S Sup- port added in 10.0.2 for Java Run- time 1.7.0_ 21 (64b) for Trisoft- Solr- Lucene ser- vice. Java Development Kit 1.6.0_18 --SSD- (32b/64b) Java Development Kit 1.7.0_21 ----S S (64b) Sup- port added in 10.0.2 for Java Devel- opment Kit 1.7.0_ 21 (64b) SDL LiveContent Architect 11.0 Release Notes 81 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... OASIS DITA 1.0 DTD/Catalog D D D D D D configuration The The The The The The public public public public public public identi- identi- identi- identi- identi- identi- fier of fier of fier of fier of fier of fier of OASIS OASIS OASIS OASIS OASIS OASIS DITA DITA DITA DITA DITA DITA has no has no has no has no has no has no ver- ver- ver- ver- ver- ver- sion, sion, sion, sion, sion, sion, so so so so so so when when when when when when we we we we we we intro- intro- intro- intro- intro- intro- duced duced duced duced duced duced OASIS OASIS OASIS OASIS OASIS OASIS DITA DITA DITA DITA DITA DITA 1.1 we 1.1 we 1.1 we 1.1 we 1.1 we 1.1 we had to had to had to had to had to had to redirect redirect redirect redirect redirect redirect the the the the the the ver- ver- ver- ver- ver- ver- sion- sion- sion- sion- sion- sion- less less less less less less identi- identi- identi- identi- identi- identi- fier to fier to fier to fier to fier to fier to this this this this this this latest latest latest latest latest latest fully fully fully fully fully fully back- back- back- back- back- back- ward ward ward ward ward ward com- com- com- com- com- com- patible patible patible patible patible patible version version version version version version in our in our in our in our in our in our catalog catalog catalog catalog catalog catalog files. files. files. files. files. files. 82 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... OASIS DITA 1.1 DTD/Catalog SSD D D D configuration The The The The public public public public identi- identi- identi- identi- fier of fier of fier of fier of OASIS OASIS OASIS OASIS DITA DITA DITA DITA has no has no has no has no ver- ver- ver- ver- sion, sion, sion, sion, so so so so when when when when we we we we intro- intro- intro- intro- duced duced duced duced OASIS OASIS OASIS OASIS DITA DITA DITA DITA 1.2 we 1.2 we 1.2 we 1.2 we had to had to had to had to redirect redirect redirect redirect the the the the ver- ver- ver- ver- sion- sion- sion- sion- less less less less identi- identi- identi- identi- fier to fier to fier to fier to this this this this latest latest latest latest fully fully fully fully back- back- back- back- ward ward ward ward com- com- com- com- patible patible patible patible version version version version in our in our in our in our catalog catalog catalog catalog files. files. files. files. OASIS DITA 1.2 DTD/Catalog --SSSS configuration SDL LiveContent Architect 11.0 Release Notes 83 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... IBM DITA 1.3.2 DTD/Catalog D D D D D D configuration We We We We We We We strongly advise to change to strongly strongly strongly strongly strongly strongly OASIS DITA. The provided IBM advise advise advise advise advise advise DITA setup is only for backward to to to to to to compatibility. No new features change change change change change change will be implemented on these to to to to to to DTDs. OASIS OASIS OASIS OASIS OASIS OASIS DITA. DITA. DITA. DITA. DITA. DITA. The The The The The The pro- pro- pro- pro- pro- pro- vided vided vided vided vided vided IBM IBM IBM IBM IBM IBM DITA DITA DITA DITA DITA DITA setup is setup is setup is setup is setup is setup is only only only only only only for for for for for for back- back- back- back- back- back- ward ward ward ward ward ward com- com- com- com- com- com- patibil- patibil- patibil- patibil- patibil- patibil- ity. No ity. No ity. No ity. No ity. No ity. No new new new new new new fea- fea- fea- fea- fea- fea- tures tures tures tures tures tures will be will be will be will be will be will be imple- imple- imple- imple- imple- imple- mented mented mented mented mented mented on on on on on on these these these these these these DTDs. DTDs. DTDs. DTDs. DTDs. DTDs. AntennaHouse XSL Formatter 3.3 ------AntennaHouse XSL Formatter 4.1 S - - - - - AntennaHouse XSL Formatter 4.2 S S - - - - AntennaHouse XSL Formatter 4.3 - S - - - - AntennaHouse XSL Formatter 5.1 - - S - - - AntennaHouse XSL Formatter 5.3 - - - S - - AntennaHouse XSL Formatter 6.0 - - - - S - AntennaHouse XSL Formatter 6.2 - - - - - S PTC Arbortext Publishing Engine SSD--- 5.3 84 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Microsoft Internet Explorer 8 - - S S D - Microsoft Internet Explorer 9 - - - S S - Microsoft Internet Explorer 10 - - - - S S Sup- port added in 10.0.1 for Inter- net Ex- plorer 10. Microsoft Internet Explorer 11 - - - - - S Google Chrome (release update ----S S channel) Sup- Veri- port fied on added version in 35 10.0.4 for Google Chrome - veri- fied on version 30 SDL LiveContent Architect 11.0 Release Notes 85 Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Mozilla FireFox (release update ----S S channel) Sup- Veri- port fied on added version in 30 10.0.4 for Mozil- la Fire- Fox - veri- fied on version 25 SDL TMS 2011 SP4 CU2 - - - - - S SDL WorldServer 10.1 - - - - S D SDL WorldServer 10.2 - - - - S D SDL WorldServer 10.3 - - - - S D SDL WorldServer 10.4 - - - - - S Acrolinx Plug-in for Oxygen - - - - S S Veri- Veri- fied on fied for 10.0.5 oXy- for gen oXy- 14.2 gen and 14.2 15.2 using using AcrolinxAcrolinx 3.3.0 3.3.0 build build 3325 3325 86 SDL LiveContent Architect 11.0 Release Notes Deprecated, Obsolete and Restrictions SDL LiveContent Architect re- 3.7.x 3.8.x 9.0.x 9.2.x 10.0.x 11.0.x lease ... supports ... Acrolinx Plug-in for XMetaL - - - - S S Veri- Veri- fied on fied for 10.0.5 XMet- for aL 8 XMet- and 8J aL 8 using and 8J Acrolinx using 3.2.0 Acrolinxbuild 3.2.0 882 build 882 SDL LiveContent Architect 11.0 Release Notes 87 Deprecated, Obsolete and Restrictions 88 SDL LiveContent Architect 11.0 Release Notes Chapter 5 Acknowledgements SDL LiveContent includes open source or similar third-party software. “7zip” Is a file archiver with a high compression ratio “ant.jar, ant-optional.jar” 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, assemble, test and run Java applications. Ant can also be used effectively to build non Java applications, for instance C or C++ applications. More generally, Ant can be used to pilot any type of process which can be described in terms of targets and tasks. “DockPanel Suite” .Net Docking Library for Windows Forms “DITA-OT” The DITA Open Toolkit is a Java-based implementation of the OASIS DITA Technical Committee's specification for DITA DTDs and schemas. It contains ANT, SAXON,... “Apache FOP” Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF. “GeckoFX” Gecko is a free and open source layout engine used in many applications developed by 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. SDL LiveContent Architect 11.0 Release Notes 89 Acknowledgements “GNU Aspell” GNU Aspell is a Free and Open Source spell checker designed to eventually replace Ispell. It can either be used as a library or as an independent spell checker. Its main feature is that it does a superior job of suggesting possible replacements for a misspelled word than just about any other spell checker out there for the English language. Unlike Ispell, Aspell can also easily check documents in UTF-8 without having to use a special dictionary. Aspell will also do its best to respect the current locale setting. Other advantages over Ispell include support for using multiple dictionaries at once and intelligently handling personal dictionaries when more than one Aspell process is open at once. Specifically we are using GNUASpell dictionaries for de-CH, de-DE, en-CA, en-GB, en-US, es-ES, fr-FR, fr-CH, nl-NL. “google-code-prettify” google-code-prettify is a Javascript module and CSS file that allows syntax highlighting in an html page. “Hunspell” Hunspell is the spell checker of LibreOffice, OpenOffice.org, Mozilla Firefox 3 & Thunderbird, Google Chrome, and it is also used by proprietary software packages, like Mac OS X, InDesign, memoQ, Opera and SDL Trados. “InstallAnywhere” InstallAnywhere is the leading multiplatform development solution for application producers who need to deliver a professional and consistent cross installation experience for physical, virtual and cloud environments. From a single project file and build environment, InstallAnywhere creates reliable installations for on-premises platforms - Windows, Linux, Apple OS X, Solaris, AIX , HP-UX, and IBM iSeries - and enables you to take existing and new software products to a virtual and cloud infrastructure. “Jetty” The Jetty Web Server provides an HTTP server and Servlet container capable of serving static and dynamic content either from a standalone or embedded instantiations. Starting from Jetty version 7, the Jetty webserver and other core compoments are hosted by the Eclipse Foundation. “jQuery” jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. “jQuery 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. 90 SDL LiveContent Architect 11.0 Release Notes Acknowledgements “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. “Knockout JavaScript library” Knockout is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), KO can help you implement it more simply and maintainably. “Lucene, SOLR” The Apache Lucene™ project develops open-source search software. “MVC Web Projects” Auxiliary MVC Web Project libraries to serve InfoShareAuthor and InfoShareSTS. Typical libraries like WebGrease, StringTemplate (antlr3), AutoMapper, RouteDebug- ger, WebActivator,... “nHunspell ” NHunspell brings the spell checking, hyphenation and thesaurus to the Microsoft® .NET Framework. NHunspell is C# library and wraps native libraries for Hunspell, Hyphen and MyThes. One design goal of this library and wrapper is to keep the source code of the included libraries as unmodified as possible. New versions of the base libraries can therefore easily adopted to NHunspell. The integrated libraries are used in OpenOffice and they work with the dictionaries published on OpenOffice.org. “Red Hat Linux” Red Hat Enterprise Linux OpenStack Platform delivers an integrated foundation to create, deploy, and scale a secure and reliable public or private OpenStack cloud. Red Hat Enterprise Linux OpenStack Platform combines the world's leading enterprise Linux and the fastest-growing cloud infrastructure platform to give you the agility to scale and quickly meet customer demands without compromising on availability, security, or performance. “Rx .NET” Reactive Extensions for .NET library used to validate entered values “serializer.jar, xalan.jar” Xalan-Java is an XSLT processor for transforming XML documents into HTML, text, or other XML document types. It implements XSL Transformations (XSLT) Version SDL LiveContent Architect 11.0 Release Notes 91 Acknowledgements 1.0 and XML Path Language (XPath) Version 1.0 and can be used from the command line, in an applet or a servlet, or as a module in other program. “Thinktecture IdentityServer” Front-end Secure Token Service to serve SAML tokens. “Apache Tomcat” Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. “WiX” The WiX toolset builds Windows installation packages from XML source code. The toolset integrates seamlessly into build processes. “xercesImpl.jar” The Apache Xerces Project is responsible for software licensed to the Apache Software Foundation intended for the creation and maintenance of: ■ XML parsers ■ related software components “XULRunner” XULRunner is a runtime environment developed by the Mozilla Foundation to provide a common back-end for previewing. 92 SDL LiveContent Architect 11.0 Release Notes