Bug Fixes

IXIASOFT CCMS Web

• [DEV-15927] Encrypted passwords were not supported for the IXIASOFT CCMS Web installation script. This issue has been fixed.
• [DEV-15908] The CCMS Web Oxygen license for 2021 is included in this Service Pack.

IXIASOFT CCMS Desktop

• [DEV-15996] If a map was open in DITA Map view and a user performed a Clear Map action, the Validate Links option remained grayed out after opening a new map. This issue has been fixed.
• [DEV-15904] When adding a new row in the Relationship Table Editor perspective, rows were added at the top of the table and not at the insertion point. This issue has been fixed. A workaround is to refresh the map which will show the correct location of the newly inserted row.

CCMSUtils

• Starting with 6.3 SP2, cmsutils has been renamed to CCMSUtils and the User Guide is now included in the .zip package on the Downloads site.

IXIASOFT Dynamic Release Management

• [DEV-15706] In the DRM Synchronization perspective, sometimes when trying to merge a topic that did not have any changes between versions, a Merge Objects has encountered a problem error message appeared. This issue has been fixed.

IXIASOFT Output Generator

• [DEV-15925] On a Linux system, the 6.3 Output Generator would start and then immediately terminate when running as the service user account instead of the root user account. This issue has been fixed.

IXIASOFT Scheduler

• [DEV-15926] On a Linux system, the 6.3 Scheduler would start and then immediately terminate when running the Output Generator as the service user account instead of the root user account. This issue has been fixed.
• [DEV-14871] The Scheduler assignation_ticket.xsl configuration file had UTF8-BOM instead of UTF-8 encoding. This issue has been fixed.

TEXTML

• None

Known Issues

IXIASOFT Output Generator

• [DEV-13458] Customers that have set up the Output Generator to have additional libraries (jar files) for custom processing such as Fluid Topics, need to edit the numbering in the conf/client/classpath.conf configuration file to begin with either 200 or 300. For example, wrapper.java.classpath.200=../libs/fluidtopics/ftconnector.jar

Bug Fixes

IXIASOFT CCMS Web

• [DEV-15894] The CCMS Web installer script failed to complete the upgrade if reverse proxy was set up. This issue has been fixed.

IXIASOFT CCMS Desktop

• None

IXIASOFT Dynamic Release Management

• None

IXIASOFT Output Generator

• None

IXIASOFT Scheduler

• None

TEXTML

• None

Known Issues

IXIASOFT Output Generator

• [DEV-13458] Customers that have set up the Output Generator to have additional libraries (jar files) for custom processing such as Fluid Topics, need to edit the numbering in the conf/client/classpath.conf configuration file to begin with either 200 or 300. For example, wrapper.java.classpath.200=../libs/fluidtopics/ftconnector.jar

Bug Fixes

IXIASOFT CCMS Web

