Ixiasoft CCMS

What’s New

Keep up with IXIASOFT'S latest CCMS solutions.

Lite User Experience

Version 5.0

  July 10, 2018

Screenshot of IXIASOFT CCMS desktop and CCMS web.
Designed for the DITA expert and the lite user, IXIASOFT CCMS 5.0 introduces content-level security, easy authoring for SMEs, and a slick new UX. The product comes with new features—as requested by customers in the Evolution Lab—for the CCMS desktop version.

 

Now, a SME can be an author in DITA without knowing DITA. This solution is ideal for customers with confidentiality concerns. Information Architects can configure three different user permissions for content: invisible, read-only, or read-write. The UX was revamped to provide a straightforward and easy-to-use layout for lite users, with a user interface that is both accessible and responsive.

 

IXIASOFT CCMS 5.0 provides a democratic, collaborative work environment. In other words: it breaks down the barriers between different teams. In addition, version 5.0 aims to integrate a new, much simpler upgrade experience for customers.

CCMS Web 5.0

  • Lite users can act as authors and create and edit a map or a topic
  • Lite users can assign maps or topics
  • New IXIASOFT CCMS oXygen side panel provides topics’ CCMS properties
  • Information architects can create templates and associate them with a role
  • Content level security: information architects can set read and write access to user groups on DRM products or libraries
  • Responsive UI allows the usage of any device

 

CCMS Desktop 5.0

  • Build Manifest are now DRM objects, new instances are created with the new instances of their map
  • Ditaval are now CCMS objects, they have statuses and a revision history
  • Option to limit search to current DRM version
  • Support of External ID on import
  • CCMS Desktop built on Eclipse 4.7.3 framework
Server-side requirements

 

IXIASOFT TEXTML Server

  • IXIASOFT TEXTML Server  4.4.1.5167 and up
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended
    • Linux® Red Hat®/CentOS version 7 64-bits only

 

IXIASOFT CCMS Web

  • IXIASOFT CCMS Web Server
    • Apache Tomcat® 9 (9.0.8)
    • Java™ JDK 8 u121 or above, 64-bit
    • IXIASOFT CCMS Desktop 5.0 configuration files (minimum)
    • DITA-OT 2.3.1

 

IXIASOFT CCMS Admin plugin

  • TEXTML Admin plugin 4.3.7.4299 and up

 

Output Generator

  • Java 1.8.171 and up; 64-bit
  • Rendering software (such as RenderX, Antenna House, Apache FOP or Miramo)

 

Scheduler

  • Java 1.8.171 and up; 64-bit

 

 

Client-side requirements

 

IXIASOFT CCMS Web

  • The browser must support HTML5, CSS3, and JavaScript ES5 and must allow cookies
  • On Windows®:
    • Microsoft® Internet Explorer® 11
    • Last 3 major versions of Microsoft® Edge™
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™
  • On Linux®:
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™
  • On Mac®:
    • Apple® Safari® 10.0.1 and up
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™

 

IXIASOFT CCMS Desktop

  • oXygen® XML 19.1, oXygen® XML 20.x and up will be supported soon
  • Eclipse 4.7.3 64-bit (a ready packages is available from IXIASOFT download website)
  • Java 1.8.172 64-bit (already included into package)
  • Versions of OS supported:
    • Windows® 10 64-bit version is recommended, but the following are supported: Windows 7 64-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit, Windows 2016 64-bit (RDP or Citrix)
    • MacOS and Linux will be available soon
Important: The IXIASOFT CCMS Desktop requires good communication with the server components. The latency needs to be better than 50 ms.
Version Matrix
Initial Release - July 10, 2018
IMPORTANT NOTES

 

IXIASOFT CCMS Desktop build

  • To upgrade Desktop components from CMS solution version 4.5 to 5.0: please follow the instructions provided in the Upgrading the IXIASOFT CCMS Desktop from 4.5 to 5.0 Guide.
  • To update version 5.0 Desktop components to the current build: please follow the instructions provided in Updating an Existing IXIASOFT CCMS Desktop v5.0 Deployment Guide (Update Guide).

 

