DITA CMS 4.3 Release Notes

BuildRelease Date
4.3.61 August 8, 2017
4.3.57 June 15, 2017
4.3.47 March 15, 2017
4.3.33 December 15, 2016
4.3.31 October 17, 2016
4.3.7 April 29, 2016
4.3.6 March 29, 2016

Build 4.3.61 - 20170808

 To view the instructions for updating to a new build, see the Update Guide

Important notes

Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in Updating an Existing DITA CMS v4.3 Deployment (Update Guide).

 

End of Support

The IXIASOFT Web Author and Web Collaborative Review modules are being merged into a unique DITA CMS Web component to take your content creation and reviewing processes to the next level. The DITA CMS Web component will include the authoring and reviewing features available today as well as new features, such as a map view, topic and map creation, as well as map editing.

As such, all support for Web Author and Web Collaborative Reviewer will stop by December 31st, 2017.

 

Features

  • oXygen XML Editor 19 is now supported.

Major bug fixes

  • DITA CMS Core
    • None
  • Dynamic Release Management
    • None
  • Output Generator
    • None
  • Scheduler
    • None
  • Documentation
    • None

Bug fixes

  • DITA CMS
    • [DEV-2240] If the Import as External checkbox was selected when importing content, the status of the objects was reset to the initial state instead of remaining in the external read-only state. This issue has been fixed so that the status is not changed when importing.
    • [DEV-2370/3955] When a ditaval was being edited by a user, the Open Ditaval XML option was greyed out for other users. This issue has been fixed.
    • [DEV-2644/4143] The DITA CMS Eclipse Client would eventually become unresponsive when the Ditaval view remained open. This issue has been fixed.
  • Dynamic Release Management
    • None
  • Output Generator
    • None
  • Scheduler
    • None
  • Documentation
    • None

Legacy components

  • Web Collaborative Reviewer
    • None
  • Web Author
    • None
  • CMS Application Server
    • None

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

Software Requirements

Before installing DITA CMS components, the servers and workstations on which the software will be installed must meet a set of requirements.

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • 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 Admin plugin
  • TEXTML Admin plugin 4.3.6.4205 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
    Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
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
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Collaborative Reviewer
If installing Apache Tomcat® 6:
  • Apache Tomcat® 6.0.33 and up
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
If installing Apache Tomcat® 7:
  • Apache Tomcat® 7.0.11 and up
  • Java™ JDK 8 u60 or above, 64-bit
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Author
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java™ JDK 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
    • Microsoft® .NET Framework 3.5 (on Windows only)
  • Web Author Application:
    • Apache Tomcat® 6.0.33 and up
    • Java™ JRE 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.

 

Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • 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, 32-bit or 64-bit (Java 1.8 is not supported)
  • 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.
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™
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Collaborative Reviewer
  • Java™ JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up
  • Internet browser:
    • On Windows®:
      • Microsoft® Internet Explorer® 11
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
      Note: Chrome is not supported.
    • On Linux®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
    • On Mac®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Author
  • Java™ JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)
  • Internet browser:
    • On Windows®:
      • Microsoft® Internet Explorer® 11
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
      Note: Chrome is not supported.
    • On Linux®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
    • On Mac®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.

Build 4.3.57 - 20170615

 To view the instructions for updating to a new build, see the Update Guide

Important notes

  • Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in Updating an Existing DITA CMS v4.3 Deployment (Update Guide).
  • A new build of the TEXTML Server is available (4.3.7.4299). This build includes a bug fix (DEV-2051) in the ICU word parsing feature, where asterisks (*) were removed from the search query. If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, IXIASOFT recommends that you install this version to benefit from this bug fix.

 


End of Support

The IXIASOFT Web Author and Web Collaborative Review modules are being merged into a unique DITA CMS Web component to take your content creation and reviewing processes to the next level. The DITA CMS Web component will include the authoring and reviewing features available today as well as new features, such as a map view, topic and map creation, as well as map editing.

As such, all support for Web Author and Web Collaborative Reviewer will stop by December 31st, 2017.

Features

  • None

Known Issues

  • [DEV-2962] The Edit Profiling Attributes dialog box may not display the correct values if multiple subject schemes are contained in the map and the user changes the positions of the subject schemes in the map while setting conditions on content.

Major bug fixes

  • DITA CMS Core
    • [DEV-2077] Each time an object open in the editor was manually or automatically saved, the DITA Map view was refreshed causing the elements in the DITA Map view to expand. This issue has been fixed so the DITA Map view is no longer refreshed automatically and elements do not automatically expand when the DITA Map view is refreshed.
    • [DEV-2086/4068] A report created using the DITA CMS Eclipse Client in a language other than English did not work with Scheduler. This issue has been fixed.
    • [DEV-2089/4133] In pivot localization, when localizing from a pivot language to a target language, the authoring revision property of the target topic was initialized with the wrong value, which created problems during the localization process. This issue has been fixed.
    • [DEV-2096/4063] Some strings in the DITA CMS user interface had not been translated to French. This issue has been fixed.
    • [DEV-2098/4045] When opening the Set Conditions dialog for a map that contained a subject scheme, the dialog showed the first level of the subject scheme conditions, and not the whole hierarchy. This issue has been fixed and the complete subject scheme hierarchy is now displayed.
    • [DEV-2270] When an image localization kit was prepared, the status of the map was used to validate the status of the images included in the kit, which caused an error when the map was not in a valid status to prepare the kit. This issue has been fixed so this validation no longer occurs and preparing an image localization kit is no longer dependent on the status of the map and its topics, but only on the status of the images being included in the kit.
    • [DEV-2634] When a map contained submaps nested in submaps, it appeared possible in the DITA Map view to remove a child map from its parent submap without it being locked. The child map would disappear from the DITA Map view, but the child map was not actually removed from the submap. This issue has been fixed.
  • Dynamic Release Management
    • None
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • None
  • Scheduler
    • None
  • Web Author
    • None
  • Documentation
    • None
  • CMS Application Server
    • None