• [DEV-15521] Long map titles plus long branch names caused CCMS Web to truncate the top menu and breadcrumb display in the map editor. This issue has been fixed.
• [DEV-15432] In a DRM deployment, users were unable to search for and insert a conref into a topic using CCMS Web. This issue has been fixed.
• [DEV-15409] In CCMS Web, inserting conrefs, cross-references, and related links was only available to users in the Advanced Users group. These features are now available for the Contributor role as well.
• [DEV-15317] In CCMS Web, sometimes the Insert Element option did not show a list of elements to select. This issue has been fixed.
• [DEV-15316] After checking in a topic in CCMS Web, editing icons were clickable and the topic could be edited even though the Check In button was not available. This issue has been fixed.
• [DEV-15264] If an output in CCMS Web failed, the log zip file could not be opened if it contained only the log file and no content. This issue has been fixed.
• [DEV-15171] Some maps were not found when searching for a context map in the advanced search panel in CCMS Web. This issue has been fixed.
• [DEV-15108] After inserting a newly created SVG image into a topic in CCMS Web, the thumbnail was not created. This issue has been fixed.
• [DEV-15086] In 6.2 CCMS Desktop, double-clicking on an annotation for a Collaborative Review displayed a This annotation does not contain the topic id so it can not open error message. This issue has been fixed.
• [DEV-14984] If a custom trigger returned an unexpected error, CCMS Web became unstable. This issue has been fixed.
• [DEV-14833] In a DRM deployment, the release action in CCMS Web failed with a Cannot check in error message if a map contained an invalid keyref. This issue has been fixed.
• [DEV-14758] If a topic was at an end state and the parent DRM version was closed, users were able to change the topic status in CCMS Web. This issue has been fixed and the change status action is prevented.
• [DEV-14517] When creating an image in CCMS Web, the configuration default for translate=”yes” was not applied. This issue has been fixed.
• [DEV-14502] The CCMS Web search did not search the description of a template, it only searched the title. This issue has been fixed.
• [DEV-14278] When attempting to open a map with topic stubs, a blank page appeared. This issue has been fixed.
• [DEV-14234] When editing a topic and inserting a conref that is a table element, a validation error appeared. This issue has been fixed.
• [DEV-14196] In CCMS Web, images exported on a MAC had incorrect filename extensions. This issue has been fixed.
• [DEV-14187] If maps had a different workflow than topics, a Sorry, move didn’t work error message appeared when moving a topic from Authoring:done to Authoring:work. This issue has been fixed.
• [DEV-14104] If the web browser was resized and a topic was edited by clicking the More Options button, the topic did not open on the first attempt. This issue has been fixed.
• [DEV-13949] The CCMS Web Assignments page was blank when an object included a deprecated role as part of its assignments. This issue has been fixed.
• [DEV-13924] Clearing the Advanced Search filters did not remove the Assignment filters. This issue has been fixed.
• [DEV-13916] A Google Chrome Sign in dialog box appeared if the CCMS Web session was left idle. This issue has been fixed and users are now redirected to the CCMS Web login page.
• [DEV-13915] When a search was performed, the browser page was blank and there was no indication that the search was being performed. This issue has been fixed and a spinner is now displayed.
• [DEV-13859] Pressing the Enter key after an existing table within a topic, created an invalid table. This issue has been fixed.
• [DEV-13793] Topic creation failed if the map did not have the version.filename custom property. This issue has been fixed.
• [DEV-13787] When a change status failed in CCMS Desktop due to a custom trigger, a detailed error message appeared. In CCMS Web the same operation failed with a generic Sorry the move did not work error message. This issue has been fixed.
• [DEV-13673] Installing CCMS Web on a Linux system failed when it was installed in a folder different from the default and the service account was different from root. This issue has been fixed.
• [DEV-13672] CCMS Web did not load when using the Internet Explorer browser. This issue has been fixed.
• [DEV-12638] In a DRM deployment, when trying to insert a cross-reference in a topic in CCMS Web and clicking Search to see all topics in the context map, topics in sub-libraries were not listed. This issue has been fixed.
• [DEV-12315] When SCCM is used to manage Windows updates on the server, the CCMS Web installation script failed when setting the Oxygen license. This issue has been fixed.
• [DEV-11175] When adding an annotation to a footnote in a Collaborative Review, the text was highlighted but the annotation was not added. This issue has been fixed.

IXIASOFT CCMS Desktop