IXIASOFT CCMS Web build
The IXIASOFT CCMS Web component requires a license. Please contact IXIASOFT Sales to find out how your organization can obtain a license or update its existing license to use the new IXIASOFT license model for IXIASOFT CCMS Web. Install a new IXIASOFT CCMS Web component: Once you have your license, please follow the instructions provided in the IXIASOFT CCMS Web Installation Guide.

  • Update an existing 5.0 IXIASOFTF CCMS Web component: Please follow the instructions provided in the Updating an Existing IXIASOFT CCMS Web Deployment Guide.
  • Upgrade the CMS solution web components from version 4.6 to 5.0: Please follow the instructions provided in the Upgrading the IXIASOFT CCMS Web from 4.6 to 5.0 Guide
  • Additional requirement for Collaborative Review: configuration files in the Content Store and IXIASOFT Output Generator must be at least at version Desktop 4.5 (minimum).

 

 

KNOWN ISSUES

 

DITA CMS Web build

  • Subject scheme map is not supported in CCMS Web.
  • [DEV-5429] TEXTML Linux is case sensitive for login

 

 

BUG FIXES

 

IXIASOFT CCMS Web

  • [DEV-4299] IXIASOFT CCMS Web was unresponsive when the <reference/>, <prefix/>, <middle/> elements were missing from the users defined in the users.xml configuration file. This issue has been fixed.
  • [DEV-5449] When running the upgrade script, the oXygen workspace plugins were not updated. This issue has been fixed.
  • [DEV-4651] If the IXIASOFT CCMS Web was open in one browser and another session was opened in a separate browser, an error message appeared stating: “An internal error has occurred (HTTP error 500). Please contact your system administrator.” This issue has been fixed.

 

IXIASOFT CCMS Desktop

  • [DEV-4761] IXIASOFT CCMS Desktop experienced performance issues when working with subject scheme maps in DITA Map view. These issues have been fixed.
  • [DEV-5341] Instead of using relative paths, the DTD parser now uses public IDs specified in the ENTITY declarations to resolve the references between the modules.
  • [DEV-5533] When cloning a keydef in DITA Map view and selecting the option “Replace original component“, the key value was incorrectly changed to match the new topic ID. This issue has been fixed and the keydef retains the original key value.
  • [DEV-4718] A redline compare between two maps failed if a referable content topic was updated. This issue has been fixed

 

IXIASOFT Dynamic Release Management

  • none.

 

IXIASOFT Output Generator

  • none.

 

IXIASOFT Scheduler

  • none.

 

IXIASOFT Documentation

  • none.

Integration of the oXygen XML Web Author Component

Version 4.6

  December 21, 2017

This release’s key feature is the integration of the oXygen XML Web Author Component with DITA CMS Web—our powerful, fully DITA-compliant web editor that provides an intuitive, Word-like experience to Lite users like SMEs, engineers, and reviewers.

 

With this integration, DITA CMS 4.6 has all the features your Lite users want, all within a customizable framework that simplifies their experience. The DITA editor supports forms, has Schematron capabilities, guides users to utilize the correct markup, and imposes your business rules.

Web 4.6

  • oXygen XML Web Author Component integration
  • Map View for specialized map: lite users will be able to visualize and browse any assigned map regardless of their specialization level

 

Core 4.5

  • Library Dependency Editor: allows an information architect to globally change many dependencies of DRM structures
  • Redline compare improvement for DRM: technical writers will now be able to compare any map with any other snapshot or map from the same product or library
Server-side Requirements

 

TEXTML Server – Requirement

  • IXIASOFT TEXTML Server 4.3.6.4188 and up
    • If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, TEXTML Server 4.3.7.4299 and up is recommended.
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended.
    • Linux® Red Hat®/CentOS version 5 or 6 (both 64-bits only)
      Note: Red Hat®/CentOS version 7 is not supported.

DITA CMS Web

  • CMS Application Server
    • GlassFish Server 4.x
    • Java™ JDK 8 u60 or above, 64-bit
    • Microsoft® .NET Framework 3.5 (on Windows only)
  • DITA CMS Web Application:
    • Apache Tomcat® 7 (7.0.11 and up)
    • Java™ JDK 8 u60 or above, 64-bit
  • DITA CMS Core
    • DITA-OT 2.3.1
    • DITA CMS Core 4.5.35 configuration files (minimum)

DITA CMS Admin Plugin – Requirement

  • TEXTML Admin plugin 4.3.7.4299 and up

