Ixiasoft CCMS

IXIASOFT CCMS V6.5

December 2, 2021

Important Notes

Important

Install and upgrade documentation is available to current customers on the Downloads website.

Bug Fixes

IXIASOFT CCMS Web

  • This service pack replaces the Log4j Apache logging component with version 2.16.0.

IXIASOFT CCMS Desktop

  • None

IXIASOFT Dynamic Release Management

  • None

IXIASOFT Output Generator

  • This service pack replaces the Log4j Apache logging component with version 2.16.0.

IXIASOFT Scheduler

  • None

TEXTML

  • None

Known Issues

  • Opening maps with Oxygen DITA Map Editor using version 23 showed File not found validation errors for topicrefs. This happens the first time you open a map because the content is not synchronized to your workspace. If you open with XML Editor with resolved topics, the errors clear. To prevent performance issues downloading all the content to the user’s workspace, this issue will not be fixed in CCMS Desktop.
  • [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

Important Notes

Important

Install and upgrade documentation is available to current customers on the Downloads website.

Bug Fixes

IXIASOFT CCMS Web

  • [DEV-17718] Maps that had keys defined in a submap instead of in the main map, sometimes had a Sorry, could not load map in CCMS Web Structure view. The maps would open in Content view. This issue has been fixed.
  • [DEV-17524] When editing a topic in CCMS Web and searching for an image to insert, the search took a long time if the search values were left blank. This issue has been fixed.
  • [DEV-17476] Sometimes, a Collaborative Review was created at Authoring:creating status instead of Authoring:review. This issue has been fixed.
  • [DEV-17448] After resizing the browser window, users could not check in documents using the More options button.
  • [DEV-17391] In CCMS Web, some maps reported out-of-scope errors for submaps when changing status. This issue has been fixed.
  • [DEV-17368] Keys that were defined in a map using CCMS Web did not appear after clicking the Insert Links and variables defined as DITA keys icon. This issue has been fixed.
  • [DEV-17340] After upgrading CCMS Web to 6.4 SP1, users were not able to load their assignments or favorites. This issue has been fixed.
  • [DEV-17303] When adding a topic to a map in CCMS Web Structure view, a Key definition not found validation error was displayed, and the topic title was not resolved. This issue has been fixed.
  • [DEV-17285] Some Collaborative Reviews in CCMS web remained locked by the system during a Move operation and were displayed with a broken graphic in the Assignments view. This issue has been fixed.
  • [DEV-17284] User-defined keys did not resolve in topics for CCMS Web. This issue has been fixed.
  • [DEV-17257] When a Collaborative Review in CCMS Web was left open in a browser for an extended period and the session timed out, there was no indication of the timeout. This issue has been fixed.
  • [DEV-16940] After a single sign-on login was completed, CCMS Web did not correctly redirect to the Assignments page. This issue has been fixed.
  • [DEV-16937] When a user had both a Writer and Information Architect role, creating a new map in CCMS Web created the map at a review state instead of the initial working state. This issue has been fixed.
  • [DEV-16776] Sometimes the CCMS Web Tomcat process would hang, and users were unable to login. The log file showed a java.io.IOException: Too many open files error message. This issue has been fixed.
  • [DEV-16772] In the CCMS Web Advanced Search panel, DRM products and libraries were not sorted alphabetically. This issue has been fixed.
  • [DEV-16760] In 6.3 SP3, the default user parameters specified in the Output Generator preprocessors.xml configuration file, were not populated in CCMS Web. This issue has been fixed.
  • [DEV-16721] In CCMS Web, table entry tags were sometimes superimposed. This issue has been fixed.
  • [DEV-16711] In CCMS Web, some context maps were not appearing in the advanced search. This issue has been fixed.
  • [DEV-16563] Users sometimes saw a blank Search Results page in CCMS Web when logged in with a username that contained mixed case. This issue has been fixed.
  • [DEV-16467] If the Writer role was renamed in a configuration, the Collaborative Review open topic icon did not appear in CCMS Web. This issue has been fixed.
  • [DEV-16228] In CCMS Web, attributes that contained an uppercase character did not copy to clipboard. This issue has been fixed.
  • [DEV-16172] In CCMS Web, the assignment indicators were not fully displayed. This issue has been fixed.
  • [DEV-16170] In CCMS Web, the locid attribute was displayed by default in Content View. This issue has been fixed.
  • [DEV-16159] Users were unable to create a Collaborative Review in CCMS Web for a map that contained a topic with a self-reference. The log file in My Outputs showed a The file does not exist error. This issue has been fixed.
  • [DEV-15892] Sometimes a nested map would not load in Structure view. 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.

IXIASOFT CCMS Desktop

  • [DEV-17475] In a DRM deployment using a pivot language, the CCMS auto-translated topics on their first localization cycle. This issue has been fixed.
  • [DEV-17447] When trying to create a topic in CCMS Desktop using saved settings for a topic with more than one subfolder, an error dialog box appeared with an empty description. This issue has been fixed.
  • [DEV-17442] In CCMS Desktop, sometimes creating a snapshot failed with a String index out of range: -1 error message. This issue has been fixed.
  • [DEV-17256] Reports were not filtered according to the saved date criteria. This issue has been fixed.
  • [DEV-16939] When localizing a published map using a pivot language, the translate=”no” attribute was incorrectly inherited from the pivot language. This issue has been fixed.
  • [DEV-16936] When the metadata of an image was modified and then localized, the system comment in the Revision History showed that the image was auto-translated but the image content was replaced with the authoring source image. This issue has been fixed.
  • [DEV-15817] If topics in the localization cycle were already locked when the parent map was localized, an Unable to lock the document error message appeared. This message has been changed to Unable to lock, the document is locked by another user.
  • [DEV-15758] For large topics with a lot of ixia_locid attributes, the Localize action took a long time. Performance has been improved and where possible IXIASOFT recommends splitting large topics greater than 2Meg in size into smaller topics.

IXIASOFT Dynamic Release Management

  • None

IXIASOFT Output Generator

  • None

IXIASOFT Scheduler

  • [DEV-17255] The Scheduler Activity Report failed to process tickets if any were for topics that contained special characters. This issue has been fixed.
  • [DEV-16973] The Scheduler did not send email notifications when a Collaborative Review that was created on the web was assigned to a user. This issue has been fixed.

TEXTML

  • None

Known Issues

  • Opening maps with Oxygen DITA Map Editor using version 23 showed File not found validation errors for topicrefs. This happens the first time you open a map because the content is not synchronized to your workspace. If you open with XML Editor with resolved topics, the errors clear. To prevent performance issues downloading all the content to the user’s workspace, this issue will not be fixed in CCMS Desktop.
  • [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