DITA CMS 4.2 Release Notes

Build 4.2.53 - 20160919

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.2 Deployment (Update Guide).

 

An important change to the rootClass index must be made in the Index Definition in this release. Please follow the instructions provided in Updating an Existing DITA CMS v4.2 Deployment (Update Guide).

 

Reminder:

The Detailed Release Notes have been replaced by Updating an Existing DITA CMS v4.2 Deployment (Update Guide). This new guide not only describes the changes you must make to the components' configuration files to support the features and fixes made in the build release, but also provides instructions on how to bring your deployment up to date to a more current build release.

Features

  • [2659] The Ditaval view has been enhanced so that you can select multiple ditaval files and delete them.
  • [3126] The Dependencies view has been enhanced so that the contents of the columns can be sorted by clicking on the column headers.
  • [3616] The Recent Documents pane in the Documents view has been enhanced so that the documents are now listed by default in chronological order with the most recent displayed at the top of the list.
  • [3703] The Build Manifest window has been enhanced. The output types in the Output types pane are now sorted alphabetically.
  • [3720] Snapshots have been enhanced to warn users when they are attempting to create a new snapshot using the same version label as an existing snapshot and to allow them to enter a new version label.

Known Issues

  • [3774] When a map is created, it is opened in the DITA Map view with its elements collapsed instead of expanded as was the previous default. This is a known issue in this release and will be addressed in a future release.

Major bug fixes

  • DITA CMS
    • [2695] When a ditamap containing a broken submap (a nested map with invalid XML) was open in the DITA Map view, it caused the DITA Map view to become unresponsive. This issue has been fixed so the broken submap is not displayed in the DITA Map view and an error is reported in the Error Log view.
    • [3700] When you attempted to clone a topic that contained the following sequence of characters "{{", then operation would fail. The failure occurred because the sequence of characters was identified as an unclosed map template variable. This issue has been fixed.
    • [3713] While generating output from a map, in some cases some of the referenced objects were not saved to the output generation folder resulting in an incomplete output and errors in the logs. This issue has been fixed.

Bug fixes

  • DITA CMS
    • [715] Two issues were occurring when you cloned topics:
      • When a topic was cloned when its parent map was not locked, the cloned topic was created but did not replace the original topic in the map. This issue has been fixed so the Clone feature is disabled when the map is not locked.
      • If you selected multiple topics to clone and selected the Replace original component checkbox, only the first instance was replaced. This issue has been fixed.
    • [2898] Adding or removing topics from the ditamap in the DITA Map view caused the entire map to be refreshed and 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.
    • [3440, 3467]* When a search was performed for content in a referable-content topic containing multiple referable-content elements with IDs, only one instance was found. This issue has been fixed and requires a configuration change, see Upgrading the DITA CMS to 4.2.
    • [3503] A performance issue was discovered with relationship tables containing a large number of references and rows. This issue has been fixed.
    • [3592] When the Search Results view contained results from a previous search and then the Locate button was clicked followed by the results being exported, the export incorrectly included the results from the previous search. This issue has been fixed.
    • [3623] When specifying perspective names in the system/conf/eclipseui.xml file, you can now use wildcards to specify multiple perspectives in a single line. For example, "com.ixiasoft.dita.eclipse.gui.perspective.*" will match all the DITA CMS perspectives.
    • [3645] When using Node-based localization method, users were allowed to localize a map from the Published cycle despite having more current revision in the Authoring cycle. This issue has been fixed so this is prevented and a warning has been added to alert users.
    • [3677] When a self-referencing keydef was defined in a topic and the topic was saved or released, it resulted in ajava.lang.StackOverflowErrorerror and caused the DITA CMS Eclipse Client to become unresponsive. This issue has been fixed.
    • [3692] During the process of hiding a menu for a simplified user interface (UI), a menu from a plug-in would fail to return an ID, which resulted in a NullPointerException error. This issue has been fixed.
    • [3696] When a table was inserted into a topic as a conref using the oXygen XML Editor's Author view, the tgroup element was inserted with an invalid value for the cols attribute (). This issue has been fixed.
    • [3701] If a special character such as a trademark was included in the topic or map title, an error would occur. This issue has been fixed.
    • [3721] In a few cases an unhandled event loop exception was generated when an image was imported. This issue has been fixed.
    • [3726] When a topic was imported with the "Update exisitng documents" option selected, it resulted in a java.lang.NullPointerException error. This issue has been fixed.
    • [3731] When XSLT was applied to topics using the Apply XSLT functionality on the Search and Replace dialog box opened from the Search Results view, the transformation resulted in unnecessary elements being added to the topics. This issue has been fixed.
    • [3740, 3742] When a key was added to a submap of a ditamap open in the DITA Map view, the submap would replace the ditamap in the DITA Map view, which was the incorrect behavior. This issue has been fixed so that the parent ditamap remains in the view while the key is added to the submap.
    • [3784] In the DITA Map view, the list box containing the titles of the recently opened maps displayed additional information (cycle, language, and revision information) that was obscuring part of the title. This issue has been fixed so up to 40 characters of the title are displayed.
    • [3839] Performance issues would occur when a ditamap containing numerous submaps was opened in the DITA Map view. This issue has been fixed.
  • Dynamic Release Management
    • [3657] Under unusual circumstances, locking a resource object may result in a NullPointerException error. This issue has been fixed.
    • [3736] In some cases, when topics containing cross-references were imported, the href attribute was not converted to a keyref. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [3661] The temporary job folder stored under the temp folder was not being deleted at the end of the output process of a build manifest. This issue has been fixed.
    • [3664] When a document included SVG images with a doctype containing http://www.w3.org, DITA CMS and Output Generator would try to fetch the DTD from the website for each image. A fix has been made to prevent DITA CMS and Output Generator from contacting the site, which also results in improved performance for processing SVG images.
    • [3719] When an output was generated from a map with a exceptionally long title, the resulting filename for the .zip file could potentially be up to 200 characters long. This issue has been fixed so the filename for the .zip file is limited to a maximum of 100 characters
  • Scheduler
    • [283] The temporary files produced by the Generate Review PDF job were not being deleted from the %SchedulerDir%/temp/scheduler/review folder. This issue has now been fixed.
    • [3673] The /scheduler/sentitems/ directory was not being automatically created in the Content Store, which resulted in the same email messages from the Bulletin Board broadcast feature being continually sent to the project members. This issue has been fixed and resolves the Known Issue stated in the Release Notes for build 4.2.45. The GarbageManJob has also been modified to delete documents older than 7 days from "/scheduler/sentitems/" directory.
  • 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 17.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.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.2.45 - 20160718

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.2 Deployment (Update Guide).

 

IMPORTANT CHANGE TO THE IXIASOFT DOCUMENTATION SET