Bug fixes

  • DITA CMS Core
    • [DEV-1616]* The Preview view could not display a preview of topics which contained new DITA 1.3 elements. This issue has been fixed and requires changes to the Content Store. The Preview view is now based on the xhtml plugin of the DITA OT 2.3.1. See Updating an Existing DITA CMS v4.3 Deployment (Update Guide) for the procedure.
    • [DEV-2038/4132] The list of results produced when a user clicked Validate Links contained incorrect results. This issue has been fixed so the list contains only the instances of links that point to documents that are not in the current map (out-of-scope links).
    • [DEV-2269] When a user prepared a localization kit for a map and theinclude.default.imagesparameter was set to "true" in the DITA CMS configuration, images referenced by topics in the map were incorrectly changing status to Localization:in translation. This issue has been fixed so images do not change to Localization:in translation until the image localization kit is prepared.
    • [DEV-2464] When importing localized content back into DITA CMS, the content was reformatted into a single line. This issue has been fixed so the localized content is imported as is.
    • [DEV-2661] When a user attempted to insert an image into a topic open in the editor area using XMetaL XML editor and the DITA Map view was open but did not contain an active map, the insert action would fail. This issue has been fixed.
    • [DEV-2720] The toolbar icons for the HyperSTE plugin were missing from the interface. This issue has been fixed.
  • Dynamic Release Management
    • [DEV-2085] In some cases objects were not set with a primary version. To resolve the issue, the Change Primary Version feature has been modified to allow users to reset the primary version on objects that are missing the value.
    • [DEV-2106] When a topic from one version was added to a map in another version using drag-and-drop or the right-click XML editor menu, the topic was added to the map's version, but its referenced objects were not. This issue has been resolved by preventing objects in one version from being added to another version when they are added to a map using drag-and-drop or the right-click XML editor menu. Now objects must be added to the version before they can be included as a child of an object in that version. For example, a topic and its child objects must be added to the map's version before the topic can be added to the map.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [DEV-2093/4155] A new script is now available to simplify making the Output Generator files executable on Linux for deployments that use source control. See the Output Generator Installation Guide for the procedure.
    • [DEV-2675/3691] The DTDs in \data\DITA-OT1.8.5\plugins\com.ixiasoft.dita.dtd and \data\dita-ot-2.3.1\plugins\com.ixiasoft.dita13.dtd were replaced with updated versions.
    • [DEV-2683/2781] The example targetclient.FooBarwrapperin the conductor-client.xml.orig file was modified to include all the possible antcalls supplied by IXIASOFT:
  • Scheduler
    • [DEV-2642] Changes have been made in the log4j.properties file, which results in less unnecessary information being added to the wrapper.log file.
  • Web Author
    • None
  • Documentation
    • [DEV-2019] A broken link in the Upgrading a Deployment to DITA 1.3 was fixed.
    • [DEV-2112] A recommendation for the minimum monitor resolution was added to the hardware system requirements in Planning a DITA CMS Deployment.
    • [DEV-2289] Information was added to the topics that describe how to import objects to clarify the relationship between the Import Base Path value and the Use relative path along with file name to match document to update option. See DITA CMS User Guide.
    • [DEV-2297] An outdated paragraph that mentioned a read-only general login for OTRS was removed from the OTRS Quick Reference.
  • CMS Application Server
    • None

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

Software Requirements

Before installing DITA CMS components, the servers and workstations on which the software will be installed must meet a set of requirements.

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • 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 Admin plugin
  • TEXTML Admin plugin 4.3.6.4205 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
    Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
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
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Collaborative Reviewer
If installing Apache Tomcat® 6:
  • Apache Tomcat® 6.0.33 and up
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
If installing Apache Tomcat® 7:
  • Apache Tomcat® 7.0.11 and up
  • Java™ JDK 8 u60 or above, 64-bit
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Author
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java™ JDK 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
    • Microsoft® .NET Framework 3.5 (on Windows only)
  • Web Author Application:
    • Apache Tomcat® 6.0.33 and up
    • Java™ JRE 1.7.0_51 or 1.7.0-80 and up, 64-bit (Java 1.8 is not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.

 


Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • oXygen® XML 18.x (19.x not supported)
  • 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, 32-bit or 64-bit (Java 1.8 is not supported)
  • 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.
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™
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Collaborative Reviewer
  • Java™ JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up
  • Internet browser:
    • On Windows®:
      • Microsoft® Internet Explorer® 11
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
      Note: Chrome is not supported.
    • On Linux®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
    • On Mac®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.
Web Author
  • Java™ JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)
  • Internet browser:
    • On Windows®:
      • Microsoft® Internet Explorer® 11
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
      Note: Chrome is not supported.
    • On Linux®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
    • On Mac®:
      • Mozilla® Firefox® 52 ESR (Extended Support Release), 32-bit (Firefox 52 not supported)
Note: This is not included in the basic DITA CMS Small Business deployment. It requires an additional license.

Build 4.3.47 - 20170315

 To view the instructions for updating to a new build, see the Update Guide

Important notes

  • Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in Updating an Existing DITA CMS v4.3 Deployment (Update Guide).
  • To better support the DRM multi-level library feature, it is no longer possible to create or import maps, topics, images, and resources into more than one product or library. To reuse objects between products, you must use multi-level libraries.

Features

  • [2340] The Ditaval view has been enhanced with the ability to clone a DITAVAL file.
  • [3486]* You can now deprecate conditional attribute values so that they no longer appear in the DITA CMS dialogs. This requires changes to the conditionaltext.dtd file. See Updating an Existing DITA CMS v4.3 Deployment (Update Guide) for the procedure.
  • [3891]* The languages.xml configuration file has been enhanced with two new optional attributes,defaultandauthoring, which define which language is selected by default in the dialogs used to create objects and which languages are offered as options in those dialogs. This requires changes to the languages.dtd file. See Updating an Existing DITA CMS v4.3 Deployment (Update Guide) for the procedure.
  • [3893/3900] The Assignments view has been enhanced to:
    • Allow the lists of available assignees to be filtered based on the defined Team members in the selected project.
    • Allow a link to an external web page to be included with the assigned document.
  • [3896] You can now store oXygen XML Editor's document types extensions (framework extensions) in the Content Store so they are added into the oXygen Editor's Preferences when the DITA CMS Eclipse Clients are launched.
  • [3919] The Create Ditaval and Edit Ditaval dialogs have been enhanced to support subject schemes.
  • [4122] (DRM only) You can configure an index to search with the filename in the Search view, in the Search in drop-down list. This requires changes to the advancedSearchIndexes.xml file. See Updating an Existing DITA CMS v4.3 Deployment (Update Guide) for the procedure.

Known issues