Output Generator – Requirement

  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up; 64-bit
    Note: When you run the integrator on the DITA-OT (for example, run ant -f integration.xml in the command prompt) and you are using Java 1.8, it may give you different results because the plugins are not processed in the same order. Since this may cause a change in the behavior of the plugins, it is recommended that you validate the results before going into production.
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)

Scheduler – Requirement

  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up, 64-bit

 

 

Client-side Requirements

 

DITA CMS Web

  • The browser must support HTML5, CSS3, and JavaScript ES5 and must allow cookies
  • On Windows®:
    • Microsoft® Internet Explorer® 11
    • Last 3 major versions of Microsoft® Edge™
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™
  • On Linux®:
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™
  • On Mac®:
    • Apple® Safari® 10.0.1 and up
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Google Chrome™

DITA CMS Eclipse Client – Requirement

  • oXygen® XML 18.x and 19.x
  • XMetaL® XMAX™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700], 32-bit or 64-bit
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (recommended), or Java 1.8.60 and up (limited support), 32-bit or 64-bit
    Note: Java 1.8 support for the DITA CMS solution Eclipse Client is available, but not recommended and should only be used if absolutely necessary. To use Java 1.8.60 or up, you must install an extra plugin or dropin to patch Eclipse to support Java 1.8. For more information, see the guide: Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Versions of OS supported:
    • Windows® 7 64-bit version minimum is recommended, but the following are supported: Windows 7 32-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit (RDP or Citrix)
    • Any Linux® platform supported by Eclipse SDK 4.3 (32-bit or 64-bit version)
Important: The DITA CMS Eclipse Client requires good communication with the server components. The latency needs to be better than 50 ms.
Version Matrix
Service Pack 3 - June 14, 2018
IMPORTANT NOTES

 

DITA CMS Core build

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • To update version 4.5 Core components to the current build: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

DITA CMS Web build
The DITA CMS Web component requires a license. Please contact IXIASOFT Sales to find out how your organization can obtain a license or update its existing license to use the new IXIASOFT license model for DITA CMS Web.Install a new DITA CMS Web component: Once you have your license, please follow the instructions provided in the DITA CMS Web Installation Guide.

  • Update an existing 4.6 DITA CMS Web component: Please follow the instructions provided in the Updating an Existing DITA CMS Web Deployment Guide.
  • Upgrade Web components from version 4.5 to 4.6: Please follow the instructions provided in the Upgrading the DITA CMS Web from 4.5 to 4.6 Guide.
  • Additional requirement for Collaborative Review: configuration files in the Content Store and Output Generator must be at least at version Core 4.5 (minimum).

 

KNOWN ISSUES
  • DEV-5449 When running the upgrade script, the oXygen workspace plugins were not updated.
  • DEV-5122 If a user was provisioned in the DITA CMS with a lower case domain but logged into the DITA CMS Web using an uppercase domain, topics could not be checked out.
  • DEV-3384 In deployments using DRM, images were added to topics without the keyref attribute which resulted in broken images.
BUG FIXES
  • DEV-5533 When cloning a keydef in DITA Map view and selecting the option “Replace original component”, the key value was incorrectly changed to match the new topic ID. This issue has been fixed and the keydef retains the original key value.
  • DEV-5315 When using the Search and Replace feature for documents that had been localized, the Error Log view displayed an “Unhandled event loop execution” error. This issue has been fixed.
  • DEV-5168 In DRM deployments, when opening a map with the oXygen DITA Map Editor, all topics and images used in the map were saved to the user’s workspace. This issue has been fixed.
  • DEV-4761 DITA CMS experienced performance issues when working with subject scheme maps in DITA Map view. These issues have been fixed.
  • DEV-3706 In deployments using DRM, the Search and Replace feature would not find any matches when executed from the DITA Map view. This issue has been fixed.
  • [DEV-4864] Images within referable-content topics did not display in DITA CMS Web. This issue has been fixed.
  • [DEV-4905] When a user session became inactive, an error message appeared stating: “An internal error has occurred (HTTP error 500). Please contact your system administrator.” This issue has been fixed and users are now presented with a new login window.
Service Pack 2 - April 19, 2018
IMPORTANT NOTES

 

DITA CMS Core build

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • To update version 4.5 Core components to the current build: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

 