The Detailed Release Notes have been replaced by Updating an Existing DITA CMS v4.2 Deployment (Update Guide). This new guide not only describes the changes you must make to the components' configuration files to support the features and fixes made in the build release, but also provides instructions on how to bring your deployment up to date to a more current build release.

Known issue

If you are using the Bulletin Board broadcast feature (see bug 2520) and the same email message is continually sent to the project members, this means that the sentitems collection is missing from the Content Store.

To solve this issue:

  1. Open the TEXTML Administration perspective.
  2. Connect to the server and Content Store.
  3. Navigate to the Repository\system\scheduler directory.
  4. Right-click scheduler and select Create Collection.
  5. In the Add Collection dialog, enter sentitems.
  6. Click OK.

A bug was opened to resolve this issue (3673).

Features

  • [3598] The Ditaval view has been enhanced. A new column was added by default to display the DITAVAL's filename.
  • [3599] The Ditaval view has been enhanced with a new option in the right-click menu which allows users to open the DITAVAL in read-only mode.
  • [3600] The Edit Ditaval dialog box has been enhanced to clearly indicate that the Action column is editable to allow users to select whether the action is include or exclude.

Major bug fixes

  • DITA CMS
    • [3593] Objects containing &nbsp entities could break the Xliff transformation processing of the concurrent localization manager. This issue has been fixed.
  • Dynamic Release Management
    • [3493] When importing a map containing elements, the elements disappear from the map, whether they were referencing topics already in the map or other topics. This issue has been fixed.
    • [3632] When a user created a topic and the Append to current map option was selected but a map was not open in the DITA Map view, the topic was created as an "orphan" (without being associated to a map). This issue has been fixed. Now the Append to current map option is disabled when a map is not open in the DITA Map view.
  • Output Generator
    • [3608] When generating output using the Export[DRM] output format, the keydefs were not handled correctly. This issue has been fixed.

