DITA CMS version 4.1 - Release Notes

Build 4.1.16 - 20161122

Important notes

This release contains an important fix to prevent loss of content. IXIASOFT strongly recommends that you update all your environments.

 

Major bug fixes

  • DITA CMS
    • [3525] In rare cases, the latest released revision was not being retrieved from the Content Store when a user locked an object. This situation might occur when two users edited and released the same object in quick succession with one user performing the lock from an existing list of search results, which retrieved the object from the workspace rather than the Content Store. This could result in changes from the initial user being unintentionally overwritten or lost. The issue has been fixed so that the latest revision of the object is always retrieved from DITA CMS when the object is locked.

Bug fixes

  • DITA CMS
    • None
  • 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.5.4164 and up (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213 and up
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170 and up
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 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 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

Build 4.1.15 - 20161028

 

Bug fixes

  • DITA CMS
    • [3249]: The Search & Replace "all pages" feature only replaced content on the current page of the search results. This issue has been fixed.
    • [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.
    • [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.
    • [3431] One of the oXygen toolbars was missing from the editing view. This issue has been fixed.
    • [3525] In rare cases, the Search Results view was not being refreshed in time to reflect changes committed by another users; therefore, 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.
    • [3571] In some cases, searching for referable-content in the Referable-Content view returned an error message. This issue has been fixed.
    • [3676] Inserting an image reference in oXygen was very slow. This issue has been fixed.
  • 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.
    • [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.
    • [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.
    • [3657] Under unusual circumstances, locking a resource object resulted in a NullPointerException error. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator/Scheduler
    • [3314/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.

  • Web Author
    • None
  • Documentation
    • None
  • CMS Application Server
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164 and up (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213 and up
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170 and up
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 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 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

Build 4.1.14 - 20160219

Critical/major bug fixes

  • DITA CMS Eclipse Client
    • [3134] Creating Adobe Illustrator (*.ai) images blocked any other further image actions. This issue has been fixed.
    • [3198] (XMetaL only) It was not possible to save or release a topic after inserting a keyword element. This issue has been fixed.
    DRM
    • [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
    • [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 Eclipse Client
    • [679/3245]
      • 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".
    • [2542/3117] In the Assignments view and Assign to dialog, entering data in the filter box removed the existing selections. This issue has been fixed.
    • [3147] When localizing content with reltables in the Concurrent localization feature, the topicrefs were not updated to point to the localized topics. This issue has been fixed.
    • [3210] Personal queries did not load and execute properly. 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.
    • [3211] It is no longer possible to update a topic in another version if the topic is not in a lockable state in that version. Now, if the topic is not in a lockable state, the topic is disabled.
    • [3244] When opening a topic in XMetaL from the DITA Map view, the images did not appear in XMetaL. This issue has been fixed.
    • [3296] It was possible to select an object and insert it using the right-click Oxygen Editor menu (Insert as Conref, Insert as Related Link, Insert as Xref, and Insert Image), even if the object was not in the same version as the document. This issue has been fixed.
  • 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
    • None
  • Documentation
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164 and up (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213 
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170 and up
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 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 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

Build 4.1.13 - 20151202

 

Bug fixes

  • DITA CMS Eclipse Client
    • [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.
    • [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 remove a source and its reference at the same time. 
    • [2989] (XMetaL only) The XMAX Set Conditions dialog did not resize correctly when the screen was magnified to 125%. This issue has been fixed.
    • [3027] (XMetaL only) 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.
    • [3032] Importing a localized image corrupted the image. This issue has been fixed.
    • [3052] MathML images (with the .mml extension) were not resolved in the DITA CMS. This issue has been fixed.
    • [3067] When users ran the Localize operation, a blank entry was created in the revision history. This issue has been fixed.
    • [3073] In the DITA Map view, opening the right-click menu and pressing the Escape character generated a java.lang.NullPointerException error. This issue has been fixed.
  • Dynamic Release Management
    • [3066] When importing a composite topic with multiple topics in it, the DRM import did not properly extract the topics: it only imported the last topic in the file. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [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.1.13.
  • Scheduler
    • None
  • Web Author
    • None
  • Documentation
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164 and up (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170 and up
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 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 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

Build 4.1.12 - 20151119

Download Detailed Release Notes (PDF)

Bug fixes

  • DITA CMS Eclipse Client
    • [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.
    • [2574/2920] (XMetaL only) 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.
    • [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.
    • [2664] When reimporting objects and selecting the Update existing documents option, the status of the objects was always set to review, which was invalid in certain configurations. This issue has been fixed and the status is now set according to the workflow configuration.
    • [2825] When importing content that was previously exported from a Content Store, the following message was displayed "Unable to import dita file: Unable to find state for " message. This issue has been fixed.
    • [2864] 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.
    • [2943] Searching a referable-content map was very slow. This issue has been fixed and the operation is now much faster.
    • [2991] 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.
    • [3044] If a map contained incorrect key definitions, trying to resolve these keys caused the DITA CMS to enter an infinite loop when users tried to open the map in the DITA Map Editor. This issue has been fixed and the DITA CMS now returns a list of incorrect keys.
    • [3058] When using the Build Manifest Output Type tab, sorting on the status corrupted the output types. This issue has been fixed.
  • DITA CMS Administration plugin (TEXTML Administration perspective)
    • [2824] Creating users using the Manage Users dialog in the TEXTML Administration perspective did not add the data correctly in the users.xml file. This issue has been fixed.
    • [3001] The DITA CMS Admin > Manage Users dialog in the TEXTML Administration perspective could not be opened when SSL security was enabled. This issue has been fixed.
  • Dynamic Release Management
    • [2624]* Permissions can now be set for actions in the the Dynamic Release Management right-click menu. These changes require configuration updates. 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.
    • [3054/3061] The Clone version and Clone library commands did not work correctly. These issues have 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
    • None
  • Scheduler
    • [3039] The commons-compress-1.7.jar file was missing from the Scheduler package. This issue has been fixed.
  • Web Author
    • None
  • Documentation
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164 and up (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170 and up
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51 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 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51 and up (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

Build 4.1.11 - 20151022

 

Bug fixes

  • DITA CMS Eclipse Client
    • [2616] Cloning an SVG image that referenced other images did not work. This issue has been fixed.
    • [2919] When a map in the Localization cycle was localized multiple times, the containerref in the map did not resolve. This issue has been fixed.
    • [2964] The Open With->XML Editor with resolved topics command failed if the workspace was on a network location that was accessed using an address of type "\\server\...". This issue has been fixed.
    • [2967] In the Build Manifest dialog, it was not possible to delete a Ditaval file; an existing file could only be replaced with another. This issue has been fixed.
    • [2971] When images were deleted, they were not removed from the .image zip file. This issue has been fixed.
  • Dynamic Release Management
    • [2931] In the DITA Map view, when adding a topic to a map in a different version using the Set Drop Point command, the DITA CMS did not warn users that they were adding a topic to a different version. This issue has been fixed and a warning message is displayed.
    • [2935] When creating a new instance of an SVG image that referenced other images, the new instance was corrupted. This issue has been fixed.
    • [2990] In some cases, creating a new instance of an image generated a null pointer exception. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2557] Build Manifests were not generating correctly in Linux. The Build Manifest feature was redesigned and is now working correctly. Please update the Output Generator to 4.1.11 to benefit from these changes.
  • Scheduler
    • [2870] Notification tickets were not sent out and the following message was displayed: "javax.mail.internet.AddressException: Local address contains control or whitespace in string". This issue has been fixed.
  • Web Author
    • [2925] The catalog parser in Web Author did not normalize public IDs, which created issues when looking up public IDs that contained spaces. This issue has been fixed.
  • Documentation
    • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164+ (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213 
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170+
WCR Server
  • Tomcat 6.0.33 and up
  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
Web Author Server
  • CMS Application Server:
    • GlassFish Server 3.1.2.x
    • Java JDK 1.7.0_51 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 and up (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

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

Build 4.1.10 - 20151006

Download Detailed Release Notes (PDF)

Important notes

  • The algorithm to generate IDs has changed. From now on, 3 random letters will be used to form the start of object IDs. This change was required as more IT department create username schemes that are not based on actual names and created issues with the Content Store. This change has no impact on existing objects and should be completely transparent.

Bug fixes

  • DITA CMS Eclipse Client
    • 2131: When creating a ditaval, users could select a default action when the Default action checkbox was unchecked. This issue has been fixed. Users must now first check the Default action box before selecting a default action.
    • 2294: When changing the status of an object, if users typed a comment *and* selected a pre-configured comment checkbox, only the typed comment appeared in the Revision History. This issue has been fixed and both comments are now displayed.
    • 2327: In some cases, if an error occurred when changing the status of maps, the Locate action in the Error dialog did not work. This issue has been fixed.
    • 2383: When saving a search query, the "Limit to DITA Map view" option was not saved. This issue has been fixed.
    • 2541: User parameters that were set for a Build Manifest were not taken into account when the Build Manifest was generated. This issue has been fixed.
    • 2543: When importing content with a language code of en-US, the DITA CMS displayed the language as en-us, giving the impression that the language code had been converted during the import. This was actually a display issue which has been fixed. The language code is now displayed correctly.
    • 2556: Releasing an SVG image with an external doctype was blocked if the DTD was not found. The SVG DTDs are now referenced by the DITA CMS master catalog, resolving this issue.
    • 2595/2770: In some cases, a personal query returned incorrect results. This issue has been fixed.
    • 2606: The display of images was too small in the oXygen Author mode. This issue has been fixed.
    • 2660: When importing Ditaval files, the DITA CMS ID was used as the name and description of the Ditaval. This issue has been fixed; the name of the Ditaval file on disk is used as the Ditaval name and the description is blank.
    • 2667: (HyperSTE) A document had to be checked out for the "Look up a word" menu option to be available. This behavior was modified and the document no longer needs to be checked out for users to look up words.
    • 2680: When users made a change to a topic title or template in the Generate Topics from Stubs dialog box, the changes were not applied to the generated topic. The title and template given to the stub when it was initially created were used instead. This issue has been fixed.
    • 2766: When importing topics that contained an href to a file with an encoded space (%20) in the file name, the file was not imported. This issue has been fixed.
    • 2784: In the Show/Edit Image dialog, the Release button was displayed even when the image was not locked. This issue has been fixed.
    • 2789: The only way to close a stuck Preview window was to press the Escape key. A Close button is now available on the Preview window.
    • 2806: Creating a project with no project coordinator generated a Java exception when trying to open the Project Management perspective. This issue is fixed and projects are now automatically assigned to a project coordinator.
    • 2817: Searching all topics for orphans created a Java heap space error. This issue has been fixed.
    • 2822: Showing the preview of an SVG image that included parts did not work. This issue has been fixed.
    • 2823: In the Search Results view, the Version column did not display characters correctly; it displayed character entities instead. This issue has been fixed.
    • 2844: Creating a Build Manifest without specifying the "Open build manifest in default editor" option generated an error. This issue has been fixed.
    • 2889: When users opened a snapshot, the DITA CMS also created the preview of the snapshot, which sometimes took a long time. This issue has been fixed and a preview of the snapshot is no longer created when users open a snapshot.
    • 2903: When releasing a TEXTML query, the following message was sometimes displayed: Attribute "xml:lang" must be declared for element type "elem". To solve the issue, you must update the cms_query.dtd file. See the Detailed Release Notes for more information.
  • Dynamic Release Management
    • 2358: When opening a topic that included conkeyrefs in XMetaL, the conkeyrefs were not rendered, an error message was displayed, and a NullPointerException was generated. This issue has been fixed.
    • 2642: If a keydef reference contained a keyref to reference another keydef, the target of the keyref was not properly resolved in oXygen. This issue has been fixed.
    • 2655: The DRM section of the Information View did not display all the versions to which a topic belonged. This issue has been fixed.
    • 2740: The status of a DRM version could not be changed even when all of the objects in the version were in a done state. This issue has been fixed.
    • 2745: Creating a new instance of a map in another version with the option "Clone a new instance for all the topics/images/resources ..." created duplicate entries in the container part of the target version when these objects already existed in that version. This issue has been fixed.
    • 2759: Re-importing a map into an additional version did not create a new instance of the map. This issue has been fixed.
    • 2773: An image imported or created by a user and added to a topic was not displayed in the topic for other users. This issue has been fixed.
    • 2786: When including an image in a referable content, the image was not rendered in the editor. This issue has been fixed.
  • Web Collaborative Reviewer
    • 2219/2575: An issue with the voting process prevented objects from moving to the next configured status when they were approved or rejected. This issue has been fixed.
  • Output Generator
    • 2386: The OutputGeneratorClient did not set the value for the following properties: outgen.job.lastmodifier.name, outgen.job.lastmodifier.email, outgen.job.requester.name, and outgen.job.requester.email. This issue has been fixed.
    • 2614: The SVG DTDs were missing from the Output Generator build. This issue has been fixed.
    • 2617: When an image object containing an SVG that references other files was packaged by the Output Generator, the SVG was extracted and saved as the .image but the referenced files were not extracted. This made the SVG invalid. This issue has been fixed.
    • 2663: The default value for the AXF_DIR property in the outgen-init-client.xml.orig file was incorrect. It should be as follows:
      	
      	
      The default value has been fixed in the outgen-init-client.xml.orig file.
    • 2673: elements (i.e., resource elements) were not copied to the output folder when generating the output. This issue has been fixed.
    • 2736: The default timeout of 60 seconds in the outputtypes.xml file was not sufficient in most cases. The default is now 10 minutes (600000 seconds).
    • 2738: The ditaval file can now be included in the zipped folder when exporting content. To get the ditaval file, in your custom preprocessors.xml file, set the following system parameter for the Export output type:
       
    • 2850: In some cases, the encrypt program (used to encrypt passwords) could not find where Java was installed. The issue has been fixed and the program was updated to use the Java location specified in the wrapper.conf file.
  • Scheduler
    • 2718: The PrepareKitJob failed when processing images for the kit. This issue has been fixed.
    • 2850: In some cases, the encrypt program (used to encrypt passwords) could not find where Java was installed. The issue has been fixed and the program was updated to use the Java location specified in the wrapper.conf file.
  • Web Author
    • None
  • Documentation
    • 2815: The User Guide now indicates that while you cannot localize a snapshot directly, you can publish a snapshot and then localize the published version.

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164+ (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170+
WCR Server

Web Author Server

  • Tomcat 6.0.x + Java JRE 1.7.0_51+ (Java 1.8 is not supported)
  • [Web Author Server only] GlassFish 3.1.2.x _ Java JDK 1.7.0_51+ (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

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

 

Build 4.1.7 - 20150715

 

Bug fixes


  • DITA CMS Eclipse Client
    • [786] When changing the status from work to review for a topic that was opened in the oXygen editor, the DITA CMS correctly applied the ixialocids to the topic but did not refresh the topic. This issue has been fixed and the DITA CMS now updates the topic to show that the ixialocids have been applied correctly.
    • [981] In some cases, related links in a localized topic did not point to the latest revision of the target topic in localization. This issue has been fixed.
    • [1878] When branching a sub-map, reverting it to Authoring, and then re-branching it with the same tag, a new branch with the same tag name was created. This issue has been fixed, and when you branch/revert/re-branch a sub-map, the DITA CMS now checks if a branched version with the same tag exists and points you to that sub-map instead of creating a new branch version of the sub-map.
    • [2160] The Create New Branch and Branch Topic options were displayed even when a map/topic could not be branched because it was not published. The issue has been fixed and these options are displayed only when they are available.
    • [2334] It was not possible to release a Build Manifest without a Notify field, even if this field is optional. This issue has been fixed.
    • [2335] The DITA CMS did not validate the content of the Notify field in the Build Manifest window. The content is now validated to make sure that:
      • The email address(es) specified are valid. See the DITA CMS User Guide for a detailed list of valid email addresses.
      • If multiple email addresses are provided, they are separated either by commas or semi-colons; a combination of both is not accepted.
    • [2364] When importing localized maps and topics with the Concurrent localization method, the imported maps and topics remained in the "Localization:in translation" status. This issue has been fixed and the maps and topics are now in the "Localization:review" status (or as configured in your deployment) when they are imported.
    • [2496] Access rights for objects whose types used a combination of upper and lower casing (e.g., learningAssessment) were not read properly, so actions could not be applied to these objects (for example, lock a learningAssessment topic). This issue has been fixed.
    • [2501] The DITA Map view did not display the revision number of a map when you opened an older revision of the map. This issue has been fixed and the revision number is now displayed beside the map title in the DITA Map view.
    • [2511] Hiding the Dates panel in the Search view and then returning to the default Search view created a null pointer exception. This issue has been fixed.
    • [2517] When using the Concurrent localization manager, the localization kit was created in Xliff format even when the configuration specified the DITA format. This issue has been fixed.
    • [2519] The default localizationManagers.xml file was improved so that the Concurrent localization model could be enabled more easily.
    • [2528] When localizing a map for a second time (version=2), the localized map was not displayed in the search results. This issue has been fixed.
    • [2540] The Create Build Manifest dialog allowed users to add or delete user parameters but not to modify an existing parameter. This issue has been fixed and it is now possible to modify an existing user parameter.
    • [2556] Releasing an SVG image with an external doctype was blocked if the DTD was not found. The SVG DTDs are now referenced by the DITA CMS master catalog, resolving this issue.
    • [2565] When importing an SVG image, if the image included a part whose filename had the pattern <id_format_name.jpg>, the image was not imported correctly. This issue has been fixed.
    • [2567] When a topic containing a conref was auto-translated using the Sequential localization manager and the element containing the conref had not changed, the conref was lost. This issue has been fixed.
    • [2580] There was an encoding issue with the Information view that prevented some characters (such as accentuated characters) in the system and user comments to be displayed properly. This issue has been fixed.
    • [2584] When a map containing multiple levels of topicrefs was auto-translated using the Sequential localization manager and one of the lower-level topic had been modified but none of its parents, the topicref was lost during the auto-translation of the map. This issue has been fixed.
    • [2596] A Java null pointer exception sometimes occurred when running a personal query. This issue has been fixed.
  • Dynamic Release Management
    • [2307] References inserted in Author mode were not resolved right away by the DRM. This issue has been fixed and references (images, xref, related links, etc.) are now automatically resolved.
    • [2503] The Open With-->XML Editor with Resolved Topics right-click menu option for maps did not work with DRM. This issue has been fixed.
    • [2508] When a topic was removed from a version, the Primary Version column continued to show the version. This issue has been fixed.
    • [2524] If an object belonged to more than one version with the same name, it was not possible to see the primary version for the object. This issue has been fixed.
    • [2555] The Import Ditaval option was not available in the DRM module. This issue has been fixed.
    • [2558] The Referable-Content libraries did not work in the DRM module. This issue has been fixed.
    • [2560] The Show Statistics button in the DITA Map view toolbar did not work in the DRM module. This issue has been fixed.
    • [2561] The @href attribute was not validated when releasing topics. This issue has been fixed.
    • [2566] The Lock dialog only displayed the version of an object, which was confusing when the same version was used in multiple releases and the user had to specify which version to lock. This issue has been fixed and the Product/Release/Version is now displayed.
    • [2571] The message displayed when creating a map with the option to "Add to current map as a sub-map" was not clear. This issue has been fixed.
    • [2572] Searching in a product version did not include the documents that were in library versions used in this product. This issue has been fixed and the library versions are now also searched.
    • [2581] When importing a map, the primary version was not displayed for the map. This issue has been fixed.
    • [2588] The Output Generator could not generate the output of localized maps. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2590] In some cases for the DRM module, the Output Generator converted keyrefs to hrefs, which invalidated references and excluded topics from the output. This issue has been fixed.
  • Scheduler
    • [2113] SSL is now supported for the Scheduler. See the DITA CMS System Administrator's Guide for more information.
    • [2529] Notification tickets no longer included theandelements for the DITACMSActivityReport. These elements were used by some customers to customize the message in the notification email (template change_status_ticket.xsl). This issue has been fixed and these elements are now included in the tickets.
  • Web Author
    • None
  • Documentation
    • [2610] Thetopworkloadattribute in the roles.xml file is now documented in the DITA CMS System Administrator's Guide.
    • [2630] The topics in the "About conditional topics" section of the DITA CMS User Guide were not ordered correctly. This issue has been fixed.

Features

  • None

Requirements

 

ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.5.4164+ (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.
DITA CMS Eclipse Client
  • oXygen XML 16.1.0.v2015012213 
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.5.4170+
WCR Server

Web Author Server

  • Tomcat 6.0.x + Java JRE 1.7.0_51+ (Java 1.8 is not supported)
  • [Web Author Server only] GlassFish 3.1.2.x _ Java JDK 1.7.0_51+ (Java 1.8 is not supported)
Output Generator

Scheduler

  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
WCR Client

Web Author Client

  • Java JRE 1.7.0_51

 

 

Build 4.1.6 - 20150617

Features


  • [2413]* The DITA CMS now supports SVG images with embedded raster graphics. See the Detailed Release Notes for more information.
  • [2518]* The Concurrent Localization Manager now includes a configuration parameter to specify whether to produce XLIFF or DITA files in the localization kit. See the Detailed Release Notes for more information.

Bug fixes


  • DITA CMS Eclipse Client
    • [410] Editing an image sometimes generated an "Unsupported image type" error message because the new width and height of the image were not reloaded properly. This issue has been fixed.
    • [1705/1958] When creating a snapshot of a map that included a keyref in its title, the title was not resolved correctly in the snapshot. This issue has been fixed.
    • [1932] The items in the Search drop-down list (in the Search for panel) were not sorted alphabetically. This issue has been fixed and the items are now listed in alphabetical order.
    • [1950] You can now retrieve the revision history by typing Ctrl+Shift+0.
    • [1955] Deleted snapshots were displayed in the Dependencies view. This issue has been fixed and deleted snapshots no longer appear as dependencies of a map in the Snapshot to section.
    • [2061/2404] When configuring users in the User Manager window, pressing Ctrl-S did not keep the last modified field. This issue has been fixed.
    • [2128] The Load and Clone actions in the Shared Queries area did not work properly. This issue has been fixed and users can now load and clone shared queries.
    • [2287] The View Dependencies command reported incorrect results in the Published to dependencies. This issue has been fixed.
    • [2319]* Active assignments were not showing when assigned to multiple users. This issue has been fixed and requires a configuration change. See the Detailed Release Notes for more information.
    • [2325] In the Search Results view, changing the status of multiple grouping selections only changed the status of the first grouping. This issue has been fixed and the status change is now applied correctly to all selected objects.
    • [2341] You can now set the flag action for a DITAVAL file in the Create Ditaval and Edit Ditaval dialogs. See the DITA CMS User Guide for more information.
    • [2344] When a map was open in the DITA Map view and another map was open in the DITA Map Editor, making changes to the columns in the DITA Map Editor created a mismatch in the DITA Map view columns. This issue has been fixed.
    • [2346] Deleting user parameters in the Output Types tab of the Build Manifest window sometimes moved the focus to the first output type in the list. This issue has been fixed and the focus remains on the output type being defined.
    • [2348] Adding a topic twice to a reltable cell incorrectly generated the message "Topic is not present in the map. It might result in a broken link." This issue has been fixed.
    • [2364] After importing a localized map and its topics, the status of the map and topics remained at "Localization:in translation" for the concurrent localization manager. This issue has been fixed, and the status after localization is now "Localization:review" (or as defined in your configuration).
    • [2365] When a localization error occurred, the error message dialog displayed did not always show the correct error icon. This issue has been fixed.
    • [2375] Deleting an object incorrectly created a collection in the Content Store with the deleted file name. This issue has been fixed and a collection is no longer created.
    • [2408] If a key could not be resolved (for example, if a topic referred to a key that was not defined in the map), the topic could not be displayed and a NullPointerException was generated. This issue has been fixed and the topic now simply shows an unresolved key.
    • [2410] In XMetaL, double-clicking a link to a webpage or PDF did not open the link. This issue has been fixed.
    • [2418] in XMetaL, keywords were duplicated every time users saved or refreshed a topic. This issue has been fixed.
    • [2425] The HyperSTE toolbar buttons did not refresh properly when users switched between documents. This issue has been fixed.
    • [2431] It was not possible to hide the Queries panel using the Show/Hide command in the Search view. This issue has been fixed.
    • [2433] When users entered comments in the Change Status dialog and clicked a status bubble to change the status, the comment did not appear in the list of previous comments. This issue has been fixed.
    • [2441] It was not possible to release a topic when an ID and its reference were deleted from the topic at the same time. This issue has been fixed.
    • [2453/2474] When branching snapshots, no version was assigned to the branched map. The Create Snapshot dialog now requests users to specify a version, and this version is also assigned to the branched map when branching snapshots.
    • [2468] In some cases, adding a topic to an empty DITA Map view caused an exception. This issue has been fixed.
    • [2492] A bug in a trigger prevented the DITA CMS from displaying newly created referable-content topics in the Referable-Content view. This issue has been fixed, and new referable-content topics are now quickly displayed in the Referable-Content view.
  • Dynamic Release Management
    • [1363] The Dependencies view did not always provide the correct results for the Parent and Child Dependencies of container parts. This issue has been fixed.
    • [2273] The Create a new Instance command was displayed for containers and container parts. This issue has been fixed and this command is now disabled for containers and container parts.
    • [2277] It is no longer possible to open a product or library in the default editor from the Create Product/Library dialog, because this option was causing workflow issues.
    • [2351] Nested conkeyrefs did not resolve in XMetaL. This issue has been fixed.
    • [2378] When creating a new instance of a map in a new version, the DITA CMS now checks if the libraries referenced in the map are also available in the new version. If not, the new instance is not created and the following message is displayed: "The id [xxx] exists in library of current version [V1], but it does not exist in target version[V2]."
    • [2381] When creating an object, it was possible to add it to both a product and a library. This is no longer possible.
    • [2382] It is no longer possible to remove objects from a library if they are used in a product version.
    • [2385] The Links > Copy Reference context menu always created an href reference, which is not useful in a DRM deployment. This behavior has changed and the DITA CMS now uses the systemversion.xml configuration file to determine if a keyref or href should be used. By default, this is a keyref for DRM deployments. You do not need to modify your configuration for this change to occur.
    • [2421] Keywords defined with a keyref did not display correctly in the oXygen XML Editor. This issue has been fixed.
    • [2435] Key definitions in a keydef map that was referenced in a bookmap's frontmatter were not resolved. This issue has been fixed.
    • [2439] A configuration conflict between the sequential and concurrent localization models created an issue when importing a localized map. This issue has been fixed.
    • [2485] Out-of-scope objects were not detected when trying to change the status of a top map. This issue has been fixed.
    • [2491] The Spellcheck feature was not working properly on DRM maps. This issue has been fixed.
    • [2494] Opening a map using the Open With > XML Editor with resolved topics command now synchronizes all children of localized maps.
    • [2505] A map created with the bookmap-stub template could not be localized from the Published:done status. This issue has been fixed.
  • Web Collaborative Reviewer
    • None
  • Output Generator
    • [2286] The NightBuild script now includes a template to query and output Build Manifests. The new package is available at the following URL: http://cms.ixiasoft.com/downloads/cmsutils/4.1/.
    • [2306] In the Generate Output dialog, if users did not select an output type and clicked the Create button, an error was generated. To improve this behavior, the Create button is available only when users have selected an output type.
    • [2315] When users selected the "Unzip when done" option in the Generate Output dialog, the DITA CMS did not delete the previous output, if it existed. This issue has been fixed and the previous output is now deleted.
    • [2336] The Output Generator no longer fails if an invalid email address is provided in the Notify field of a Build Manifest. If an invalid address is provided, the outputs are generated, but no email is sent and a warning is provided in the wrapper.log and build.html files.
    • [2357]* You can now set the size of the memory allocated to transform a PDF using the RenderX XEP engine. See the Detailed Release Notes for more information.
    • [2376]: Theextract_HiRes_imagesandextract_LowRes_imagestargets in the%OutputGenDir%/data/commontargets.xml file used an incorrect variable (outgen.job.input.dir). The file was updated and the targets now use the correct variable (outgen.job.source.dir). If you created your own image targets based on the code in the commontargets.xml file, change theoutgen.job.input.dirvariable name tooutgen.job.source.dir.
    • [2464]* The path environment variable set in the Output Generator configuration file was not passed properly in Linux. This issue has been fixed, but you may need to update the outgen-init-client.xml file if you customized it. See the Detailed Release Notes for more information.
    • [2476] An exception occurred when trying to show the preview of a snapshot. This issue has been fixed and snapshots can now be previewed.
    • [2507] The outgen-init-client.xml.orig file contained a syntax error in the outgen.job.ant.java.memory property. This issue has been fixed, but you need to update the outgen-init-client.xml file if you customized it. See the See the Detailed Release Notes for more information.
  • Scheduler
    • [2424] If a topic was deleted before its tickets were all processed, an error occurred and the Scheduler stopped processing tickets. This issue has been fixed. The Scheduler now skips notifications related to the deleted topic and continues sending notification emails for other tickets.
    • [2428] Notification tickets did not provide the correct from address in the email. This issue has been fixed.
  • Web Author
    • [2401] The Glassfish log4j.xml file was updated to set the logging level to INFO. This ensures that all appropriate messages are provided in the logs.
    • [2467] The Build Manifest feature did not work properly with the Web Author. This issue has been fixed.
    • [2482] The IXIASOFT logo created CSS rendering issues in Internet Explorer 10. This problem has been fixed.
  • Documentation
    • [1852] The DITA CMS User Guide and online help did not describe all the usages of the - search operator. This issue has been fixed and the documentation now covers all usages.
    • [1877] The "Associate DRM files with an XML editor" procedure in the Dynamic Release Management Module User Guide did not specify that the file association had to be specified with the *.product extension. This issue has been fixed.
    • [2244] Links have been added to the HTML version of the Web Author Installation Guide to facilitate navigation between procedures.
    • [2263] Theandelements of the Scheduler configuration file (scheduler.xml) are now documented. See the DITA CMS System Administrator's Guide for more information.
    • [2328] In the "Check the spelling of topics and maps" topic, the documentation stated that "if you select the parent topic of a sub-tree, all of its child topics are checked as well." This is incorrect. Only the topics selected are spell checked. The documentation has been fixed.
    • [2400] Setting the Corba timeout is no longer necessary in the DITA CMS 4.x versions. The documentation has been updated to remove these instructions.
    • [2450] The documentation did not specify that images cannot be compared. A note has been added to that effect in the documentation.
    • [2500] Some files were missing the execution flags for the Linux installation. The procedure now covers all required files.

Requirements

ComponentRequirement

TEXTML Server

  • Ixiasoft TEXTML Server 4.3.5.4164+ (4.3.5.4175 is not supported)
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.6.4188 and up.

DITA CMS Eclipse Client

  • oXygen XML 16.1.0.v2015012213 
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)

DITA CMS Admin plugin

  • TEXTML Admin plugin 4.3.5.4170+

WCR Server
Web Author Server

  • Tomcat 6.0.x + Java JRE 1.7.0_51+ (Java 1.8 is not supported)
  • [Web Author Server only] GlasshFish 3.1.2.x _ Java JDK 1.7.0_51+ (Java 1.8 is not supported)

Output Generator
Scheduler

  • Java JRE 1.7.0_51+ (Java 1.8 is not supported)
 

WCR Client
Web Author Client

  • Java JRE 1.7.0_51 
 

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

 

Build 4.1.5 - 20150409

New Features


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

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

Important notes


  • A new build of the TEXTML Server is available (4.3.5.4175). If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, IXIASOFT recommends that you install this version, otherwise ICU word parsing may not work properly.

Bug Fixes


  • DITA CMS Eclipse Client

    • [704] The Show Preview did not display images and conrefs correctly. This issue has been fixed.
    • [822] When a Published map is archived, a new comment is now added to the custom properties to record details about the operation (name of user who performed the archive, date, and time).
    • [904] When importing images, the option "Resources: Resources have unique names" was displayed, even if it did not apply to images. This option has been removed.
    • [1239] Performance issues occurred when running multiple localizations at the same time without providing an informative error message. The performance issues have been fixed.
    • [1269] The assignment due date was not visible in the Assignments dialog box. This issue has been fixed.
    • [1471] An empty error message was displayed when releasing a topic that contained a conref to a topic with a higher status. The behavior of the DITA CMS was modified so that a topic can be released in this situation.
    • [1597] The Preview view was not reset when a user connected to a new docbase. This issue has been fixed.
    • [1607] The Spellchecker only checked the contents of the map (and not its children) when the Spellcheck command was run from the Search Results view. This issue has been fixed and the Spellchecker now checks all the children of the map.
    • [1849] The Generate Output dialog now lets user select a Ditaval file with the Ditaval view.
    • [2024/2195] The Preview and Dependencies view now provide a "Pin Content" option.
    • [2034] Filtering results in the Ditaval view did not work correctly when the collections were collapsed. This issue has been fixed.
    • [2109] PNG images with transparency were not displayed correctly (background was displayed in black) because they were converted to JPG format. Thumbnails are now saved in PNG format to fix this issue.
    • [2175] The "LastModified by" field in the Search view used the InternalUserID. This behavior was modified and the field now uses the complete user ID, allowing users to filter on the user name.
    • [2184] The Conditionals panel did not work correctly in the Preview View. This panel was removed from the Preview view.
    • [2217] Comments were dropped from imported topics. This issue has been fixed, and the DITA CMS now keeps all comments when importing topics.
    • [2316] The Save Settings button in the Generate Output did not work if an output type was not selected. This issue has been fixed and the Save Settings button works as expected.
    • [2317] Fixed typos in the Generate Output dialog.
    • [2321] In some cases, refreshing a map that contained a link to a deleted topic created an event loop exception. This issue has been fixed.
  • Dynamic Release Management

    • [2043] Is it now possible to configure what determines a unique product.
  • Web Collaborative Reviewer

    • None
  • Output Generator

    • None
  • Scheduler

    • None
  • Web Author

    • None
  •  

 

Features


  • None

 

Requirements

ComponentRequirement

TEXTML Server

  • Ixiasoft TEXTML Server 4.3.5.4164+
  • * ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th is only supported with TEXTML Server 4.3.5.4175 and up.

DITA CMS Eclipse Client

  • oXygen XML 16.1.0.v2015012213
  • Xmax 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700]
  • Java JRE 1.7.0_51+

DITA CMS Admin plugin

  • TEXTML Admin plugin 4.3.5.4170+

WCR Server
Web Author Server

  • Tomcat 6.0.x + Java JRE 1.7.0_51+
  • [Web Author Server only] GlasshFish 3.1.2.x _ Java JDK 1.7.0_51+

Output Generator
Scheduler

  • Java JRE 1.7.0_51+
 

WCR Client
Web Author Client

  • Java JRE 1.7.0_51
 

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