DITA CMS Web build
The DITA CMS Web component requires a license. Please contact IXIASOFT Sales to find out how your organization can obtain a license or update its existing license to use the new IXIASOFT license model for DITA CMS Web.Install a new DITA CMS Web component: Once you have your license, please follow the instructions provided in the DITA CMS Web Installation Guide.

  • Update an existing 4.6 DITA CMS Web component: Please follow the instructions provided in the Updating an Existing DITA CMS Web Deployment Guide.
  • Upgrade Web components from version 4.5 to 4.6: Please follow the instructions provided in the Upgrading the DITA CMS Web from 4.5 to 4.6 Guide.
  • Additional requirement for Collaborative Review: configuration files in the Content Store and Output Generator must be at least at version Core 4.5 (minimum).

 

 

KNOWN ISSUES

 

DITA CMS Web build

  • [DEV-3579] When a topic is imported into DITA CMS and then assigned to a user for editing in DITA CMS Web in a deployment where the ForceTrackChanges option is set to “true,” the track changes feature is not enabled if the topic is identified as a first revision of the object.
  • [DEV-4299] DITA CMS Web becomes unresponsive when the <reference/>, <prefix/>, <middle/> elements are missing from the users defined in the users.xml configuration file. Ensure that these elements are present in the configuration for each user and left empty if no value is required.
  • [DEV-4343] When an assignment that contains inline SVG content is opened in the Editing or Preview page, the SVG is not displayed.

 

 

BUG FIXES

 

DITA CMS Core

  • [DEV-2102] In DITA Map view, users were able to move the first topic above the title element which broke the map. This issue has been fixed and the up arrow is now disabled when selecting the first topic.
  • [DEV-4132, DEV-4761] DITA CMS experienced performance issues when working with subject scheme maps in DITA Map view. These issues have been fixed.
  • [DEV-4704] When performing a Localize operation in sequential localization, localized content was incorrectly set back to English after edits to other content within the English topic. This issue has been fixed.
  • [DEV-4865] When clicking the Refresh button in DITA Map view or performing an action that caused a refresh of the open map, all of the content above the selected map element was highlighted. This issue has been fixed.
  • [DEV-4867] When a submap was locked from the DITA Map view, the content of the submap was not refreshed with the content from the Content Store. This issue has been fixed.
  • [DEV-5127] An issue occurred when an image was created in a Content Store that was configured with a default language other than English. For example, <languages default=”English (US)”>. If a user created an image without selecting a language from the Language list, the image was created without a language code, and as a result, it could not be found in search results. This issue has been fixed. If you have encountered this issue, please contact the IXIASOFT support team for further assistance with locating and fixing these images.

 

Dynamic Release Management

  • [DEV-3451] When performing a Localize operation in DRM, localized content was incorrectly set back to Localization:tb translated without any edits being made to the English topic. This issue has been fixed.
  • [DEV-4734] DITA CMS experienced performance issues for DRM objects with a large number of dependencies when performing a view dependencies or a delete operation. Performance improvements have been implemented.

 

DITA CMS Web

  • [DEV-4864] Images within referable-content topics did not display in DITA CMS Web. This issue has been fixed.
  • [DEV-4905] When a user session became inactive, an error message appeared stating: “An internal error has occurred (HTTP error 500). Please contact your system administrator.” This issue has been fixed and users are now presented with a new login window.

 

Output Generator

  • none.

 

Scheduler

  • none.

 

Documentation

  • none.
Service Pack 1 - February 22, 2018
IMPORTANT NOTES

 

DITA CMS Core build

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • To update version 4.5 Core components to the current build: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

 

DITA CMS Web build
The DITA CMS Web component requires a license. Please contact IXIASOFT Sales to find out how your organization can obtain a license or update its existing license to use the new IXIASOFT license model for DITA CMS Web.Install a new DITA CMS Web component: Once you have your license, please follow the instructions provided in the DITA CMS Web Installation Guide.

  • Update an existing 4.6 DITA CMS Web component: Please follow the instructions provided in the Updating an Existing DITA CMS Web Deployment Guide.
  • Upgrade Web components from version 4.5 to 4.6: Please follow the instructions provided in the Upgrading the DITA CMS Web from 4.5 to 4.6 Guide.
  • Additional requirement for Collaborative Review: configuration files in the Content Store and Output Generator must be at least at version Core 4.5 (minimum).

 

 

KNOWN ISSUES

 