Bug fixes

  • DITA CMS
    • [1391] When a user attempted to set conditions on an unlocked map, no action occurred. A new message has been added to warn users that the map must be locked before conditions are set.
    • [1442] Issues occurred during sequential localization when generating multiple localization kits for different languages for a map and the jobs were run in the background. This issue has been fixed so multiple Prepare Localization Kit jobs can be run in the background. The localization kit is created as a compressed (.zip) package including a timestamp (yyy-mm-dd_hhmmss) in the file name.
    • [2520]* When a user clicked Broadcast on the Bulletin Board view, the posted message was not being emailed to the team. This issue has been fixed and requires both a configuration change for existing deployment and the Scheduler to be updated to the current build release, see Updating an Existing DITA CMS v4.2 Deployment (Update Guide).
    • [2769] When a user closed folders in the Ditaval view and then refreshed the view, the closed folders would reopen. This issue has been fixed so that when the Ditaval view is refreshed or closed, the items in the view will preserve their expanded or collapsed state as set by the user.
    • [3010] Some labels in the user interface where still appearing in English when DITA CMS was configured to appear in Japanese. This issue has been fixed.
    • [3322] Objects in Localization:review were being updated during sequential localization. This issue has been fixed so that objects can only be updated when the status of the object is in a status configured with the attribute initial="true" or type="end".
    • [3371] The menu items in the oXygen context menu in Text mode remained in English instead of the selected language. This issue has been fixed.
    • [3403]* When a snapshot was created from content in localization, the status of the snapshot was still Authoring:review. This issue has been fixed so it is now Localization:review and a warning has been added to alert users when a configuration error is occurring. This fix requires a configuration change for existing deployment, see Updating an Existing DITA CMS v4.2 Deployment (Update Guide).
    • [3404] During the process of preparing a localization kit of the localized map, the PDF generated during the process would contain duplicates of the topics. This issue has been fixed.
    • [3406] The DITA Map view displayed another map after Refresh was clicked. This issue has been fixed.
    • [3461] Changes have been made to the Branch and Clone features. Branched objects will now contain the same ID as their source objects. Clone objects must now contain unique IDs so the option Use same ID has been removed form the Clone dialog box.
    • [3525] In rare cases, the Search Results view was not being refreshed in time to reflect changes committed by another users so if a topic was opened from the Search Results view the previous revision of the topic was opened instead of the current one. This issue has been fixed.
    • [3554] The speed at which the Generate Output dialog box opened was adversely affected when the Content Store contained a large number of DITAVAL files. This issue has been fixed.
    • [3555] Each time a topic was opened in XMetaL XMAX the message "the file has been modified..." appeared. This issue has been fixed.
    • [3565] When you performed a search containing a selection from the Assigned to or Role lists in the Limit to pane and then saved it as an XML query, the selection was not saved in the query. This issue has been fixed.
    • [3569] In some cases, a java.lang.nullpointerexception error would appear when the Revision History was opened. This issue has been fixed.
    • [3585] Performance issues were occurring with the ValidatePushConrefsInMap trigger. This trigger has been optimized.
    • [3590] When the Clean All Views button was clicked on the main toolbar, the DITA Map view was not cleared. This issue has been fixed.
    • [3595] Error messages were not being displayed when issues occurred during the configuration synchronization of the login process. This issue has been fixed.
    • [3609] When a user clicked Rename Project in the Project Management view and then clicked Cancel, the name of the project was deleted. This issue has been fixed.
    • [3610] When users clicked Add Message on the Bulletin Board, the Visible checkbox on the Message dialog box had no effect. In this release this checkbox has been removed.
    • [3611] When deleting multiple objects, the progress bar on the dialog box did not display the progress of the deletion. This issue has been fixed.
    • [3612] When a user created a branch of a map in the Authoring:done status, the source map was overwritten by the branch. This issue has been fixed.
    • [3614] When a user opened the Revision History for a map and attempted to view a past revision, it resulted in a NullPointException error. This issue has been fixed.
    • [3618] A "String index out of range: -1" error was occurring in the project Management view when the project had assignments but did not have one for the role that is defined as the project coordinator role. This issue has been fixed.
    • [3626] When an object was reverted to a previous revision, the revert operation was not listed in the Recent Operations pane of the Documents view. This issue has been fixed.
    • [3645] Users were allowed to localize a map from the Published cycle despite having more current revision in the Authoring cycle. This issue has been fixed so this is prevented and a warning has been added to alert users.
    • [3653] When an error existed in a condition in the accessrights.xml configuration file, the condition was mistakenly evaluated to true. This issue has been fixed so that if an error exists in the condition it evaluates to false and a warning appears in the Eclipse log view to alert users to the error.
  • Dynamic Release Management
    • [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.
    • [3574] The Lock, Release, and Replace With Server Version buttons have been added to the Dynamic Release Management perspective.
  • 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 17.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.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.2.38 - 20160615

Download Detailed Release Notes (PDF)

Important notes

Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in the Detailed Release Notes.

 

Bug fixes

  • DITA CMS
    • [3180] In the Assignments dialog box, the list of users that appeared in the Assignee pane included deactivated users. This has been fixed so that deactivated users no longer appear in the Assignee pane unless they are still assigned to a document.
    • [3229] Attempts to re-import an image with the same file name and format as an existing image in the Content Store would fail. This issue has been fixed.
    • [3347] The list of roles displayed in the Role list in the Limit to pane on the Search view did not contain the full list of roles configured in DITA CMS. This issue has been fixed.
    • [3360] The Insert Variable dialog box has been enhanced so the variables are organized by the map in which they are defined and can also be filtered by name or value.
    • [3370] When DITA CMS was started in Japanese, unnecessary error messages would appear in the Error Log view. This issue has been fixed.
    • [3420] The labels for DITA CMS > Label Configuration in the main menu, the Manage Label Configuration button on the main toolbar, and the Manage Label Configuration dialog box have all been changed to Configure Labels.
    • [3457] Enhancements have been made to the Referable-Content view:
      • You can now sort the contents of the columns by clicking on the column headers.
      • A new feature called Copy Element ID has been created to allow you to copy the element ID (displayed in the element ID column) from the selected referable-content topic. For more information, see DITA CMS User Guide.
      • A new right-click menu has been added to contain the following options: Copy ID, Copy Element ID, and Copy Reference.
    • [3477] When an object was released, the comments in the Choose a previously entered comment list in the Release dialog box were sorted in chronological order with the most recent comment at the bottom. In this release, this order has been changed so the most recent comments appear at the top of the list.
    • [3480] When UPDATE_EXISTING=true was specified in the import.properties configuration file, it was not being applied during the import process because the value was being overridden in the Import dialog box by the Overwrite existing resources without warning checkbox. This issue has been fixed so the value set in the import.properties configuration file overrides the value set in the dialog box.
    • [3496] A warning has been added to DITA CMS to inform users when they attempt to insert a cross-reference in an invalid location using the Oxygen Editor right-click menu available from the views.
    • [3541] In the process of generating an output, the focus does not return to the Generate Output dialog box after a ditaval is selected preventing a user from completing the process using the keyboard. This issue has been fixed.
    • [3562]* When the new feature that allowed administrators to restrict the visibility of status options by group was implemented, the statuschange method was omitted from the accessrights.dtd, which caused a validation error when the statuschange method was added to the accessrights.xml configuration file. This issue is fixed and requires a configuration change for existing deployment. See the Detailed Release Notes.
  • Dynamic Release Management
    • [3518] During localization, the trademark element () was being removed from content. This issue has been fixed.
    • [3550] After clicking the Resolve Keys button in the DITA Map view, java.lang.OutOfMemoryError: Java heap space error would occur in certain cases, which resulted in the need to set a high value for the maximum Java heap size (-Xmx) in the eclipse.ini file. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [3513] A performance issue was discovered in DRM deployments in the process for resolving keyrefs during output generation. This issue has been fixed.
    • [3453] Output Generator did not retrieve user parameters set in the Generate Output dialog box when they were left at their default values. This issue has been fixed.
  • Scheduler
    • [3484] The DailyReminder job fails while generating the second email notification. This issue has been fixed.
  • Web Author
    • None
  • Documentation
    • [3469] The sample code in the "extract-images" section of the Output Generator Administrator's Guide was not clear. This issue has been fixed and the documentation was updated.
  • CMS Application Server
    • None

Requirements

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.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.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.2.34 - 20160516

Download Detailed Release Notes (PDF)

 

Important notes

If you created custom Build Manifest templates using DITA CMS version 4.2.31 or earlier, you need to add a new element to your templates, otherwise you will get the following error when creating a Build Manifest based on this template:

The content of element type "globals" must match "(shortdesc,mode,locstatusend,mapref,languages,rootcontext,ditaval,properties,notify?).

If you are using the standard DITA CMS Build Manifest template (that is, /system/templates/bmanifests/build-manifest.bmanifest), you do not need to add the element since it will be done automatically.

See the Detailed Release Notes for more information.

Major bug fixes

  • Dynamic Release Management
    • [3444] It was possible to remove library versions containing objects referenced by a parent library from the parent library, thus breaking the references in the objects of the parent library version. This issue has been fixed.
    • [3460] When working in a clone version, the new parts that were created had duplicate numbers in their titles. This issue has been fixed.
    • [3498] An 'unhandled event loop exception' error was occurring when a new map instance was being created. This issue has been fixed.
  • Output Generator
    • [3452] Referenced content in a referable-content topic in DRM was not being resolved well in Dita2pdf output. This issue has been fixed.

Bug fixes

  • DITA CMS
    • [3017] The pop-up used to display the contents of a field displayed truncated content instead of its entire contents. This issue has been fixed.
    • [3413] Cross-references from one element to another within a topic were not being displayed correctly. This issue has been fixed.
    • [3419]* The element in the Index Definition has been updated with two new entries, CreationDate and CreationTime, to improve performance. See the Detailed Release Notes for more information.
    • [3470] Conkeyrefs were not resolved correctly when they were contained in conref. This issue has been fixed.
    • [3490] The ability to drag an image onto a keydef to create a reference to it was not available. This issue has been fixed.
  • Dynamic Release Management
    • [3491] When a keydef referencing a topic was created in DRM, it was incorrectly created with an @href instead a @keyref to the ID. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [3458] It is now easier to specify the DITA-OT catalog when installing a new version of the DITA-OT. See the Output Generator Administrator's Guide for more information.
    • [3488] When generating the output of a snapshot, the .snapshot file is now packaged with the source content in the /temp folder.
  • 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 17.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.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.2.33 - 20160316

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.
    • [3346, 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/3355] 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.

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.
    • [3460]: In rare cases, creating a new instance of a version could create invalid DRM versions. Container parts in these invalid versions were created with bad titles (part numbers were duplicated in the titles). This new build corrects the initial problem. Please contact IXIASOFT Support if you have encountered this issue.

Bug fixes

  • DITA CMS
    • [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.
    • [3159/3375]: Validating out-of-scope links did not detect errors in reltables. This issue has been fixed.
    • [3330/3332/3341/3427] The following issues were fixed in the localization feature:
      • 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).
    • [3249]: The Search & Replace "all pages" feature only replaced content on the current page of the search results. This issue has been fixed.
    • [3441] Generating the Children Intersection Report (Compare With > Export Children Intersection) failed and created an InvocationTargetException. This issue has been fixed.
    • [3373] 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.
    • [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.
    • [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.
    • [3385] 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.
    • [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
    • [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.
    • [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.
  • 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.
  • Scheduler
    • [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
    • [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.
  • Documentation
    • [3240]: The documentation did not include a description of the error icon displayed in the RelTable editor when a reltable linked to topic that could not be found in the Content Store. This issue has been fixed, and the icon is now described in the DITA CMS User Guide.
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.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.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.2.31 - 20160316

Download Detailed Release Notes (PDF) 

Important notes

Some mandatory changes to the configuration must be made in this release. Please follow the instructions provided in the Detailed Release Notes.

NEW GUIDE: Introducing the Maintaining a DITA CMS Deployment Toolsmith's Guide. This brand new guide is intended for those who are responsible for performing the regular maintenance tasks on the deployment or coordinating with the company's IT department to ensure that these tasks are done. It provides information about testing fixes and features, generating backups, restoring components, and troubleshooting the deployment.

Major bug fixes

  • DITA CMS
    • [2360]* 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 Detailed Release Notes for more information.
    • [3158] The due dates for document assignments did not reflect the correct date when the timezone on DITA CMS client's machine was set to UTC+1. This issue has been fixed.
    • [3223] 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.
    • [3233] 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.
    • [3248] 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.
    • [3300, 3352, 3354, 3358]* Added the ability to insert keys into maps from a default list defined in a configuration file. This feature requires configuration updates. See the Detailed Release Notes for more information.
    • [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.
  • Dynamic Release Management
    • [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.
    • [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.
  • Output Generator
    • [2798] The and elements did not resolve when generating the output of DRM content. This issue has been fixed.
    • [3129]* You can now run the Dita2ReviewPdf transformation scenario using the DITA-OT 2.1.1. See the Detailed Release Notes for more information.
    • [3260] 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.

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] 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.
    • [2730] When the Search Results view switched from a selected viewpoint to None, the view did not display some of the default columns. This issue has been fixed so all the expected columns are displayed.
    • [2843] When the option Open build manifest in default editor was not selected when creating a Build Manifest object, it resulted in an error appearing in the log and the document could not be released since it required an output type to be defined. This issue has been fixed so the Build Manifest object can be released without specifying the output type; however, it cannot generate output until the output type is defined.
    • [3036] The results displayed in the Search Results view after clicking the Locate button could not be exported by clicking the Export Results List. This issue has been fixed.
    • [3065] 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.
    • [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.
    • [3106] When a topic containing an image existing in the Content Store was imported, only the thumbnail of the image was being updated instead of the image itself. 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.
    • [3144] When you selected multiple maps nested in a map and attempted to change their status, it resulted in an error message and you were unable to change the status of the selected objects. This issue has been fixed.
    • [3160] When localizing content from a previously localized map using the Concurrent localization feature, the revision numbers were not updated correctly which results in a broken map. 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.
    • [3162] In some cases the successful login message did not appear when expected. This issue has been fixed.
    • [3168] Opening a topic in oXygen XML Editor or Author while working in offline mode sometimes generated the message: "Error creating nested xml editor". This issue has been fixed.
    • [3175] In some cases, searching for referable-content in the Referable-Content view did not return the correct results. This issue has been fixed.
    • [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.
    • [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.
    • [3245/679]
      • In the XMAX editor, if an xref has an ID associated to it that pointed to a section with a title element, the section title was not resolved. This issue has been fixed.
      • 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".
    • [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 youreclipseui.xml file. See the Detailed Release Notes 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.
    • [3276] When you generated a child intersection report (Compare With > Export Children Intersection) in version 3.4, the report contained the authoring revision number of the reported child objects. In version 4.2, the revision numbers were replaced by "X". This has been fixed so that the report displays the authoring revision number again.
    • [3295] 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.
    • [3297] 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".
    • [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). See the Detailed Release Notes for more information.
    • [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. See the Detailed Release Notes for more information.
    • [3313] In previous releases, when an object was imported, the access rights assigned to the user were not applied correctly. This issue has been fixed.
    • [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.
    • [3384] 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.
  • Dynamic Release Management
    • [2605] When saving a document in the editor, the message "This document is not valid" sometimes appeared, even though the document was valid. This issue has been fixed.
    • [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.
    • [3110/3214/3215/3269] The following issues were fixed in the import feature:
      • 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.
      • 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.
    • [3135] Creating a snapshot failed when the map contained a keydef. This issue has been fixed.
    • [3170] If a topic contained an xref to another topic, it was not possible to change its status from Authoring:work to Authoring:complete (or the equivalent in your deployment). This issue has been fixed.
    • [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.
    • [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?"
    • [3258] It was not possible to move a topic from a product version to a library version when the topic was used in a map. This behavior was updated and this operation is now possible if the library version is referenced by the product version for the map.
    • [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.
    • [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.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2957] Both the bin/outputgenerator.sh and bin/outputgenerator.sh.empty files were packaged in the build, which meant that the changes made to bin/outputgenerator.sh were overwritten when customers installed a new Output Generator build. This issue has been fixed and only the outputgenerator.sh.empty file is now shipped.
    • [3294] When generating the output of DRM maps and topics, 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. See the Detailed Release Notes for more information.
    • [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.
  • Web Author
    • [3176] Inserting an image in a DRM deployment generated a "Key not found" error. This issue has been fixed.
    • [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.
    • [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.
  • Documentation
    • [3335]: The procedure "Configure the TEXTML Server connection settings" in the Output Generator Installation Guide described how to set theaddressanddocbaseattributes, but these attributes are no longer used. This issue has been fixed.
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.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.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.2.30 - 20160126

 

Bug fixes

  • DITA CMS
    • [263] The Data Set Definition dialog for BIRT reports sometimes returned an error message ("An internal error occurred") if some fields were empty. This issue has been fixed and the fields are now validated to ensure users enter the required values.
    • [843] Renaming a template collection sometimes caused errors if users were working with templates from this collection. This issue has been fixed.
    • [987] When users changed Content Store (in the Document base field of the Window->Preferences->CMS configuration dialog), the message "Problems occurred when invoking code from plug-in: org.eclipse.jface" was sometimes displayed. This issue has been fixed.
    • [2303/3164] The following issues were fixed in the Spellchecker feature:
      • When the Hunspell dictionary was not found on Linux, an error occurred. This problem has been fixed and the libhunspell-linux-x86-64.so library was updated to a more recent version.
      • On Windows, spell-checking a map created a java.lang.UnsupportedOperationException. This issue has been fixed.
    • [2542/3117/3158] The following issues were fixed in the Assignments feature:
      • In the Assignments view and Assign to dialog, entering data in the filter box removed the existing selections. This issue has been fixed.
      • The due date for the assignment changed automatically to the previous day when the time zone was set to UTC +1. This issue has been fixed.
    • [2662] In the Ditaval view, the Release Ditaval XML command did not update the name and description of the Ditaval file. This issue has been fixed.
    • [2937] If a topic contained an ID and a reference to this ID (using an xref), it was not possible to remove the element with the ID and the xref at the same time. An error message was displayed when users tried to release a topic in which both the ID and the reference had been deleted. This issue has been fixed and it is now possible to delete a source and its reference at the same time.
    • [3009/3013] In the Japanese version of the DITA CMS, some dialogs were still displaying strings in English. These issues have been fixed.
    • [679/3027/3198] The following issues were solved in the XMetaL XMAX Editor:
      • In the XMAX editor, if an xref has an ID associated to it that pointed to a section with a title element, the section title was not resolved. This issue has been fixed.
      • When users added a related link to a topic, the XMAX editor resolved the related link keyref and displayed the topic title, but it no longer rendered the title when users saved the topic. This issue has been fixed.
      • It was not possible to save or release a topic after inserting a keyword element. This issue has been fixed.
    • [3041/3220] The following issues were solved when working with SVG images:
      • When inserting an SVG image that did not contain sub-components, the DITA CMS still displayed a message indicating that sub-components would be inserted. This issue has been fixed and the warning is no longer displayed.
      • SVG images were not handled consistently. This issue has been fixed.
    • [3095] Xrefs of type docID#anchor were not resolved and generated the following error message in the Results view: "css null warning". This issue has been fixed.
    • [3115] Deleting topics with large custom properties generated a java.lang.OutOfMemoryError. This issue has been fixed.
    • [3126] In the Dependencies view, it is now possible to sort content by clicking on the column headers.
    • [3127] In the Information view, it is now possible to sort the content of the Parents section.
    • [3141] In the Manage Viewpoint dialog, it was not possible to remove all of the grouping columns from a viewpoint. This issue has been fixed.
    • [3145] In the DITA Map view, selecting an object did not refresh the Information view with the correct information. This issue has been fixed.
    • [3147/3160] The following issues were fixed in the Concurrent localization feature:
      • When localizing content with reltables, the topicrefs were not updated to point to the localized topics. This issue has been fixed.
      • Relocalizing a map broke previously localized maps. This issue has been fixed.
    • [3157] If the maps and the topics did not have the same initial status in their configuration, importing a map for the second time with the "Update existing documents" option checked gave the wrong status: The status of the map was set to the initial state of the topics instead. This issue has been fixed.
  • DITA CMS Administration plugin (TEXTML Administration perspective)
    • [3084]: In the Manage Users dialog, clicking roles sometimes generated a NullPointerException. This issue has been fixed.
  • Dynamic Release Management
    • [3047] When importing a DRM map into a library, the message "No products" was sometimes displayed, even if the user was working with the Library tab. This issue has been fixed.
    • [3086]: Indirect keys were not validated properly. This issue has been fixed.
    • [3087] The Referable-Content view displayed only the referable-topic title, which made it impossible to differentiate between topics with the same name but different versions. The view now provides the Primary Version of the topic.
    • [3112]: Dropping a map to another map in the DITA Map View was allowed, even though the maps were not in the same library tree. This issue has been fixed and an error message is now displayed.
    • [3125]: The Change Status command validated the status of all the children recursively, which took a long time for containers with multiple levels. This issue has been fixed and the command now only checks the first level of dependencies.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2874] The Output Generator could not output a map that included a topic with an SVG image. This issue has been fixed.
  • Scheduler
    • None
  • Web Author
    • [2950] Newly created images and topics now have the same Primary version as the selected Editing Context.
    • [3116] Special characters in keydef tables caused javascript errors. This issue has been fixed.
    • [3155] The Editing Context is now updated when a linked document is opened.
  • Documentation
    • [1937]: In the Dynamic Release Management Module User Guide, added information about the fields that can be configured in the product, release, and version files.
    • [2254]: Added a new topic describing how to generate the timers log for DITA CMS.
    • [2362]: Updated Ditaval topics:
      • Documentedpassthroughandflagactions.
      • Added new topic describing filter in the Ditaval view.
      • Fixed incorrect screen captures.
    • [2984]: For the Export Dependencies as TSV procedure, the DITA CMS User Guide incorrectly stated that all dependencies were exported. This issue has been fixed and the guide now states that the resulting file will include all dependencies directly related to the selected object.
    • [3185]: The documentation now explains that if you are importing the source file for an image and wish to retain its original extension, you must add its MIME type in the mimetypes.xml configuration file.
    • [3189] The User properties button on the Add/Edit Resource dialog was confusing to users when it was disabled. To solve the issue, additional information was added to the DITA CMS User Guide.
    • [3204]: The DITA CMS User Guide incorrectly stated that only the project coordinator of a project can view it. This issue has been fixed.
    • [3206]: Images in the "Use viewpoints in search results" topic were not clear. This issue has been fixed.
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.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.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.2.29 - 20151210

Download Detailed Release Notes (PDF)

Important notes

  • The DITA CMS Administrator's Guide was reorganized to improve usability. Many changes were also made to the document, including:
    • Added a new chapter, "Configuration file reference", which contains a reference of all the configuration files.
    • Clarified last step in topics to indicate whether users can click Synchronize Configuration to update their instances with the changes or if they need to restart.
    For more information, see the detailed list of changes.

Bug fixes

  • DITA CMS
    • [586] When a topic contained an entity (e.g., &company), the Show Preview command failed. This issue has been fixed.
    • [1127] On Mac OS, certain operations (e.g., Release) set the lock flag on files on the user's disk, which caused subsequent operations to fail. This issue has been fixed.
    • [2521/2975/2864/2976] The following issues were fixed in the Dependencies view:
      • By default, the Pin Contents button is now always enabled in the Dependencies view, ensuring that the view is not refreshed when a new document is opened.
      • If the Pin Contents button in the Dependencies view was enabled and users selected View Dependencies on an object, a new Dependencies view was opened, even if the current one was empty. This issue has been fixed and a new view is not opened if the current one is empty.
      • When multiple Dependencies views were opened and the user changed the status of an object that was not in the primary view, the status was never updated in the view, even if it was changed directly from the Dependencies view. This issue has been fixed.
      • If multiple Dependencies views were open and Eclipse was restarted, all the views were reopened again. This issue has been fixed and a single Dependencies view is now open upon restart.
    • [2574/2920/2989] The following issues were fixed in the XMetaL editor:
      • Certain elements that require a child element to be valid, such as (requires) or dlentry (requires), produced an invalid topic when inserted as a conref or conkeyref from the Referable-Content view using the XMAX editor. This issue has been fixed.
      • The XMAX Set Conditions dialog did not resize correctly when the screen was magnified to 125%. This issue has been fixed.
    • [2620]* The Create Build Manifest action was not properly defined in the access rights. This issue has been fixed and requires configuration updates. See the Detailed Release Notes for more information.
    • [2917/2918] Editing and releasing SVG and TIFF images took a long time, even with very small images. This issue has been fixed and working with these images is now much faster.
    • [2943] Searching a referable-content map was very slow. This issue has been fixed and the operation is now much faster.
    • [2977] In the Referable-Content view, the libraries in the drop-down All libraries menu were listed in random order. This issue has been fixed and the libraries are now listed in alphabetical order.
    • [2981] In the Eclipse UI feature, sub-menu items configured in theoxygenpopupsection of the eclipseui.xml file were not taken into account. This issue has been fixed.
    • [2985/3071] The following issues were fixed in the Queries panel of the Search view:
      • When users double-clicked or selected Load on a query from either the History, Personal, or Shared sections, the query was automatically executed. This behavior caused a problem for queries that took a long time to run. This issue has been fixed and queries are no longer automatically executed.
      • When users tried to run a report using the Run Report right-click command, an Unhandled event loop exception occurred. This issue has been fixed.
    • [2991/3064/3069/3101/3114] The following issues were fixed in the DITA Map view:
      • Keys defined in a chapter map within a bookmap were not resolved by oXygen when the bookmap was open in the DITA Map view. This issue has been fixed.
      • In the DITA Map view, when dropping a map to a map of type bookmap, the map was sometimes added as a topicref instead of a chapter. The drag and drop operation in the DITA Map view is now specialization-aware.
      • If a map that was listed in the map view history of the DITA Map view no longer exists, the DITA Map view failed to initialize. This issue has been fixed.
      • The oXygen Editor entry was missing from the right-click menu in the DITA Map view. This issue has been fixed.
      • In some cases (for example, in very large maps), opening a map or a topic with the oXygen editor when a map was open in the DITA Map view was very slow. This issue has been fixed.
    • [3008/3009/3010/3012] In the Japanese version of the DITA CMS, some dialogs were still displaying strings in English. Also, queries were not saved properly. These issues have been fixed.
    • [3024] In the RelTable Editing perspective, when inserting a relrow from a template, the content of the element was removed. This issue has been fixed.
    • [3029/3058] The following issues were fixed in the Build Manifest editor:
      • Adding output types to the Build Manifest editor was confusing, because the output types were added in random order and the new output type was not automatically selected for editing. These issues have been fixed.
      • When using the Build Manifest Output Type tab, sorting on the status corrupted the output types. This issue has been fixed.
    • [2983/3030/3032/3067/3121] The following issues were fixed in the Localization feature:
      • When importing localized content in which the language code had been modified, no error message was provided, but it was no longer possible to find the localized content in the Content Store. This issue has been fixed, and the DITA CMS now returns an error and cancels the import if the localized files contain a language code that is different than the source files.
      • The action name for the import localized image operation was changed from "Localize" to "importLocalization" in the system comments.
      • Importing a localized image corrupted the image. This issue has been fixed.
      • When importing images in the node-based localization method, the revision history did show the images as imported but the old images were still displayed. This issue has been fixed.
      • When users ran the Localize operation, a blank entry was created in the revision history. This issue has been fixed.
    • [3034/3038] The following issues were fixed in the Generate Output command:
      • When generating the output of a document, if the Unzip when done option was selected and users clicked Cancel in the Save as dialog, the output was still unzipped and saved in a "null" directory. This issue has been fixed.
      • When users generated the output of documents, multiple "NLS missing message: " messages were displayed in the Error Log. This issue has been fixed.
    • [3036] In the Search Results view, the contents of the Locate group were not exported when users clicked the Export as tsv button. This issue has been fixed.
    • [3051] Changes were lost when users released a topic with the Keep locked option twice in a row. This issue has been fixed.
    • [3052] MathML images (with the .mml extension) were not resolved in the DITA CMS. This issue has been fixed.
    • [3068] The com.ixiasoft.cms.triggers.CheckSvgContent trigger no longer blocked the releases of SVG images that contained external links. This issue has been fixed, and if this trigger is enabled, it will not be possible to release SVG images with external links.
    • [3074] In the Ditaval view, Ditaval folders and files were not sorted alphabetically. This issue has been fixed.
    • [3076] When trying to delete a map for which a snapshot had been created, an error message was displayed, but it was confusing. The error message now explains that a snapshot exists for this map, and thus the map cannot be deleted.
    • [3079] Branching a topic in a branched map generated the following DitaException "An error occurred while updating references to branched documents." This issue has been fixed.
    • [3085] In the Assignments dialog, groups were not sorted alphabetically. This issue has been fixed.
    • [3120] Importing an XLIFF file with CmsUtils 4.2 failed with the error "premature end of file". This issue has been fixed.
  • DITA CMS Administration plugin (TEXTML Administration perspective)
    • [2824/3001] The following issues with fixed in the Manage Users dialog:
      • Creating users in the Manage Users dialog did not add the data correctly in the users.xml file. This issue has been fixed.
      • The Manage Users dialog could not be opened when SSL security was enabled. This issue has been fixed.
    Dynamic Release Management
    • [2624]* Access rights can now be set for actions in the Dynamic Release Management right-click menu. These changes require configuration updates. See the Detailed Release Notes for more information.
    • [2830/3016/3026]* The following issues were fixed for the Synchronization view:
      • If users added topics to a map in a target version (e.g., V2) from a source map (e.g., in version V1) using the Compare Editor in the DRM Synchronization view and the topics were not part of the target version (i.e., V2), the topics were not added to the V2 container. This issue has been fixed, and the DITA CMS now prompts the user to add topics to the target version.
      • The Synchronization view was updated to change the command "Commit" to "Release".
      • White spaces were sometimes being added to topics as part of the merge functionality. This issue has been fixed but requires an update to an XSL file. See the Detailed Release Notes for more information.
    • [2999] Multiple errors occurred when different users created new instances of objects in same version at the same time. This issue has been fixed.
    • [3002] The Create Tag dialog provided the option to select a language instead of using the language of the version. This option has been removed.
    • [3004] The Parent section of the Information view was empty or incomplete for DRM objects. This section is not applicable to DRM, so it was removed from the Information view.
    • [3054] The Clone version and Clone library commands did not work correctly. These issues have been fixed.
    • [3057]* In the base DRM configuration, the@use-specializationattribute was set to "true" for the Lock access rights. This is not appropriate in DITA CMS 4.2 and the Lock access rights must be modified. See the Detailed Release Notes for more information.
    • [3066] When importing a composite topic with multiple topics in it, the DRM import only imported the last topic in the file. This issue has been fixed.
    • [3080] A map exported using the DRM export could not be re-imported using the DRM import. This issue has been fixed.
  • Web Collaborative Reviewer
    • [2952] When the voting process was applied to an object (map or topic) and the status of the object was changed, the change status was recorded in the revision history under the username who last voted on the topic, but there was no information about the other voters. The revision history now provides more information; for example:
      Content has been accepted by vote.
      Accepted: David Smith [dave.smith@acme.com], Julie Tremblay [julie.tremblay@acme.com]
      Rejected: None 
  • Output Generator
    • [3040] When the ANT processor parsed SVG images for serialization, the following warning was recorded in the wrapper.log file "Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set". This issue has been fixed and the warning is no longer displayed.
    • [3055] The Output Generator could not generate a Build Manifest for DRM maps that were in localization. The %OutputGenDir%/data/conductor-bmanifest.xml was modified to solve this issue. This file is updated automatically when you update the Output Generator to 4.2.29.
    • [3056] When SVG files were present, the Output Generator did not extract LowRes images correctly. This issue has been fixed.
  • Scheduler
    • [3062] A Scheduler running on Linux could not connect to a Windows TEXTML Server using Kerberos. This issue has been fixed.
    • [3063] The schedule.xml.empty file did not have the correct default values. This issue has been fixed.
  • Web Author
    • [2926/2978] The Editing Context menu displayed only the map title as the context name, which made it impossible to differentiate between contexts for maps with the same name. This issue has been fixed, and the solution depends on the DRM version that you are using:
      • For the standard DRM, the version of the map is now also displayed in the Editing Context.
      • For SAP, the version of the container is now also displayed in the Editing Context.
    • [2958] Adding new topics and imported images sometimes generated the following error: "Key definition 'vrs1443535548624' not found in the DITA Root Map." This issue has been fixed and new topics and imported images are now added to the current container defined by the current Editing Context.
    • [2982] Searching for images in a DRM environment sometimes took more than 10 minutes. This issue has been fixed.
    • [2986] Inserting images in a DRM environment returned the following message: "No active status is defined for role ". This issue has been fixed. Images are now assigned the initial status specified in the image_status.xml configuration file, regardless of the user's current role.
    • [2987] When creating topics, the topics were not assigned to the role selected by the user when creating the topic. The topics are now assigned to the role used to create the topic. Also, the status of the topic is set to the initial status defined in the templates.xml configuration file for that role.
    • [3023] The Web Author only supported thumbnails in JPEG format. It now also supports thumbnails in PNG format.
    • [3031] If there were syntax errors in the web.author.config.xml file, the Web Author did not provide error messages in the error logs. This issue has been fixed and the error log now includes information about the error.
    • [3043] When searching for images, if the currently selected editing context did not contain any image then a search error would occur. This error has been fixed and the search will simply return no images.
  • Documentation
    • [2397] The WCR documentation did not specify how to install Tomcat. This issue has been fixed. See the WCR Installation Guide for more information.
    • [2398] The WCR help file provided an older version of the documentation set. This issue has been fixed.
    • [2399] The WCR documentation did not specify how to install the WCR help file. This issue has been fixed. See the WCR Installation Guide for more information.
    • [2526] The procedures in the DITA CMS Administrator's Guide did not clearly indicate how to apply configuration changes. This issue has been fixed and each procedure now specifies if users must restart the DITA CMS or synchronize the configuration.
    • [3082] The DITA CMS User Guide still included documentation about the Synchronize Working Documents command, even though it was removed from the software for 4.2. This issue has been fixed.
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
DITA CMS Eclipse Client
  • oXygen XML 17.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.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.2.25 - 20151015

 

New Features

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

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

Upgrading your deployment

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

  • TEXTML Server
  • 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:

Bug fixes

  • DITA CMS
    • [531] The Dependencies view did not always display the correct number of children objects. This issue has been fixed.
    • [609] In some cases, the topic preview HTML hover pane did not close once it was opened. This issue has been fixed.
    • [681] The Taxonomy Terms view was missing expand and collapse buttons when a node was selected. These buttons are now available.
    • [907] The Preview view did not preview images from the Dependencies view. This issue has been fixed.
    • [963] When clicking a link to another topic (using an xref) in the oXygen Editor, a file not found error was displayed. This issue has been fixed and the editor now correctly opens the topic in another tab.
    • [1123] Orphan objects were not reported correctly in the Search Results. This issue has been fixed and orphans are now reported in the Search Results.
    • [1162] The DITA CMS did not display usernames consistently in the different views. This issue has been fixed and the CMS now displays the user information as "firstname lastname [email]".
    • [1388] When inserting a topic as an xref, the title of the topic was not always displayed. This issue has been fixed.
    • [1449] The File properties view now displays the Locked date.
    • [1467] When a user deletes multiple elements of different types at the same time, the DITA CMS now checks the dependencies of the objects and deletes the objects in the right order. If objects cannot be deleted, an error message is displayed.
    • [1476/1806] When users resize the DITA CMS dialogs, the new size is now retained the next time that the user logs in.
    • [1567] In the Revision History, the DITA CMS used the size of the largest Revision History entry to size all the rows, which reduced readability. This issue has been fixed. Also, the first entry in the Revision History is now automatically selected.
    • [1605] Links to another topic using an xref did not display in oXygen if the referenced object was not already in the workspace. This bug fix requires oXygen version 17.
    • [1832] The Taxonomy Terms in the Search panel did not always display the human-readable version of the terms. This issue has been fixed.
    • [1843] Any user could change the status of an object using the Revert function from the Revision History. This issue has been fixed and only users with access rights to lock an object can revert the changes in the Revision History.
    • [2068] In the Revision History, when multiple entries were created at the same time, the entries were not always in the right order. Also, user comments and system comments were not always properly aligned. These issues have been fixed.
    • [2095] After adding a new taxonomy, users had to lock the taxonomy to start editing it. Since users almost always want to modify the taxonomy right away, the taxonomy is now locked and ready for editing immediately.
    • [2096] When adding a new taxonomy term, the Vocabulary Term value always defaulted to a value of "untitled_n". To maximize user readability, the Vocabulary Term value now matches the Human Readable term by default.
    • [2134] The DITA CMS no longer allows guest user logins.
    • [2207] In the Search Results view, the creation date and time were always shown in separate columns. To improve readability, the creation date and time columns are now concatenated.
    • [2293] The name of the taxonomy appeared as a selectable term in the Select Taxonomy Terms dialog. This issue has been fixed.
    • [2312/2359] The Dependencies view had to be refreshed a few times to display the Children Dependencies. This issue has been fixed.
    • [2409] When configuration files (in the /system/conf directory) included typos or were malformed, the Eclipse log did not provide a meaningful error message. This issue has been fixed and the log now contains information that allows administrators to troubleshoot the configuration.
    • [2449] An unnecessary warning was displayed in the Error Log when connecting to a docbase for the first time ("Search preferences could not be retrieved from the server."). This issue has been fixed and the warning has been removed.
    • [2593] In some cases, the Export Search Results command failed and returned a ClassCastException error. This issue has been fixed.
    • [2602] The default value for the Assigned to list in the Search view was not consistent. This issue has been fixed and the default value is now the logged in user.
    • [2618] The Search and Replace dialog in the DITA map view displayed a dialog about processing the results on Search Results pages, which was confusing. This issue has been fixed and the dialog has been removed.
    • [2645] If a map template contained a stub for a keydef element, the "Generate topics from stubs" action did not show the stub, so the topic was not generated. This issue has been fixed.
    • [2726] The Role Assignment dialog was not displayed correctly. This issue has been fixed.
    • [2728] In previous releases, a snapshot could be created for a single map only. You can now select multiple maps to snapshot at the same time.
    • [2743] The version is now displayed, in addition to the title, in the editor tab for the opened topics.
    • [2756] Inactive users (that is, users with the active="false" flag) could still log in and be assigned new content. This issue has been fixed and inactive users cannot log in and cannot be assigned new content.
    • [2790] The "UTC time must be enabled" error was sometimes displayed when setting preferences in the DITA CMS even when the value was set in the TEXTML Server. This issue has been fixed.
    • [2804/2948] The list of users in the Last modified by drop-down of the Search view was not in alphabetical order. This issue has been fixed. The users are listed in alphabetical order and the default user is the current user.
    • [2819] When multiple actions were performed within a single revision, they did not have separate time stamps. This issue has been fixed and each action now has its own time stamp.
    • [2836] The ditaval folders and files were listed in random order in the Ditaval view. They are are now listed in alphabetical order.
    • [2847] The "Optimization Required - See summary" message was displayed in the DITA CMS log as an ERROR, even if it's not an error. This message has been changed to WARN.
    • [2871] The Change Status command was modified to improve how the DITA CMS handles changing the status of multiple objects at the same time.
    • [2875] When doing a preview of a first map and then a second map, the first preview was not cleaned correctly and sections of the first map could still be seen. This issue has been fixed.
    • [2883] In the progress monitor for an action, the CMS displayed the names of all the triggers configured for this action, even if the trigger was not actually executed. This issue has been fixed.
    • [2907] The maps in the history list of the DITA Map view were displayed in random order. They are now displayed in the order they are opened.
    • [2953] The error message for an invalid entry in display.xml referred to the displayColumns.xml file. The error message now displays "Unable to retrieve *entry* from CMS display.xml or from the TEXTML Server. Please check your CMS configuration."
  • Dynamic Release Management
    • [2228] Multiple configuration files were updated to define a new type for containers. These changes are covered in the Upgrading the DITA CMS DRM from 4.1 to 4.2 document.
    • [2308] Non-DRM DITA CMS clients could connect to a DRM Content Store, which should not be allowed. This issue has been fixed and a new configuration parameter now ensures that clients can only connect to the appropriate Content Store.
    • [2493] It was possible to add a conref to a topic even though that topic was not in the same version as the source topic. This issue has been fixed, and the DITA CMS now displays a dialog asking users if they want to add the target topic to the version.
    • [2632] The Empty Product (No Release) and Empty Product (No Version) exclusion filter settings were renamed to Empty Product/Library (No Release) and Empty Product/Library (No Version) for clarity.
    • [2735] It was possible to change the status of an object that was in the done state and for which the parent container and version were closed. This issue has been fixed and it is no longer possible to change the status of a version.
    • [2749/2750/2751/2752] The Select Versions, Create New Instance, Update To, and Remove From dialogs displayed versions that were not in the work state. This issue has been fixed and the dialogs now only display versions that are in the work state.
    • [2753] The DITA CMS allowed objects to be added to or removed from versions that were not in the work state. This issue has been fixed.
    • [2805] Maps that were exported from a DRM docbase could not easily be imported into another DRM docbase. This issue has been fixed and the Output Generator now provides a new output type to export DRM content.
    • [2845] It is now possible to select multiple topics, images, or resources for the Create New Instance function.
    • [2853] The DITA CMS displayed the Publish and Branch options for snapshots, but these actions are not possible in the DRM. This issue has been fixed and these options are no longer available to users.
    • [2891] The tooltip for the icon "Create a new product" was incorrect. It has been changed to "Create a new product or library".
    • [2922] If a map included a keydef reference that contained a keyref to reference another keydef, the map could not be imported. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2665] When users selected the "Unzip when done" option, the Output Generator waited until the file was unzipped before returning the control to the DITA CMS Eclipse Client. For large maps, this gave the impression that the DITA CMS was unresponsive. This feature is now executed in the background.
    • [2686] A preprocessor required at least one system parameter in the preprocessors.xml configuration file, even if it did not need any parameter, otherwise the process failed. This issue has been fixed and it is no longer necessary to specify a system parameter.
    • [2738] The ditaval file is now included in the zipped folder when generating the output content.
  • Scheduler
    • [1993] The schedule.xml file now provides an option that allows you to easily disable a job.
    • [2124] The version.txt file was missing from the build and the manifest.mf file was incorrect. These issues have been fixed.
    • [2311/2387] The debug email address when configuring the Scheduler has been renamed to Dixia.scheduler.debug.email.
    • [2339] The Scheduler now allows users to schedule reports.
    • [2613] The templates and outbox collection are now in the Content Store's Repository, in the \system\scheduler directory.
  • Web Author
    • [1035] The "No Assignments" message was not updated when new assignments were available and the user clicked the Refresh button. This issue has been fixed.
    • [1237] The build version is now more visible in the CMS Application Server and Web Author Application builds.
    • [1361] The web.author.roles.xml configuration file was moved from the Tomcat conf folder to the Content Store.
    • [1562] Errors in the web.author.roles.xml file prevented the Web Author application from initializing properly. The Web Author now parses the web.author.roles.xml file to verify it is well-formed.
    • [1707] Better messages are now displayed when a topic has changed status and is no longer in the list of assignments for a user.
    • [2638] Version numbers were duplicated in the build process. This issue has been fixed.
    • [2765] The keyref resolution feature requires indexes that were missing from the Index Definition document. These indexes are documented in the 4.2 upgrade guides.
  • 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.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.4188 and up
WCR Server
  • Tomcat 6.0.x
  • 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 3.1.2.x 
    • Java JDK 1.7.0_51 or 1.7.0-80 and up (Java 1.8 is not supported)
  • Web Author Application:
    • Tomcat 6.0.x
    • 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)

*Some configuration changes need to be applied to benefit from the new features, please ask support for samples.