There are currently some issues with refreshing the DITA Map View in the following cases:

  • When selecting the Branch>Mark As Merged command, the asterisk is not removed until the user refreshes the map. (3994)
  • When removing a topic from a submap, clicking the Search view, and then clicking the DITA Map view again, the focus in the DITA Map view is lost. (3945)
  • When locking or releasing a submap, the submap is selected but the focus moves to the top of the main map. (3944, 3925)
  • When opening a map, the map is not expanded. (3885)
  • If the same submap is available twice in a map, clicking the expand button on the second submap expands the first submap. (4148)
  • When dropping a submap into a main map, the DITA Map view displays the submap as if it is empty. (4142)
  • After adding a topic and reverting its parent submap, the focus moves to the top of the main map. (3921)

We are currently working on these issues. If the map does not refresh automatically as expected, please use the Refresh button.

Major bug fixes

  • DITA CMS
    • [2884] The Export Children Intersection command resulted in an error in the Error Log and an empty .tsv file. This issue has been fixed.
    • [3652] The error "Invalid drop point: This file cannot be added at this position in the map" would occasionally appear when topics where dragged into a relationship table in the RelTable Editing perspective. This issue has been fixed.
    • [3659/3926] The following issues were fixed in the import feature:
      • When an image was imported with the Update existing documents checkbox selected, the imported image did not replace the existing image. This issue has been fixed. Note: If the image object contained multiple formats, all formats are replaced by the imported image.
      • When importing an image using File > Import, the default path when you clicked Browse did not provide the path set in the Image Import Directory in Window > Preferences > DITA CMS > Import Export. This issue has been fixed.
    • [3863] Replacing an SVG file in a multi-format image generated a java.lang.NullPointerException and corrupted the image. This issue has been fixed.
    • [3910] When users specified a mix of lowercase and uppercase letters in their user name in the Preferences dialog on Windows, they were able to log in but unable to open maps and topics. This issue has been fixed.
    • [3967] When the conditionaltext.xml file was updated, the changes were not reflected correctly in the DITA CMS. This issue has been fixed and the values are now updated when users click Synchronize configuration.
    • [3968] The categories for the profiling attributes in the Edit Profiling Attributes dialog were listed in random order. They are now listed in the order in which they are configured in the conditionaltext.xml configuration file.
    • [3989] When creating a map or topic from a template that included sets of curly brackets—that is, {{ and }}—as well as accented characters, the accented characters were not created correctly. This issue has been fixed.
    • [4003] When using pivot localization, auto-translated content was lost when localizing content to the third target language. This issue has been fixed.
    • [4017] When adding a topic to a bookmap that contained a submap, the auto-refresh collapsed the bookmap from the submap to the end of the bookmap. This issue has been fixed.
    • [4021] The Insert as conref menu item from the Oxygen Editor sub-menu was always active, even if the object selected could not be inserted as a conref (for example, maps and images). This issue has been fixed.
    • [4038/4058] There were performance issues with the Assign To command when the users.xml file contained more than 500 active users or 100 inactive users. These issues have been fixed.
    • [4040] When using the buttons from the DITA CMS Access toolbar (Lock, Release, and Replace with Server Revision), the states of the buttons in the toolbar were not always refreshed even when the action was completed successfully. This issue has been fixed.
    • [4062] In some cases, opening the Ditaval selection window in the Output Generator dialog generated an AssertionFailedException and trying to open the Ditaval view generated an Unhandled event loop exception. These issues have been fixed.
    • [4073] When a map in the DITA Map view containedelements, either directly or in one of its submaps, and it also referenced a subject scheme, the keyrefs were not resolved in the topics that were opened in oXygen. This issue has been fixed.
  • Dynamic Release Management
    • [3531] When running the Validate Links command on a map, the results provided the referenced topic instead of the topic that had the invalid reference. This issue has been fixed.
    • [3560] The width of the Version name column had a fixed length in the Create a New Instance window, which made it difficult to read long version names. This issue has been fixed and the column width now adjusts to the length of the version name.
    • [3823] The Merge command of the DRM Synchronization feature failed when the document contained comment lines with special characters. This issue has been fixed.
    • [3969] When creating a new instance of a topic that was in the "approved" state, the newly created topic was in the "work" state but its parent map was not cascaded to the "work" state. This issue has been fixed.
    • [3990] Using the DRM-> Add to command on topics with user defined keys returned "key not found" errors. This issue has been fixed.
  • Output Generator
    • [3706, 3714] In deployments using the DRM module, generating the output of a Build Manifest for a map failed or took much longer than generating the same output directly from the map. This issue has been fixed.
    • [3954] The commons-collections4-4.0.jar in the Output Generator package was replaced with the commons-collections4-4.1.jar file to address Apache Commons Collections Security Vulnerabilities.
    • [3964] A missing file caused a "class not found" error when attempting to use an FTP command to access the conductor file. This has been fixed by adding the commons-net-3.3.jar file to the libs\common directory.
    • [3970] The "ixiasoft.document.locator" processing instruction was missing from the ditaval file when generating output from a build manifest that included ditaval files. This issue has been fixed.
  • Scheduler
    • [3903] The Scheduler did not correctly clean up connections after generating reports. This issue has been fixed.