DITA CMS Web build

  • [DEV-3579] When a topic is imported into DITA CMS and then assigned to a user for editing in DITA CMS Web in a deployment where the ForceTrackChanges option is set to “true,” the track changes feature is not enabled if the topic is identified as a first revision of the object.
  • [DEV-4299] DITA CMS Web becomes unresponsive when the <reference/>, <prefix/>, <middle/> elements are missing from the users defined in the users.xml configuration file. Ensure that these elements are present in the configuration for each user and left empty if no value is required.
  • [DEV-4343] When an assignment that contains inline SVG content is opened in the Editing or Preview page, the SVG is not displayed.

 

 

BUG FIXES

 

DITA CMS Core

  • [DEV-4437] After moving topics in the DITA Map view using the left and right arrow buttons and then releasing the map, the topics appeared in their original location. This issue has been fixed.
  • [DEV-4603] When importing an image that was not fully supported, such as a Visio drawing, a message appeared saying that the image preview would not display but that the image would appear in outputs. The message now says: “The image file format of this file is not recognized by the CMS. If it is imported, the image will be stored in the CMS, but it will be not displayed in the Preview view or as a thumbnail. Furthermore, the rendering of this image in an output depends on the capabilities of the selected output type.”
  • [DEV-4645] When localizing from a map at Published:done using concurrent localization, some topicref elements were broken. This issue has been fixed.
  • [DEV-4695, DEV-4796] When selecting a ditaval in the Generate Output dialog box, the DITA CMS Eclipse Client became unresponsive and a Java Heap error was displayed. This issue has been fixed.

 

Dynamic Release Management

  • [DEV-3299] When trying to refactor a topic in DRM, an error message appeared stating that the object could not be moved because the library was closed. Users were then unable to view the values in the Information View for the topic. This issue has been fixed.
  • [DEV-3866] Users were unable to refactor topics to a library if the topic contained internal cross-references. This issue has been fixed.
  • [DEV-4113] The cloning of a version from one product or library to another is no longer permitted, the version can only be cloned within the same product or library.

 

DITA CMS Web

  • [DEV-4433] When you open the Editing page, the message “oXygen XML Web Author – Evaluation Only” is displayed in the editor. The new license is included in the installation script and the message is removed when you perform the update to the latest release.
  • [DEV-4480] The DITA CMS Web installation script did not update the Tomcat password correctly when customers used a different username and password combination from the default. When opening topics in the web client, a license error was displayed. This issue has been fixed.
  • [DEV-4617] When adding an image to a topic that was in a custom workflow state such as Authoring:contribute, it was not possible to change the topic status. This issue has been fixed.

 

Output Generator

  • none.

 

Scheduler

  • none.

 

Documentation

  • none.
Initial Release - December 21, 2018
IMPORTANT NOTES

 

DITA CMS Core build

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.

 

DITA CMS Web build
The DITA CMS Web component requires a license. Please contact IXIASOFT Sales to find out how your organization can obtain a license or update its existing license to use the new IXIASOFT license model for DITA CMS Web.Install a new DITA CMS Web component: Once you have your license, please follow the instructions provided in the DITA CMS Web Installation Guide.

  • Update an existing 4.6 DITA CMS Web component: Please follow the instructions provided in the Updating an Existing DITA CMS Web Deployment Guide.
  • Upgrade Web components from version 4.5 to 4.6: Please follow the instructions provided in the Upgrading the DITA CMS Web from 4.5 to 4.6 Guide.
  • Additional requirement for Collaborative Review: configuration files in the Content Store and Output Generator must be at least at version Core 4.5 (minimum).

 

 

KNOWN ISSUES

 

DITA CMS Web build

  • [DEV-3579] When a topic is imported into DITA CMS and then assigned to a user for editing in DITA CMS Web in a deployment where the ForceTrackChanges option is set to “true,” the track changes feature is not enabled if the topic is identified as a first revision of the object.
  • [DEV-4299] DITA CMS Web becomes unresponsive when the <reference/>, <prefix/>, <middle/> elements are missing from the users defined in the users.xml configuration file. Ensure that these elements are present in the configuration for each user and left empty if no value is required.
  • [DEV-4343] When an assignment that contains inline SVG content is opened in the Editing or Preview page, the SVG is not displayed.
  • [DEV-4433] When you open the Editing page, the message “oXygen XML Web Author – Evaluation Only” is displayed in the editor. This message will be removed in the next release.

 

 

BUG FIXES

 

