Known Issues

IXIASOFT CCMS Web

• [DEV-6756] The IXIASOFT CCMS Web installation program does not support the following characters in the password as clear text: & ‘ “. These characters can be used if the password is encrypted.

IXIASOFT CCMS Desktop

• [DEV-5878] The Prepare Localization Kit fails if it is configured to generate an output (enabled by default) using DITA OT 2.5.4. Contact IXIASOFT Support for assistance with a workaround.
• [DEV-6106] When importing SVG images that contain JPEG @xlink:href dependencies, the .jpeg files are renamed to .jpg. This causes an image error when viewing the topic in the oXygen editor. The workaround is to edit the SVG image to use a .jpg extension.

Bug Fixes

IXIASOFT CCMS Web

• [DEV-7963] The IXIASOFT CCMS Web installation failed with a “Retries exceeded, couldn’t reconnect to null” error when TEXTML SSL security was enabled. This issue has been fixed.

IXIASOFT CCMS Desktop

• None

IXIASOFT Dynamic Release Management

• None

IXIASOFT Output Generator

• None

IXIASOFT Scheduler

• None

TEXTML

• [DEV-6982] In previous versions of TEXTML 4.4.1.x, some indexes became corrupted. This issue has been fixed.

Documentation

• None

Known Issues

IXIASOFT CCMS Web

• [DEV-6756] The IXIASOFT CCMS Web installation program does not support the following characters in the password as clear text: & ‘ “. These characters can be used if the password is encrypted.

IXIASOFT CCMS Desktop

• [DEV-5878] The Prepare Localization Kit fails if it is configured to generate an output (enabled by default) using DITA OT 2.5.4. Contact IXIASOFT Support for assistance with a workaround.
• [DEV-6106] When importing SVG images that contain JPEG @xlink:href dependencies, the .jpeg files are renamed to .jpg. This causes an image error when viewing the topic in the oXygen editor. The workaround is to edit the SVG image to use a .jpg extension.

Bug Fixes

IXIASOFT CCMS Web