Bug fixes

  • DITA CMS
    • [2634/2928/3936/3974/4047] The following issues were fixed in the DITA Map view:
      • When adding items such as keydefs to a map using drag and drop, the keydef was not added but no message was provided. Only DITA CMS objects (maps, topics, and images) can be added to a map using drag and drop. A new error message now provides more information to users trying to add a non-DITA CMS object (such as a keydef).
      • When the Change Status dialog was opened right above one of the buttons of the DITA Map view toolbar, this button was also activated. Clicking the Change Status action also activated the button on the DITA Map view. This issue has been fixed.
      • Adding topics to a bookmap sometimes resulted in an invalid structure. This issue has been fixed.
      • When a key was inserted into a map that contained a relationship table using Edit Variables, the key was inserted in aelement after theelement, which resulted in a broken map. This issue has been fixed so that theelement is inserted in a valid location in the map.
      • The Show Conditions command did not preview the correct topics when the map included subject scheme conditions. This issue has been fixed.
    • [3255] Importing images using the Import Images with Multiple Resolutions command also imported files such as the thumbs.db file. This issue has been fixed and these files are now skipped.
    • [3281] When Show Only Latest was clicked in the Search Results view, duplicate objects were included in the results. This issue has been fixed.
    • [3741/3895] The following issues were fixed for ditaval files:
      • The Create Ditaval and Edit Ditaval dialogs displayed the attribute names rather than the category names. This issue has been fixed.
      • The Copy Ditaval Reference action in the Ditaval view generated a file path with forward slashes, which caused import errors on Windows. This issue has been fixed.
    • [3914] When the Show/Edit Image dialog was resized to a smaller size, the Import, Set as Default, Delete, and Open buttons were hidden. This issue has been fixed so that these buttons remain visible when the dialog is resized.
    • [3956]* When a topic that contained references to non-DITA files such as PDF files or videos was imported, the non-DITA files were imported as resource objects of an undefined type, which resulted in them not being searchable from the Search view. This issue has been fixed and requires changes to the resource.xml file. See Updating an Existing DITA CMS v4.3 Deployment (Update Guide) for the procedure.
    • [3959] When all the map templates were moved into a folder under /system/templates/maps, it caused an error when a map was created. This issue has been fixed so map templates can be organized in subfolders instead of directly under the maps folder.
    • [3966] The thumbnail preview of an object would disappear when the cursor moved so users were unable to scroll the display. This issue has been fixed so the thumbnail display will remain open until another object is selected or the ESC key is pressed.
    • [3971] When a user attempted to share a saved query with a role, the query would not appear in the Shared > Roles folder. This issue has been fixed.
    • [4060] Working in the To-Do list with a grouping selected in the Select Grouping box generated multiple NullPointerExceptions. This issue has been fixed.
  • Dynamic Release Management
    • [3973/4027] When a user attempted to clone a DRM version with a title containing characters such as < or > or brackets (that is, {} and []), an error would occur. This issue has been fixed and all characters are now accepted.
    • [4028] Renaming a DRM version generated a NullPointerException error. This issue has been fixed.
    • [4091] When a topic contained a cross-reference to another topic and the title of the cross-referenced topic changed, the name of the cross-referenced topic displayed in the oXygen editor's Author mode was not updated with the new title. This issue has been fixed so the correct title is displayed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • None
  • Scheduler
    • [3906] The DITACMSActivityReport and the GenerateReviewOutputs jobs generated logs about unrelated tickets. This issue has been fixed.
  • Web Author
    • None
  • Documentation
    • [3556] The Dynamic Release Management Module User Guide now includes documentation about the DRM refactor feature.
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen® XML 18.x
  • XMetaL® Xmax™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.6.4205 and up
WCR Server
  • Apache Tomcat® 6.0.33 and up
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java™ JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported), 64-bit
  • Web Author Application:
    • Apache Tomcat® 6.0.33 and up
    • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS web platform
  • CMS Application Server:
    • GlassFish Server 4.x ( Java™ EE 7 Full Platform version)
    • Java JDK 8 u60 or above, 64-bit
    • Microsoft® .NET Framework 2.0 and .NET Framework 3.0
  • DITA CMS web platform application:
    • Apache Tomcat® 7 (7.0.11 and up)
    • Java JDK 8 u60 or above
  • Browsers:
    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™
Output Generator

Scheduler

  • Java™ 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java™ JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)

Build 4.3.33 - 20161215

 To view the instructions for updating to a new build, see the Update Guide

Important notes

Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in Updating an Existing DITA CMS v4.3 Deployment (Update Guide).

Major bug fixes

  • DITA CMS
    • [3950] Each time a local cache was refreshed, the system not only refreshed the existing objects in the local cache but also added other objects modified by other users to the local cache, which resulted in the local cache growing at an unexpected rate and eventually affecting performance on the local machine and TEXTML Server. This issue has been fixed.
    • [3972] When a topic was open in the XML editor and an image from that topic was locked, the image would appear as unresolved (image not found) in the topic. This issue has been fixed.

 

Bug fixes

  • DITA CMS
    • [1262] When using oXygen, releasing a topic shuffled the topic tab to the right if multiple topics were open. This issue has been fixed and the tabs remain in the original order.
    • [1903] In the Referable-Content view, the Oxygen Editor > Insert as Conref action was not always available. This issue has been fixed.
    • [3586] The Revision History dialog now persists its column widths once the user sets them.
    • [3639] Inserting taxonomy metadata in a topic generated a java.lang.NullPointerException in Oxygen 18. This issue has been fixed.
    • [3849] When users changed added columns in the Todo List view and organized the order of columns, this information was lost when the DITA CMS was restarted. This issue has been fixed.
    • [3854] When the DITA CMS was launched for the first time and the eclipse.ini file contained an initial preferences configuration, the DITA CMS was not restarted when the users clicked Apply. This issue has been fixed and the DITA CMS now restarts correctly.
    • [3876] After importing a map, changing the status of one of its topics reverted the value of the href in the map to the topic's original filename. This issue has been fixed.
    • [3880] In the Rename Project dialog, it was possible to click OK after clearing the project name in the text box. This issue has been fixed and specifying a project name is now mandatory.
    • [3924]* The pivotlanguages.xml configuration file contained an incorrect doctype declaration. This issue has been fixed and requires a configuration change, see Updating an Existing DITA CMS v4.3 Deployment (Update Guide).
  • Dynamic Release Management
    • None
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • None
  • Scheduler
    • None
  • Web Author
    • None
  • Documentation
    • None
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 18.x
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.6.4205 and up
WCR Server

 

  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported), 64-bit
  • Web Author Application:
    • Tomcat 6.0.33 and up
    • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)

Build 4.3.31 - 20161017

 

New features

DITA CMS 4.3 includes many new features. For the list and description of these features, please see the What's New in DITA CMS 4.3 document.

Note that the DITA CMS documentation was updated for 4.3. You can find the updated documentation at the following URL: http://archive.ixiasoft.com/en/products/dita-cms/documentation/4-3/.

Upgrading your deployment

To use the DITA CMS 4.3, you must upgrade the following components:

  • DITA CMS Content Store
  • DITA CMS Eclipse Client
  • Output Generator
  • Web Collaborative Reviewer
  • Scheduler
  • Web Author

For the upgrade procedure, see one of the following documents:

Known Issue

  • [3850] The DITA Map view does not refresh correctly after a key definition is removed from a map. To force the DITA Map view to display correctly, click the Refresh button.