• [DEV-15695] A blank error message appeared when localizing multiple languages from a snapshot. This issue has been fixed.
• [DEV-15362] In CCMS Desktop, fields in the Properties view were blank when it was positioned in the same group as the DITA Map view. This issue has been fixed and the Properties view is now located in a separate group.
• [DEV-15275] When localizing content, sometimes An exception occurred while overwriting the XML content error appeared. This issue has been fixed.
• [DEV-14886] When importing images with the Images have unique names checkbox selected, the images imported without a DRM version. This issue has been fixed.
• [DEV-14835] Editing an image directly in CCMS Desktop and then performing the Localize action did not update the image correctly in the local workspace. This issue has been fixed.
• [DEV-14745] If a map was referenced in another map as a cross-reference instead of as a dependency, the Validate Links action reported the map as out-of-scope. This issue has been fixed.
• [DEV-14561] A blank entry was created in the revision history when performing a Publish action on a map that included a topic referencing elements from another topic. This issue has been fixed.
• [DEV-14495] With concurrent localization, if an element such as a <prereq> contained paragraphs with text but no text itself, the CCMS did not recognize changes to be translated and topics were set to Localization:review instead of Localization:tb translated. This issue has been fixed.
• [DEV-14336] Opening a topic for the first time from a map open in DITA Map view, sometimes displayed a red X in the editor. Opening the topic a second time was successful. This issue has been fixed.
• [DEV-14320] Importing a topic or a map a second time with the Update existing documents checkbox selected created invalid content in the CCMS if the doctype was changed in between imports. This issue has been fixed.
• [DEV-14188] When using a pivot language and auto-translation, the translate=”no” attribute was inherited and prevented the translation of elements to the third language. This issue has been fixed.
• [DEV-14129] When using a pivot localization language, the reference PDF in the originals.zip file was created in the authoring language instead of the pivot language. This issue has been fixed.
• [DEV-13914] CCMS Desktop sometimes had performance issues when right-clicking on a map in DITA Map view and clicking Sub-tree > Release. This issue has been fixed.
• [DEV-13665] Using the Select in map action from the Search Results view, the selected topic was displayed twice in the map in DITA Map view. Users had to restart CCMS Desktop for the map to display correctly. This issue has been fixed.
• [DEV-13475] For an image that was localized and set to Localization:done (or equivalent end status), editing the image in the authoring cycle and localizing it again did not show the updated image in the localization kit. This issue has been fixed.
• [DEV-13474] When localizing an image that was previously localized, the CCMS would sometimes export the previous image in the localization kit and use the old image metadata when importing the localized images. This issue has been fixed.
• [DEV-13349] Some SVG images appeared blacked out in CCMS Desktop. This issue has been fixed.
• [DEV-13126]  The localization Prepare Kit action now updates the local user’s cache for each object to make sure the kit is up to date from the TEXTML server.
• [DEV-12058] Sometimes when bulk selecting objects to change status, a Cannot change status dialog box appeared when some of the topics were child dependencies of other topics. This issue has been fixed.
• [DEV-11977] When localizing a map with incremental localization, if a topic had changed but the parent map did not and they were not at an end state, the localization status of the parent map was not cascaded. This issue has been fixed.
• [DEV-9546] Citrix users sometimes encountered an Error occurs trying to create new folder message when trying to create a new ditaval folder. They also received an An error occurred and labels could not be unlocked message when trying to add new labels to the configuration. These issues have been fixed.
• [DEV-8351] If an Output Generator Output Format had a lot of user properties, the Generate Output dialog box display was truncated and users could not see the full list. This issue has been fixed.
• [DEV-3749] Maps or topics would sometimes lose their ID after being released. In this scenario, the release will now fail and the DITA_CMS.log file in the workspace will contain details of the error that can be sent to IXIASOFT Support.

IXIASOFT Dynamic Release Management

• [DEV-14167] The Revert To action in the Revision History dialog box is now disabled for DRM objects including libraries, products, versions, and releases.
• [DEV-13163] After doing a synchronization between two DRM versions, Build Manifest objects belonged to more than one DRM version. This issue has been fixed.
• [DEV-13076] Renaming large DRM versions causes Java heap errors when the maximum allocated memory is set to 2G or less. Before performing large operations such as renaming or cloning DRM versions, it is recommended to restart CCMS Desktop to clear the cache.

IXIASOFT Output Generator

• [DEV-15645] When generating a redline PDF using OT 3.5.2, the log reported a java.nio.file.InvalidPathException: Illegal char <:> error message. This issue has been fixed.
• [DEV-14672] In the 6.2 Output Generator, the .res files were not correctly extracted. This issue has been fixed.
•  [DEV-13837] There was a typo in the classpath.conf file for the 6.1 and 6.2 Output Generator. The entry wrapper.java.classpath.15=../libs/ant-jsh-1.10.7.jar should have been wrapper.java.classpath.15=../libs/ant-jsch-1.10.7.jar. This issue has been fixed.
• [DEV-13691] The Output Generator data/commontargets-deprecated.xml configuration file was missing the ixiasoft.addingchunkatt target. This issue has been fixed.
• [DEV-13687] When creating a Collaborative Review using a customized Output Generator, a NoSuchMethodError:org.appache.commons.io.FileUtils.moveFileToDirectory error appeared. This issue has been fixed.

IXIASOFT Scheduler

• [DEV-14883] The 6.2 Scheduler /conf/classpath.conf configuration file contained invalid characters. This issue has been fixed.
• [DEV-14570] The Batik JAR files in the classpath.conf configuration file were not updated to reflect new filenames. This issue has been fixed. Also, entries for js.jar and pdf-transcoder.jar have been removed since they are no longer included in the package.

TEXTML

• None

Known Issues

IXIASOFT Output Generator

• [DEV-13458] Customers that have set up the Output Generator to have additional libraries (jar files) for custom processing such as Fluid Topics, need to edit the numbering in the conf/client/classpath.conf configuration file to begin with either 200 or 300. For example, wrapper.java.classpath.200=../libs/fluidtopics/ftconnector.jar