DITA CMS Core

  • [DEV-2125, DEV-3523] Using the arrow keys to move topics up and down in DITA Map view caused topics to not move or to move to an incorrect location in the map. This issue has been fixed.
  • [DEV-2784] Inline elements such as uicontrol were auto-translated. This caused issues with translation memory since the parent element contained English text and the inline element contained translated text. This issue has been fixed and inline elements are no longer auto-translated if the parent element is not auto-translated.
  • [DEV-3201] When comparing a map to a snapshot, redline compare failed to produce a PDF output with the DITA-OT log reporting an error about the status “tobedetermined”. This issue has been fixed.
  • [DEV-3277] Searching for orphaned documents on large content stores caused TEXTML performance issues for all users. This issue has been fixed.
  • [DEV-3526] Changing a topicref to a chapter and then back to a topicref corrupted the map open in DITA Map view. This issue has been fixed.
  • [DEV-3705] When creating a new ditaval and selecting the Use a Subject Scheme drop-down list, existing subject schemes did not appear in the list. This issue has been fixed.
  • [DEV-3737, DEV-4251] When attempting to create a Collaborative Review on a map that contained an out-of-scope cross-reference, an error would occur and the generation of the Collaborative Review would fail. This issue has been fixed. Now, when out-of-scope cross-references are present, a dialog box opens to offer the choice of proceeding with the creation of the Collaborative Review or canceling the operation. This fix has also been implemented for creating snapshots. When the Collaborative Review is opened in DITA CMS Web, an out-of-scope cross-reference appears as unclickable text.
  • [DEV-3891] When performing the Localize operation, DITA CMS was doing an incorrect comparison between the revision of the source topic in the Authoring workflow and the revision of the localized topic to determine if a change had been made. This issue has been fixed and DITA CMS now compares the source topic revision to the localized topic authoring revision.
  • [DEV-3941] DITA CMS displayed an error when importing a localization kit if the only change was letter case. The error indicated that the source files and the translated files were the same. This issue is now fixed for all localization methods, including concurrent localization.
  • [DEV-4039] For sequential localization, topics that had already been translated and had not been edited in English were being set to Localization:tb translated instead of the status defined in the translation.autotranslation.fulltranslation.status field in the localizationManagers.xml file. This issue has been fixed.
  • [DEV-4128, DEV-4129, DEV-4208] Multiple display issues with the Ditaval view were reported. These issues have been fixed so user-specified settings such as column widths and expanded or collapsed state of the folders in the view are retained after a DITAVAL is released or the DITA CMS is restarted.

 

Dynamic Release Management

  • [DEV-3738] The topic “Restrict use of output types by role” contained an out-of-date example of configuring the output types. This issue has been fixed by updating the topic with the currently recommended configuration.
  • [DEV-4372] The Select Versions dialog box offered invalid choices when performing an Add to operation. This issue has been fixed.

 

DITA CMS Web

  • [DEV-4131] When a user performed a broad search for images in the Editing page and the Content Store contained a large number of images (for example, over 90,000 images), DITA CMS Web would become unresponsive. This issue has been fixed by limiting the number of image results displayed in the Image Wizard to 240 images, and for deployments using the Dynamic Release Management module search is also limited to the images contained in the version.

 

Output Generator

  • [DEV-3737] When attempting to create a Collaborative Review on a map that contained an out-of-scope cross-reference, an error would occur and the generation of the Collaborative Review would fail. This issue has been fixed. Now, when out-of-scope cross-references are present, a dialog box opens to offer the choice of proceeding with the creation of the Collaborative Review or canceling the operation. This fix has also been implemented for creating snapshots. When the Collaborative Review is opened in DITA CMS Web, an out-of-scope cross-reference appears as unclickable text.
  • [DEV-3743] When creating a Collaborative Review in DITA CMS Eclipse Client, the review object was created even if the Output Generator transformation scenario failed. When trying to open the review in the DITA CMS Web, users would see a “404 file not found” error. This issue has been fixed and the review object is only created when the output is generated successfully.

 

Scheduler

  • [DEV-3956]* There was a syntax error in the Scheduler daily_reminder.xsl file. This issue has been fixed and may require a change in your Content Store. See the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.

 

Documentation

  • [DEV-3738] The topic “Restrict use of output types by role” contained an out-of-date example of configuring the output types. This issue has been fixed by updating the topic with the currently recommended configuration.