Features

  • [1359] You can now use the Redline With function with localized content, which allows you to compare a map to a published version and highlight the additions and deletions in different colors.
  • [3390, 3559] (DRM-only) The Dynamic Release Management perspective has been enhanced. A new menu item, called Rename Version, has been added to the right-click menu. This new feature allows you rename a DRM version.
  • [3560] The Create New Instance dialog box in the DRM view has been enhanced so that the column widths automatically adjust to their contents.
  • [3624] Sequential localization model has been enhanced to support the incremental localization process. The incremental localization process allows you to start the localization process without having all the objects in the Authoring:done status (or the equivalent status in your deployment). For more information, see What's New in DITA CMS 4.3.
  • [3642] The Dynamic Release Management > Update to feature has been enhanced to perform a check to identify objects that have become orphaned when they were replaced by another version. A dialog box containing the orphaned objects is displayed from which you can click the Locate button. The Locate button opens a list of the objects in the Search Results view from which you can perform operations such as delete the orphaned objects.
  • [3688] DITA CMS now supports subject scheme maps for specifying enumeration values for conditional processing attributes. More information can be found in the What's New in DITA CMS 4.3 and DITA CMS User Guide.
  • [3718] The sequential localization method has been enhanced to support pivot language localization. Pivot language localization is an optional feature that allows the localization of objects from the Localization cycle. For more information, see What's New in DITA CMS 4.3.
  • [3751] The DITA Map view has been enhanced. You can now use the UP and DOWN keyboard arrows to navigate the list of previously open maps.
  • [3797, 3799] The user interface is now fully available in French and German.

Major bug fixes

  • DITA CMS
    • [3780] The Show Conditions tool in the DITA Map view was no longer displaying the applied conditions when clicked by the user. This issue has been fixed.
    • [3833] Users were unable to change the status of a map containing out-of-scope links. This issue has been fixed.

Bug fixes

  • DITA CMS
    • [3053] When you cloned a topic and selected either "Replace original component" or "Append to map" options, it caused the entire map to be refreshed and then collapsed the open elements. This issue has been fixed so that the view displays the changes without losing the focus on the location in the map where the change was made.
    • [3655] When a user who is not granted administrative rights to their computer attempted to generate a report package by clicking Help > Report DITA CMS Issue, it resulted in an access denied error since the files produced during the process were saved to disk. This issue has been fixed so the files are produced and zipped in memory and not saved locally.
    • [3739] The Edit Variable dialog box was displaying the variables and values inserted into the previously opened map. This issue has been fixed.
    • [3748] When two topics were compared using Compare With feature, the "Copy" buttons on the Compare tab's toolbar were disabled. This issue has been fixed.
    • [3790] When a user connected to a different Content Store, objects open while connected to the previous Content Store remained open. This issue has been fixed.
    • [3819] The adhoc PDF files generated when a localization kit was prepared were generated with the topics in the incorrect order. This issue has been fixed.
    • [3820] When attempting to branch an image, the new image in Authoring:work was not created. This issue has been fixed.
    • [3843] If a topic was reverted to a previous revision from another view while still open in the XML editor, the XML editor was not refreshed to display the correct revision of the topic. This issue has been fixed.
    • [3858] Clicking Retranslate From Source resulted in a java.lang.IndexOutOfBoundsException error. This issue has been fixed.
    • [3870] In the Change Status dialog box, if a user selected a preset comment before clicking the new status for the object and clicking Change, a message was displayed requiring a comment to be entered despite a preset comment being selected. This issue has been fixed.
  • Dynamic Release Management
    • [3520] When a map was imported containing topics with a .dita extension, the topics were imported with the .xml extension instead. This issue has been fixed.
    • [3615] The Version Filters tab on the Exclusion Filter Settings dialog box displayed the message “No filter specified or all filters are empty” instead of filtering by the selected criteria. This issue has been fixed.
    • [3717] It was possible to remove a DRM library despite being referenced by other DRM libraries. This issue has been fixed.
    • [3804] Access rights for new DRM features have been added to the configuration file.
    • [3831] If a new instance of an image was created and then changed, the image was not displayed correctly when it was opened. The unchanged image was displayed instead of the updated one. This issue is fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [3542] The catalog-dita-outgen.xml file will no longer be overwritten when you update the Output Generator.
    • [3683] Features based on a "track changes" functionality such as redlining did not work when Apache FOP engine was implemented as the PDF rendering engine. This issue has been fixed; however, the functionality will work slightly differently depending on which PDF rendering engine is implemented. When the Apache FOP engine is used, all "track changes" functionality will work, except the vertical markers in the left margin will not appear.
  • Scheduler
    • [3680] The daily reminder notifications did not include the Comments provided when a document was assigned to a user. This issue has been fixed.
  • Web Author
    • [3454] Web Author has been updated to support symbols. This issue requires a configuration change for existing deployment.
  • Documentation
    • None
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up (minimum)
DITA CMS Eclipse Client
  • oXygen XML 18.x
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.6.4205 and up
WCR Server

 

  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported), 64-bit
  • Web Author Application:
    • Tomcat 6.0.33 and up
    • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)

 

Build 4.3.7 - 20160429

Download Detailed Release Notes (PDF)

Important notes

  • The "Run in background" mode allows users to start an operation that may take some time to complete (for example, publish or localize) and still continue working with the DITA CMS. It should not be used to run multiple resource-intensive operations (for example, multiple localization operations) at the same time.
Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in the Detailed Release Notes.

New features

  • DITA CMS
    • [3221/3395/3401] You can now specify values for variables contained in the map template when you create a map.
    • [3300, 3346, 3352, 3354, 3358, 3430] You can insert keys into maps from a default list defined in a configuration file.
    • [3307] DITA CMS administrators can now configure a default custom Eclipse perspective for when users start DITA CMS for the first time. Instead of users needing to set up the DITA perspective and configure the connection information, these settings are configured by default and the user only needs to enter their credentials to log in. This custom perspective is launched by clicking a link from the Overview page.
    • [3308] DITA CMS administrators can now configure a set of profiling attributes that are available by default to all users using the oXygen XML Editor or Author in the deployment. These profiling attributes take precedence over the local values set in the Profiling/Conditional Text pane in Window>Preferences>oXygen XML Editor(Author).
    • [3309] DITA CMS administrators can now configure DITA CMS to display conditional text in oXygen XML Editor or Author and in PDF documents in different colors. The content highlighted in different colors allows users to easily see where conditions are applied.
    • [3336] You can now refresh the Dependencies view.
    • [3356] A new parameter was added to the localization configuration file so that you can set the workflow to skip the review status after localized content is imported and instead set the status to the next state in the workflow.
  • Dynamic Release Management
    • [3242] You can now export the tree view of products/libraries, releases, and versions in the Dynamic Release Management view to a .tsv file.
    • [3433] The library layer number is now displayed with the library layer name in the Create Product or Library dialog.