• [DEV-7364] If two users were configured with the same name and email address but with a different domain or username and one was active=”false”, assignments were not correctly displayed in IXIASOFT CCMS Web. This issue has been fixed and users set to active=”false” are ignored.
• [DEV-7356] Force track changes did not work when multiple authoring states were configured for the same role. This issue has been fixed.
• [DEV-7190] Collaborative Review notifications were being sent to reviewers after a review was marked as done. This issue has been fixed.
• [DEV-7039] Internet Explorer and Microsoft Edge displayed some icons, for example, the Revert icon, as very large. This issue has been fixed.
• [DEV-6980] In IXIASOFT CCMS Web, moving a topic to Authoring:complete (or equivalent status) created a blank Revision History entry that was visible in IXIASOFT CCMS Desktop. This was a Known Issue and has been fixed.
• [DEV-6941] When creating maps and topics in IXIASOFT CCMS Web, the configured attribute initial=”true” in map_status.xml and topic_status.xml was ignored. This caused the documents to be created with the wrong status. This issue has been fixed.
• [DEV-6853] IXIASOFT CCMS Web was not able to open a map that referenced a subject scheme with empty keys. This issue has been fixed.
• [DEV-6734] The Collaborative Review in IXIASOFT CCMS Web did not display text contained within <draft-comment> or <required-cleanup> elements. This was a Known Issue and has been fixed.
• [DEV-6717] When a topic was edited in IXIASOFT CCMS Web, the XML was always reformatted to pretty-printed. This was a Known Issue and has been fixed.
• [DEV-6555 The CCMS Web displayed a blank screen when logging in if a user had an orphan topic assigned to them. This issue has been fixed.
• [DEV-6482] If a topic was created in IXIASOFT CCMS Desktop, it was not editable in IXIASOFT CCMS Web. This issue has been fixed.
• [DEV-6480] When creating a topic in IXASOFT CCMS Web and then trying to add it to a different map using IXIASOFT CCMS Desktop, sometimes a “Cannot add object to the map” error appeared. This issue has been fixed.
• [DEV-6363] In IXIASOFT CCMS Web, changing the filtering of assignments between maps and topics did not display the correct assignments in Internet Explorer. This issue has been fixed.
• [DEV-6213] In IXIASOFT CCMS Web, performing a Move on a Collaborative Review removed it from the list of assignments but the number of assignments was not updated. This issue has been fixed.
• [DEV-6018] When map templates included auto-generated topics in IXIASOFT CCMS Web, topics were created but they were not automatically assigned. This was a Known Issue and has been fixed.
• [DEV-4639] After editing a topic that contained conkeyrefs in IXIASOFT CCMS Web, IXIASOFT CCMS Desktop did not display the correct child dependencies in the Dependencies view. This issue has been fixed.

IXIASOFT CCMS Desktop

• [DEV-7692] The upgrade ditaval conversion script did not retain the <revprop> element. This issue has been fixed.
• [DEV-7677] The IXIASOFT CCMS Desktop installation package did not support PowerShell 1.0 or 2.0. This issue has been fixed.
• [DEV-7676] The trigger to check for out-of-scope map links did not run when a map was a child dependency of a build manifest. This issue has been fixed.
• [DEV-7572] The strictParaConstraint.mod and strictSectionConstraint.mod IXIASOFT DTD plugins for DITA 1.2 had an error which caused a The element type “text” was already specified in the content model of the element decl “ph” error to appear when creating topics. This issue has been fixed.
• [DEV-7246] There is a change in behaviour with the debug logs for IXIASOFT CCMS Desktop. When starting IXIASOFT CCMS Desktop, the DITA_CMS.log file is now always created and contains warnings and errors. When starting IXIASOFT CCMS Desktop in debug mode, a new log called DITA_CMS-[date].log is created and contains the debug information.
• [DEV-7223] A map that contained an empty key would not load in DITA Map view. This issue has been fixed.
• [DEV-7179] When generating output on a snapshot, the Ditaval dialog box was blank and did not list existing ditavals. This was a Known Issue and has been fixed.
• [DEV-7174] When re-importing an image that had a filename extension change, for example from .jpg to .png, the existing image in the CCMS was not overwritten. It was created as a new image object. This issue has been fixed.
• [DEV-7055] When using an entity declaration, such as nbsp, in a map title, the map failed to open in DITA Map view. This issue has been fixed.
• [DEV-7009] Copying content in a topic and then using the right-click Paste Special > Paste as link (keyref) menu option displayed a “Could not find mapped key for dropped resource” error. This issue has been fixed.
• [DEV-6935] It was not possible to customize the DITA Map view menu using the eclipseui.xml configuration file. This issue has been fixed and submenu items can now be removed.
• [DEV-6848] In standard deployments, the Resolve Keys button in DITA Map view was not functional. This was a Known Issue and has been fixed.
• [DEV-6839] When double-clicking an entry in the Revision History, IXIASOFT CCMS Desktop did not display the correct revision. This issue has been fixed.
• [DEV-6754] When branching a reused topic in different maps and using the same branch tag, duplicate branched topics were created in the authoring cycle. This issue has been fixed and only one branched topic is created.
• [DEV-6682] If an outputclass was defined for a taxonomy term, the outputclass was removed when editing the term via the Taxonomy view. This issue has been fixed.
• [DEV-5867] For the concurrent localization method, if the localization kit was configured to export objects with the status Localization:review and if the status Localization:review was configured to have Localization:tb translated as the next state, the Prepare Kit action moved objects from Localization:review to Localization:tb translated. This issue has been fixed and the objects remain at Localization:review.
• [DEV-2288] For the concurrent localization method, pre-localization kits did not set the translate=”yes” attribute correctly. This issue has been fixed.
• [DEV-2105] When a topic title contained a keyref and did not include any text, a snapshot of the map was able to be created without error, but a “Title cannot be null or empty” error was displayed when trying to publish or branch the snapshot. This issue has been fixed.

IXIASOFT Dynamic Release Management

• [DEV-5543] Renaming a DRM version required all content within the version to be lockable. This issue has been fixed and DRM versions with content at Authoring:done can now be renamed.
• [DEV-3696] In DRM deployments, when a topic title contained a keyref and did not include any text, a “Title cannot be null or empty” error was displayed when trying to create a version from a tag that contained the topic. This issue has been fixed.

IXIASOFT Output Generator

• [DEV-6868] When using a high DPI monitor, the Generate Output dialog box did not show all available selections. This was a Known Issue and has been fixed.
• [DEV-6755] When generating an output, the ditaval was missing the processing instruction <?ixiasoft.ditaval.title ?> and <?ixiasoft.ditaval.description ?>. This issue has been fixed.

IXIASOFT Scheduler

• None

TEXTML

• [DEV-7052] TEXTML was case sensitive when checking the login domain for a user. If a user locked a map or topic using an all lowercase domain and then logged in using an all uppercase domain, the IXIASOFT CCMS Web would hang when loading the My Assignments Page. This issue has been fixed.

Documentation

• None