Major bug fixes

  • Dynamic Release Management
    • [3400/3402]: There were performance issues with the following actions in oXygen Author/Editor:
      • Opening a bookmap or topic in oXygen Author/Editor
      • Changing the status of the map when the map was opened in oXygen Author/Editor
      These issues have been fixed.

Bug fixes

  • DITA CMS
    • [1103] When you double-click an image in a topic to display the Show/Edit Image dialog box, a Locate button is now available. This button allows users to easily change the status of the image.
    • [3037] In the Search view, the list of users in the Last modified by dropdown list of the Limit to section did not show all the users. This issue has been fixed.
    • [3143] If the catalog file in /system/plugins/com.ixiasoft.dita.dtd did not contain a element for the public ID "-//IXIA//MODULE DITA Variables//EN", then an error appeared in the Error Log. This issue has been fixed.
    • [3158] The due dates for document assignments did not reflect the correct date when the timezone on the DITA CMS client's machine was set to UTC+1. This issue has been fixed.
    • [3159/3375]: Validating out-of-scope links did not detect errors in reltables. This issue has been fixed.
    • [3160/3330/3332/3341/3427] The following issues were fixed in the localization feature:
      • When localizing content from a previously localized map using the Concurrent localization feature, the revision numbers were not updated correctly, which resulted in a broken map. This issue has been fixed.
      • When a paragraph contained two inline elements and the translation for that paragraph resulted in the elements appearing in a different order, the auto-translation caused the attributes to appear on the wrong elements. This issue has been fixed.
      • If a map was localized after having been published multiple times previously, the resulting localized map acquired the first occurrence of the published version in the custom properties of the Authoring map, which resulted in incorrect information being displayed. This issue has been resolved, and the version of the latest published map is now stored in the custom properties.
      • When localizing a map, the previous localization and the new localization revisions appeared in the DITA Map view with broken references. This issue has been fixed.
      • Images with the "Needs Translation" flag were assigned the Localization:translated status directly when localized. This issue has been fixed, and the images are now in the appropriate status (e.g., Localization:tb translated).
    • [3245] When releasing a topic that contained duplicate IDs in the XMAX editor, the error message displayed was incorrect. This issue has been fixed and the following message is now displayed: "Document contains duplicate IDs".
    • [3248/3295/3313] The following issues were fixed in the import feature:
      • When multi-resolution images were imported, the originalFilename metadata was not added to the .image file. Since the system uses the originalFilename index to recognize images when they are re-imported, the lack of this index prevented the images from being updated when a map containing the multi-resolution images was subsequently imported. The Import Images With Multiple Formats wizard has been fixed to include the originalFilename and originalRelativePath metadata in the .image file.
      • Importing an SVG image generated an error similar to the following: "Unable to import image: C:\Dita-CMS Clients\eclipse-4.0-jre1.7.51-x86_64-4-2-29\svg10.dtd (The system cannot find the file specified)". This issue has been fixed.
      • In previous releases, when an object was imported, the access rights assigned to the user were not applied correctly. This issue has been fixed.
    • [3249]: The Search & Replace "all pages" feature only replaced content on the current page of the search results. This issue has been fixed.
    • [3276/3441] The following issues were fixed in the child intersection report (Compare With > Export Children Intersection):
      • When you generated a child intersection report in version 3.4, the report contained the authoring revision number of the reported child objects. In version 4.3, the revision numbers were replaced by "X". This has been fixed so that the report displays the authoring revision number again.
      • Generating the Children Intersection Report failed and created an InvocationTargetException. This issue has been fixed.
    • [3291] The DITA CMS now restarts automatically when users connect to another docbase.
    • [3297/3373] The following issues were fixed in the snapshot feature:
      • When creating a snapshot, the first comment in the Revision History was "created text object". This issue has been fixed and the first comment is now "Created Snapshot".
      • When users double-clicked a snapshot, it was opened in the Eclipse text editor. This issue has been fixed and snapshots are now opened in the default XML editor.
    • [3318] The revision history now provides the revision number, language, and date from which a localized object was created.
    • [3321] If a user had only the Reviewer role, and the Reviewer role had only one active status for each document type, opening the Todo List view for this user generated the error "Load Assignment Job has encountered a problem". This issue has been fixed.
    • [3329] If the "Append topic to current map" option and "Save Settings" button were selected when a new topic was created, the "Append topic to current map" option was not saved as being selected in the settings. This issue has been fixed.
    • [3361]: After merging a new branched map with content in authoring, the following error message was displayed when users tried to open the map in authoring:
      Merge failed: an error occurred while changing a document’s status:
       
      com.ixiasoft.cms.exceptions.IxiasoftConfigurationException: Unable to retrieve state draft for cycle Authoring
                     at com.ixiasoft.cms.configuration.status.Status.(Status.java:74)
      This issue has been fixed.
    • [3365]: When exporting search results to a .tsv file, the "Last Mod by" and "Locked by" columns provided the user information in a different way than the Search Results view. This issue has been fixed.
    • [3366] When the content of a conref contained a reference to an image, the image was not displayed in XMetaL. This issue has been fixed.
    • [3367] The order of the folders in the Dependencies view is now sorted by logical order; therefore, it can no longer be sorted by clicking on the column headers.
    • [3384/3385] The following issues were fixed in the Build Manifest feature:
      • When creating a Build Manifest, if the user did not select the "Open in default editor" option, the following error was displayed: "At least one valid output type must be specified." This issue has been fixed.
      • The Create Build Manifest command always created the Build Manifest in English, regardless of the @xml:lang attribute in the template. This issue has been fixed and the Build Manifest is now created in the language specified by the template.
    • [3418] In the Generate Output dialog, the Save Settings button will now be grayed out for topics, since settings can be saved for maps only.
    • [3439]: It was possible to change the root ID of the map and then release it. This issue has been fixed and this is no longer possible.
    • [3445]: The Synchronize Image Thumbnails preference was not saved with a restart of Eclipse. This issue has been fixed.
  • DITA CMS Administration plugin (TEXTML Administration perspective)
    • [3262] The options listed in the New Type on list in the Access Manager did not include Snapshot and Build Manifest. These options have been added to the list.
  • Dynamic Release Management
    • [3269] Importing a map in two versions and specifying the Update existing documents option created a false conflict when the versions were synchronized. This issue has been fixed.
    • [3303] When an Exclusion Filter Setting was created and a Status Filter was used to exclude versions in Authoring:closed, the closed versions were still displayed in the Select Versions dialog box. This issue has been fixed.
    • [3312, 3316]* Auto-translated topics were not being set to the correct status. This issue has been fixed. This change requires configuration updates. See the Detailed Release Notes for more information.
    • [3319]* You can now run the Clone Version command on versions that are closed. This change requires configuration updates. See the Detailed Release Notes for more information.
    • [3320] Refactoring multiple images or topics at same time with the Run in background option caused exceptions. This issue has been fixed.
    • [3333] The System Comments in the Revision History now provides additional details, such as the ID and version of objects to which the action was applied.
    • [3337] It was not possible to remove a label that had been assigned to an object. This issue has been fixed.
    • [3339] The algorithm to select a container part always selected the same part, which sometimes caused collisions when users added objects to containers at the same time. This issue has been fixed.
    • [3357] When trying to change the status of a library version from "Closed" to "Development" with the "Substantial Change" option selected, an error occurred. This issue has been fixed.
    • [3362] When the DITA CMS Eclipse Client configured with a custom initial perspective automatically restarted after switching to DRM, the preferences set were not saved. This issue has been fixed.
    • [3364] When a new instance of a resource object was created, the original object and the newly created object were not being found using a search for resource objects. This issue has been fixed.
    • [3376/3382/3389] The following issues were fixed in the XMetaL XML Editor when working in DRM:
      • When inserting an image using oXygen XML Editor, the images were not resolving even after being added to the appropriate DRM Product/Release/Version. This issue has been resolved.
      • When a topic was saved in XMetaL XML Editor, the content from all @href attributes were cleared unless both the @scope and the @format attributes had a value. This issue has been fixed.
      • When opening a topic from the Search Results view in XMetaL XML Editor, an error is displayed. This issue has been fixed.
    • [3399] Opening maps in the DITA Map view took a long time and many "using cached properties" entries were written to the Eclipse debug log, even when opening small maps. This issue has been fixed.
  • Web Collaborative Reviewer
    • [2848] Changes made in a map opened in Collaborative Reviewer were not appearing in Web Collaborative Reviewer due to an error in how the review PDFs were named. This issue has been fixed.
  • Output Generator
    • [3250]*: Generating the output for a Build Manifest defined for more than one language generated the output for the default language only. This issue has been fixed and requires a configuration change. See the Detailed Release Notes for more information.
    • [3260/3294] The following issues were fixed in the Output Generator when generating the output of DRM maps and topics:
      • The Output Generator processed the same topics multiple times, which caused performance issues in large maps. This issue has been fixed.
      • The Output Generator processed images to resolve keyrefs, which is not necessary and caused performance issues in large maps. This issue has been fixed.
    • [3298] The Output Generator logged unnecessary INFO messages when processing images, creating very large wrapper.log files. This issue has been fixed.
    • [3314] The encrypt program did not run properly in the following cases:
      • (On Windows only) If the path to the Java executable contained a space
      • If the password contained special characters that could be interpreted by the shell (for example, <, >, |, &, and &&)

        These issues have been fixed. IXIASOFT recommends that you enclose the password in double quotes if the password includes special character. See the Output Generator Installation Guide for more information.

    • [3324] New batch files are now available to run the DITA-OT integrator.
    • [3328] The flatten target did not handle non-English languages correctly. This issue has been fixed.
  • Scheduler
    • [3315] The encrypt program did not run properly in the following cases:
      • (On Windows only) If the path to the Java executable contained a space
      • If the password contained special characters that could be interpreted by the shell (for example, <, >, |, &, and &&)

        These issues have been fixed. IXIASOFT recommends that you enclose the password in double quotes if the password includes special character. See the Scheduler Installation Guide for more information.

    • [3326] Too many irrelevant JACORB entries were appearing in the Scheduler's wrapper.log. To fix the issue, a new argument was added (jacorb.log.default.verbosity=0) in the wrapper.conf file to prevent these entries from appearing in the wrapper.log.
    • [3327] Errors were not logged as ERROR in the wrapper.log file for the Scheduler. This issue has been fixed.
    • [3349] Scheduler was missing the batik jar file, which caused issues with images. The %SchedulerDir%/conf/classpath.conf file was modified to solve this issue. This file is updated automatically when you update Scheduler.
  • Web Author
    • [3222] The lastmodtime custom property did not get updated when users changed the status of a document in Web Author. This issue has been fixed.
    • [3286] If two topics contained cross-references to and from each other, it caused and error when one of the topics was opened in Web Author. This issue has been fixed.
    • [3293] oXygen displayed two pairs of tags for conrefs when full tags mode was enabled. This issue has been fixed.
  • Documentation
    • None
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.0 and up
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.6.4188 and up
WCR Server

 

  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported), 64-bit
  • Web Author Application:
    • Tomcat 6.0.33 and up
    • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)

 

Build 4.3.6 - 20160329

Bug fixes

  • DITA CMS
    • [1409] When a nested map was cloned with the Replace original component checkbox selected, the original nested map was not replaced by the clone. This issue has been fixed.
    • [1810/3065/3110/3214/3215/3233] The following issues were fixed in the import feature:
      • When a topic containing two identical IDs was imported with the Update existing documents checkbox selected, the import completed successfully; however, the duplicate IDs should have caused the import to fail. The import functionality has been fixed so that it validates the document before it is imported. If duplicate IDs are identified during the import process, an error is generated and the import fails.
      • When an attempt was made to import a composite topic (a topic with the element) containing a single topic, the process to extract and import the topic failed. This issue has been fixed.
      • When importing a topic that contained internal references (that is, a reference to an element in the same topic), the internal references were not imported correctly. This issue has been fixed.
      • When importing a map, the keyrefs that were defined in the source map were transformed into keyrefs that pointed directly to the target topic in the container. This issue has been fixed. The keyrefs now point to the same key as in the source, but the key definition is updated to point to the topic in the container.
      • Importing a map removed the @keys attribute from the element and replaced the @href attribute with a @keyref attribute. This issue has been fixed. The @keys and @href attributes are now kept as in the source file.
      • When a topic containing nested topics or cross-references to elements within itself was imported, the cross-references were not defined correctly. This issue has been fixed.
    • [2360/3223] The following issues were fixed in the localization feature:
      • You can now specify the status that localized documents will be in after a Retranslate from source operation. This feature applies to the Sequential Localization Manager only and requires configuration updates. See the DITA CMS Administrator's Guide for more information.
      • When a map containing nested maps was localized, status changes for topics in the nested maps did not result in the correct change of status for the parent objects. This issue has been fixed.
    • [3099] Attempting to move an object from a sub-map nested in a map to a location in the parent map was not possible. This issue has been fixed.
    • [3144] When users selected multiple maps nested in a map and attempted to change their status, it resulted in an error message and users were unable to change the status of the selected objects. This issue has been fixed.
    • [3161] In previous releases, the Manage Categories and Labels button was always greyed out in the Assign Labels dialog. This issue has been fixed, and the button is now enabled if users have the appropriate access rights and are opening the Assign Labels dialog using the right-click Assign Labels option.
    • [3191] You can now add taxonomy terms to objects in the Authoring:Done status (or equivalent in your deployment). See the DITA CMS User Guide for more information.
    • [3192] When an attempt was made to release a sub-tree which contained the same topic multiple times, it resulted in an error. This issue has been fixed.
    • [3198] (XMetaL only) It was not possible to save or release a topic after inserting a keyword element. This issue has been fixed.
    • [3202] Authoring revision number has been added to snapshot metadata.
    • [3209] When performing a search for an object in the Published collection, the search results incorrectly contained items from the Archive collection. This issue has been fixed.
    • [3210] Personal queries did not load and execute properly. This issue has been fixed.
    • [3213] The Generate Topics from Stubs feature did not support more than one sub-folder for the topic templates. This issue has been fixed.
    • [3217] The Save As dialog box in the Output Generator did not display the .zip files existing in the folder. This issue has been fixed.
    • [3219] The logout process of the CMS API sometimes failed because of currently running background threads. This issue has been fixed and the API now waits (up to 1 minute) for background processes to complete before exiting completely.
    • [3226] Some error messages were confusing or not clear. They have been rewritten for clarity.
    • [3256] DITA CMS now handles the removal of the Create Resource menu item in the eclipseui.xml configuration file. This build also includes a new template file, eclipseui_template.xml, that you can use to customize your eclipseui.xml file. See the DITA CMS Administrator's Guide for more information.
    • [3257] The Show Preview view did not display changes made locally by the author. The topic had to be released for the changes to be visible in the Show Preview view. This issue has been fixed, and changes are now displayed when the author saves the topic.
    • [3267] In the DITA Map view, adding the Last Mod Date column to the view columns generated a NullPointerException. This issue has been fixed.
  • DITA CMS Administration plugin (TEXTML Administration perspective)
    • [1339] In the Manage Users dialog, an error occurred when trying to lock a user. This issue has been fixed.
  • Dynamic Release Management
    • [2564] It is now possible to move an object from a product to a library.
    • [3033] If an object in a source version contained XML comments, during the Synchronization merge these XML comments were added to the target object, but the target object was not flagged as having changed. This issue has been fixed and the XML comments are now flagged as changes and are displayed in the Review panel.
    • [3092] The Dynamic Release Management view was not refreshed correctly after actions were applied to libraries. This issue has been fixed.
    • [3183] Importing content when the Update existing documents option was selected created issues for objects that were not in a lockable state. This issue has been fixed. You must now make sure that the documents are in a lockable state before reimporting them. If you try to import content with the Update existing documents option selected but the objects are not in a lockable state, an error message is returned.
    • [3193/3194/3199] The following issues were fixed in the Library Dependency Editor:
      • The Debug menu options were displayed in the right-lick menu of the Library Dependency Editor. This issue has been fixed.
      • The message displayed when hovering the mouse over a library version in the Library Dependency Editor was confusing when there were no additional versions for this library. This issue has been fixed.
      • A Refresh button is now available in the Library Dependency Editor.
    • [3200] It was not possible to add a library (e.g., Library C) to another library (e.g., Library A) if it was already a child of that library (i.e., Library C is a child of Library B, which is a child of library A). This is now possible if the top library (e.g., Library A) is the focus library in the Library Dependency Editor.
    • [3203] When updating a library, if keys were missing, an error message was provided with the option to locate the missing keys, but the Locate button did not work and did not display the IDs for the missing keys. This issue has been fixed.
    • [3211] It is no longer possible to update a topic in another version if the topic is not in a lockable state in that version. Now, if the topic is not in a lockable state, the topic is disabled.
    • [3231] Creating a version based on a tag generated a NullPointerException if the version did not have a library. This issue has been fixed.
    • [3236] When adding objects to a version, the objects were added to a container part even if the container part was not in a lockable state. This issue has been fixed.
    • [3243] When cloning a version from another release, theparent.filenamecustom property of the newly created version did not get updated. Therefore, when searching for the version's parent, the original release was returned. This issue has been fixed.
    • [3244/3254] The following issues were fixed for the XMetaL editor:
      • When opening a topic in XMetaL from the DITA Map view, the images did not appear in XMetaL. This issue has been fixed.
      • Images could be added to a topic or map even when the topic or map was not in the same DRM version as the image. This issue has been fixed and the following message is now displayed: "Some of the objects to insert are not of the same version(s) as the topic. Do you want to add the objects to the version?"
      [3259] Running the Show Preview operation on a topic did not show the images in that topic. This issue has been fixed. Images are now previewed for topics that belong to a map opened in the DITA Map view.
    • [3265] It was not possible to clone libraries with child layers. This issue has been fixed.
    • [3268] When using the Synchronize With right-click menu, the Select Target Version dialog did not show items in the collapsed sections. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [3252] The IXIASOFT DTDs were not up to date in the com.ixiasoft.dita.dtd plugin. This issue has been fixed.
    • [2798] The and elements did not resolve when generating the output of DRM content. This issue has been fixed.
  • Scheduler
    • None
  • Web Author
    • [3196/3212] The following issues were fixed in the Editing Context menu:
      • The Editing Context menu displayed incorrect context names in DRM deployments. This issue has been fixed.
      • The Editing Context only displayed the version for libraries, instead of the library names and versions. This issue has been fixed.
  • Documentation
    • None
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.0 and up
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.6.4188 and up
WCR Server

 

  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported), 64-bit
  • Web Author Application:
    • Tomcat 6.0.33 and up
    • Java JRE 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51, 1.7.0-80 and up, or Java 1.8.20 and up (this version contains the fix for the singleton jacorb problem)