Ixiasoft CCMS

IXIASOFT CCMS V6.1

26 mars 2020

With new features like generate output, favorites, and dependencies view, IXIASOFT CCMS 6.1 furthers the evolution of the CCMS towards a completely web-based platform.

Most importantly, this version enables technical writers to do more in the web. Generate output allows users to see the final result of their work, favorites enables faster access by letting users classify what they are working on, and dependencies view is critical for letting users see where an object is used.

Generate Output

Ability to generate an output

  • Warning and errors automatically extracted
  • Possibility to select and search for a Ditaval
  • Asynchronous mode to generate more than one output at the same time

List of outputs

  • All the outputs generated are now saved in the same place
  • Automatic and configurable clean-up of the list of outputs
  • Download an output as many times as a user wants

Favorites

New way to manage the objects a user wants to work on

  • User can filter favorites
  • Add a favorite object from anywhere in the CCMS
  • Add, remove, edit, rename any folder
  • Drag and drop to easily manage all the objects and folders

Dependencies View

View the dependency of each object​​​​

  • Go from an object dependencies to another with just one click
  • Edit or move dependencies directly

Same action button

  • Filter per branch
  • Infinite scroll for longs list of objects
  • In DRM, shows product name and ALL branches
  • Respects content level security

Server-side requirements

IXIASOFT TEXTML Server

  • IXIASOFT TEXTML Server 4.4.1.5239 and up
  • Hardware
    • CPU: Quad-core CPU
    • Memory: a minimum of 8 GB RAM per server (depending on DocBase size)
    • Disk: Fast storage with low latency is recommended for DocBase storage; either SSD drives or high-performance RAID arrays
  • Operating system
    • Windows Server®
      • Windows Server® 2016 – recommended
      • Windows Server® 2012 R2 64-bit
      • Windows Server® 2012 64-bit
      • Windows Server® 2008 R2 64-bit
    • Linux® Red Hat®/CentOS version 7.x 64-bit only

IXIASOFT CCMS Web Server

  • Apache Tomcat® 9 (9.0.31) (provided by IXIASOFT during the installation)
  • Java™ JDK 11, 64-bit (provided by IXIASOFT during the installation)
  • IXIASOFT CCMS Content Store 6.1
  • Collaborative Review feature requires DITA OT 2.3.1 minimum
  • Operating system
    • Windows Server®
      • Windows Server® 2016 – recommended
      • Windows Server® 2012 R2 64-bit
      • Windows Server® 2012 64-bit
      • Windows Server® 2008 R2 64-bit
    • Linux® Red Hat®/CentOS version 7.x 64-bit only (changed Nov 28)

IXIASOFT CCMS Admin plugin

  • TEXTML Admin plugin 4.3.7.4299 and up
  • CCMS Admin plugin 6.1.xxx

Output Generator

  • Java 1.8.171 and up; 64-bit
  • Rendering software (such as Apache FOP, Antenna House, Miramo or RenderX)

Scheduler

  • Java 1.8.171 and up; 64-bit

Client-side requirements

IXIASOFT CCMS Web

  • The browser must support HTML5, CSS3, and JavaScript ES5 and must allow cookies
  • On Windows®:
    • Last 3 major versions of Google Chrome™ – recommended
    • Last 3 major versions of Mozilla® Firefox®
    • Last 3 major versions of Microsoft® Edge™
    • Microsoft® Internet Explorer® 11
  • On Linux®:
    • Last 3 major versions of Google Chrome™ – recommended
    • Last 3 major versions of Mozilla® Firefox®
  • On Mac®:
    • Last 3 major versions of Google Chrome™ – recommended
    • Apple® Safari® 10.0.1 and up
    • Last 3 major versions of Mozilla® Firefox®

IXIASOFT CCMS Desktop

  • Oxygen XML 21.x with a minimum version of Oxygen 21.0
  • Eclipse 4.7.3 64-bit (uses the eclipse-4.7.3_win32_x86_64_6.1.x.zip package available from the IXIASOFT download website)
  • Java® 1.8.172 64-bit (included the Eclipse package)
  • Versions of OS supported:
    • For local install:
      • Windows® 10 64-bit version – recommended
      • Windows 8.1 64-bit
      • Windows 8 64-bit
      • Windows 7 64-bit
    • For remote solutions (RDP or Citrix):
      • Windows Server® 2016 64-bit – recommended
      • Windows Server 2012 R2 64-bit
      • Windows Server 2012 64-bit
      • Windows Server 2008 R2 64-bit
    • For macOS®:
      • Catalina® (version 10.15) – recommended
      • Mojave® (version 10.14)
      • High Sierra® (version 10.13)

Important

The IXIASOFT CCMS Desktop requires good communication with the server components. The latency needs to be better than 50 ms.

Build Numbers
Hot Fix 1 - April 3, 2020

Important Notes

Important

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

Bug Fixes

IXIASOFT CCMS Web

  • [DEV-12180]  If the system/conf/roles.xml configuration file contained a reference to the Build Manifest object type, CCMS Web would not start. This issue has been fixed.

IXIASOFT CCMS Desktop

  • None 

IXIASOFT Dynamic Release Management

  • None 

IXIASOFT Output Generator

  • None 

IXIASOFT Scheduler

  • None

TEXTML

  • None

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-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.
Initial Release - March 26, 2020

Important Notes

Important

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

Bug Fixes

IXIASOFT CCMS Web

  • [DEV-12027] Expanding the document details in CCMS Web sometimes did not display the Checked out by or Last modified by information. This issue has been fixed.
  • [DEV-12014] When performing a Fork and Edit on a topic in multiple DRM versions, sometimes a “Cannot fork and edit document” error appeared. This issue has been fixed.
  • [DEV-11841] In a Standard deployment, if a map was published and used a custom published tag defined in the configuration file system/conf/publishtags.xml, assigning the map to a user caused the CCMS Web assignments list to be empty. This issue has been fixed.
  • [DEV-11823] When expanding a map in CCMS Web, users were unable to scroll to the bottom of the map. This issue has been fixed.
  • [DEV-11790] The Reuse Content icon in CCMS Web did not display a full list of reusable content. This issue has been fixed.
  • [DEV-11772] When creating an image in CCMS Web, the image was not automatically assigned to the Writer role. This issue has been fixed.
  • [DEV-11656] If the system/webplatform/configuration/webroles.xml configuration file contained a role with a status, the ForceTrackChanges option did not work. For example, <role name= »Contributor » status= »Authoring:contribute »>. This issue has been fixed.
  • [DEV-11365] In some DRM deployments, CCMS Web became unresponsive when opening a topic for editing. This issue has been fixed.
  • [DEV-11040] If a topic was included in a lot of DRM versions, the information in the CCMS Web Details panel overlapped. This issue has been fixed.
  • [DEV-10844] When editing a map in CCMS Web and clicking the Show Topic Titles icon, a “This mode is unavailable for documents with references due to performance reasons” error appeared. This issue has been fixed.
  • [DEV-10843] When editing a large map and changing the Style selection to show the topic titles, CCMS Web became unresponsive. This issue has been fixed.
  • [DEV-10840] When selecting a layout style in CCMS Web, maps displayed topic titles twice. This issue has been fixed.
  • [DEV-10835] When editing a topic in CCMS Web and selecting the option to fork the topic, the context map did not appear after selecting the DRM version. This issue has been fixed.
  • [DEV-10834] When cloning a version, the CCMS Web logs showed a « ditamap is not a containerpart » error message. This issue has been fixed.
  • [DEV-10824] When doing a fork and edit of a topic in CCMS Web, the context map and assignments were not retained. This issue has been fixed.
  • [DEV-10820] In some configurations, when trying to insert an image into a topic that was created in CCMS Web and the parent map was created in CCMS Desktop, a “Sorry, image import didn’t work” error message appeared. This issue has been fixed.
  • [DEV-10819] In some configurations, when trying to insert an image into a topic in CCMS Web and the topic was created in CCMS Desktop, a “Sorry Insert and Image reference didn’t work” error message appeared. This issue has been fixed.
  • [DEV-10813] CCMS Web sometimes became unresponsive when editing a large map. This issue has been fixed.
  • [DEV-10708] When trying to insert a Visio or Powerpoint image into a topic in CCMS Web, a « Please upload an image » error appeared. This issue has been fixed and these image formats are now supported.
  • [DEV-10706] After reviewing a document in CCMS Web and performing a Move action, the Scheduler was sending blank activity report emails. This issue has been fixed.
  • [DEV-10703] When editing a topic, CCMS Web did not offer a context map if the topic was in a child library. This issue has been fixed.
  • [DEV-10698] When editing a map in CCMS Web, parent topic references displayed their ID but not their title. This issue has been fixed.
  • [DEV-10696] In CCMS Web, users were able to insert <list> elements in invalid locations within a topic. This issue has been fixed.
  • [DEV-10567] When releasing a topic that contained invalid XML, the release appeared to be successful and did not display an error message. This issue has been fixed and an error message now appears.
  • [DEV-8853] Performance has been improved to load the assignments page in CCMS Web.
  • [DEV-8645] When using CCMS web with either Firefox or Opera, a “The performed action is not supported » error appeared when editing a topic and using the backspace or delete key. This issue has been fixed.
  • [DEV-8446] When a change status failed in CCMS Desktop due to a custom trigger, the error message provided information about the cause. In CCMS Web the same operation failed with a generic “Sorry the move did not work” error message. This issue has been fixed and the error message is more clear.
  • [DEV-6850] When creating a Collaborative Review, the review could be assigned to inactive users. This issue has been fixed.
  • [DEV-6280] When creating a Collaborative Review or Approval, all users could be selected as assignees which caused excessive notification emails from the Scheduler. This issue has been fixed and users have to be selected individually.

IXIASOFT CCMS Desktop

  • [DEV-11567] CCMS Desktop experienced performance issues when opening a map that contained a subject scheme with the element <hasKind>. This issue has been fixed.
  • [DEV-11493] When importing a map in CCMS Desktop using the Update Existing Documents option, a “File already imported more than once” error appeared for topics that contained previously imported images. This issue has been fixed.
  • [DEV-11400] When using a Citrix farm with a common workspace folder for CCMS Desktop, sometimes users could not release locked documents. This issue has been fixed.
  • [DEV-11387] Some icons from the Oxygen toolbar were missing including Apply Transformation Scenario, Configure Transformation Scenario, View In Browser, Format and Indent, Check Spelling, and Symbols. This issue has been fixed.
  • [DEV-11219] Deleting content from a resource object in CCMS Desktop did not remove the file from the .res file. This issue has been fixed.
  • [DEV-11159] Ditavals were always created in English even if the system/conf/languages.xml file had a default language set. This issue has been fixed and ditavals are now created in the default language.
  • [DEV-11148] If a map had a key defined on a topicref, the Oxygen editor Link > Cross Reference action did not list any keys in the Key drop-down list. This issue has been fixed.
  • [DEV-10968] When inserting a custom element into a bookmap in CCMS Desktop, the element was placed after the <containerref> element which broke the map structure. This issue has been fixed.
  • [DEV-10883] When inserting a PDF as a HiRes image source in CCMS Desktop, a “The selected file could not be opened” error message appeared. This issue has been fixed.
  • [DEV-10713] Opening a map with several submaps in DITA Map view sometimes took a long time. This issue has been fixed.
  • [DEV-10677] If the metadata of an image was modified and the image was then removed from the workspace, the image appeared broken in the Show/Edit Image dialog box. Localization operations on the image would also fail. This issue has been fixed.
  • [DEV-10503] When an image was imported and inserted into a topic, the image was not resolved when the topic was opened. This issue has been fixed.
  • [DEV-10361] Some content in a pre-localization kit was set to translate=”no” instead of translate=”yes”. This issue has been fixed.
  • [DEV-10317] In CCMS Desktop, an “Unhandled event loop exception” error appeared in the Error Log view when right-clicking on a table entry. This issue has been fixed.
  • [DEV-10149] Users were able to insert localized content such as images into authoring topics. This issue has been fixed and localized content can no longer be inserted into the authoring cycle.
  • [DEV-10148] When creating a ditaval folder, the New Ditaval Folder dialog box had the text “Select the parent folder” for a text input field. The text now says “Enter the folder name”.
  • [DEV-10011] Documents were moved from Localization:done to Localization:do not translate when there was no change made to the Authoring content. The documents should have remained at Localization:done. In addition, documents set to Localization:do not translate no longer cascade their parents to Localization:tb translated. These issues have been fixed.
  • [DEV-9853] Editing a ditaval in the Oxygen XML editor no longer used the CSS provided by Oxygen. This CSS provided the ability to use drop-down lists to set values such as include or exclude. A custom framework is now included in the CCMS base configuration and can be manually added to the system configuration.
  • [DEV-9790] 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. This issue has been fixed.
  • [DEV-9756] In the Ditaval view, users were able to edit ditavals at any status independent of the configuration specified in the accessrights.xml configuration file. This issue has been fixed.
  • [DEV-9750] Users were unable to compare two ditaval files. This issue has been fixed.
  • [DEV-9703] The translate=”yes” attribute was set correctly in authoring content but was not always set correctly in the corresponding localization source. This issue has been fixed.
  • [DEV-9144] When generating a pre-localization kit in XLIFF format, the root element was missing the attribute importable= »false ». This issue has been fixed.
  • [DEV-9034] When adding taxonomy terms to a map and then applying them to the map, the terms were applied in a different order than they were added. The order of the applied taxonomies would also change on a refresh of the Taxonomies Terms view. These issues have been fixed.
  • [DEV-8972] When attempting to do a redline compare on a map, snapshots to compare against were listed in random order and the column headings did not allow sorting. This issue has been fixed. Columns are now sorted by the Title column and the column headings also allow sorting.
  • [DEV-8881] When editing a topic from a map that used a Subject Scheme, the defined attributes sometimes did not appear as selections or existing attributes that were set displayed a “is not in the set of allowed values defined in the subject scheme “ error. These issues have been fixed.
  • [DEV-8876] In the Ditaval view, nothing happened when right-clicking on a ditaval folder and clicking Clone. The folder was not cloned and an error did not appear. This option has been disabled in the right-click menu.
  • [DEV-8388] The CCMS was writing images to the workspace even if the image was unchanged. This caused performance issues when editing topics with images. This issue has been fixed.
  • [DEV-8107] Editing a ditaval that had all conditions set to exclude changed the values back to include. This issue has been fixed.
  • [DEV-7931] When localizing a branched map an error sometimes occurred but the Localization Results dialog box did not include an error message. The Error Log view showed a NullPointerException for SequentialLocalizationManagerService.getAllBranchedFromFilename. This issue has been fixed.
  • [DEV-7675] In CCMS Desktop, the scroll bar was not available when opening a ditaval from the Ditaval view. In order to view the entire ditaval, users had to edit the ditaval. This issue has been fixed.
  • [DEV-6483] When localizing a map that contained two topics referencing the same conref, sometimes the localization of the second topic failed with a message indicating that it was at Localization:review status. This issue has been fixed.
  • [DEV-6189] When performing a Validate Links action in DITA Map view, errors displayed the topic ID instead of the topic filename. This issue has been fixed and both are now displayed.
  • [DEV-6019] If you opened one map in the DITA Map view and another map in the DITA Map Editor, it was not possible to set conditions in the DITA Map view. This issue has been fixed.
  • [DEV-6010] For concurrent localization, generating an XLIFF localization kit took longer than necessary and would sometimes fail with an « Out of Memory » error. This issue has been fixed.
  • [DEV-5929] When branching a map in a standard deployment, sometimes an “Unable to display branched map in map view” error appeared in the Error Log view. This issue has been fixed.
  • [DEV-5304] If a topic contained a cross-reference to another topic and the <xref> element did not have any link text, the Oxygen Results view showed a “URI has a fragment component” warning. This issue has been fixed.
  • [DEV-5073] Editing or opening a ditaval in the Ditaval view did not show the associated subject scheme. This issue has been fixed. To apply this fix, existing ditavals need to be edited to re-select the subject scheme and conditions and then released.
  • [DEV-4904] For concurrent localization, the exported XLIFF file contained content in <g> tags instead of the <trans-unit> tags. This issue has been fixed.
  • [DEV-3664] Oxygen editor linking has been improved to provide key resolution when using the right-click Paste Special menu option or the Reuse Content button. This enhancement requires version 21 of Oxygen.
  • [DEV-3611] Sometimes the localization auto-translation feature had content with a parent element set to translate=”no” and a child element set to translate=”yes”. This issue has been fixed.
  • [DEV-3532] In a non-DRM deployment, users were unable to merge a branched map that contained a key in a reltable. This issue has been fixed.
  • [DEV-3214] When cloning a topic that had a cross-reference to itself and the topic had a different ID and filename, the cross-reference in the cloned topic did not have the correct ID. This issue has been fixed.
  • [DEV-2926] It was not possible to drag and drop an element that was not a <topicref> in the DITA Map view. This issue has been fixed.
  • [DEV-2794] When viewing a revision of a localized image that had been localized more than once, the image was displayed but changed the current revision. This issue has been fixed.
  • [DEV-2793] After localizing an image that had already been localized, the older revision of image still appeared when opening the image after the localization. This issue has been fixed.
  • [DEV-2639] Users were unable to perform a spellcheck on a map using a MAC computer. This issue has been fixed.
  • [DEV-2608] When a main map had a subject scheme map, the subject scheme map showed up in the reltable editor and it wasn’t possible to remove it or to add a reltable. This issue has been fixed.

IXIASOFT Dynamic Release Management

  • [DEV-12055] When cloning a DRM version in the Dynamic Release Management view with build 6.0.290, the cloned maps referenced the containers from the original maps resulting in incorrect dependencies. This issue has been fixed.
  • [DEV-11364] In a DRM deployment, the Localize action failed but the Localization Results dialog box did not include an error message. The Error Log view showed a NullPointerException for SequentialLocalizationManagerService.getAllBranchedFromFilename. This issue has been fixed.
  • [DEV-10985] When trying to move a topic from an end state to a working state, an error message appeared saying a map in a different DRM version was locked and preventing the status change. This issue has been fixed.
  • [DEV-10981] IXIASOFT CCMS Desktop sometimes had performance issues when performing DRM operations such as refactoring or adding libraries. This issue has been fixed.
  • [DEV-10559] In a DRM deployment, it was not possible to enable the trigger to automatically change the statuses of child objects at the same time as their parent. This issue has been fixed.
  • [DEV-10302] When cloning a DRM version, if an issue was encountered due to a change in roles, the clone operation failed with an “Operation cancelled” error message. This issue has been fixed and the clone operation completes.
  • [DEV-9899] When doing a DRM Synchronize between two versions and selecting Merge In > Compare for a conflicted topic, whitespace differences were highlighted. This issue has been fixed.
  • [DEV-9878] Changing the primary version of an object in the authoring cycle did not update the version for the corresponding objects in the localization cycle. This issue has been fixed.
  • [DEV-9131] When refactoring a map with an associated Build Manifest, the Build Manifest became invalid because the mapref no longer existed in the DRM container. This issue has been fixed.
  • [DEV-8904] Performing a DRM clone action sometimes caused out of memory errors. This issue has been fixed.
  • [DEV-7457] In a DRM deployment, renaming the title of a topic stub in the Generate Topics from Stubs dialog box did not create topics with the updated title. This issue has been fixed.
  • [DEV-6502] In a DRM deployment, the Search and Replace feature did not search within a submap. This issue has been fixed.
  • [DEV-5085] The Dynamic Release Management panel in the Search view did not display the selected Release and Version when using CCMS Desktop with the Japanese language bundle. This issue has been fixed.

IXIASOFT Output Generator

  • [DEV-9978] Build Manifest outputs failed if the output type contained more than one preprocessor. This issue has been fixed.
  • [DEV-8996] For an Output Generator installed on a Linux server, creating a Collaborative Review failed when a topic included a video link starting with https. For example, <object data= »https://example.net>. This issue has been fixed.

IXIASOFT Scheduler

  • [DEV-10832] When a user performed a change status in CCMS Web, the Scheduler created a notification without a From address. This issue has been fixed.
  • [DEV-10692] If an Approval was approved or rejected via IXIASOFT CCMS Web, the Scheduler email transaction contained an invalid email format in the To address. This caused the Scheduler to fail to process the transaction. This issue has been fixed.

TEXTML

  • This new version of TEXTML is required to maintain compatibility with CCMS Web 6.1.

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-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.

Writers and Advanced Users

IXIASOFT CCMS Desktop - Advanced User Guides (Standard)

The guides for Advanced users for IXIASOFT CCMS version 6.1 are packed with information to help users author, manage, publish, and track documentation on the desktop.

IXIASOFT CCMS Desktop - Advanced User Guides (DRM)

These guides are aimed at desktop users who are also using the Dynamic Release Management (DRM) module to manage their authoring environment.

IXIASOFT CCMS Web - User Guide for Writers (Standard)

This user guide covers what writers need to know when working with IXIASOFT CCMS Web 6.1.

IXIASOFT CCMS WEB - USER GUIDE FOR WRITERS (DRM)

This user guide is for writers working with the Dynamic Release Management (DRM) version of IXIASOFT CCMS Web 6.1.

Contributors and Reviewers

Administrators

IXIASOFT CCMS WEB - USER GUIDE FOR CONTRIBUTORS & REVIEWERS (STANDARD)

This guide is for occasional contributors and content reviewers. The guide teaches how to collaborate with writers and sign off on content that you have verified.

IXIASOFT CCMS WEB - USER GUIDE FOR CONTRIBUTORS & REVIEWERS (DRM)

This guide is aimed at occasional contributors and content reviewers within the Dynamic Release Management (DRM) version of IXIASOFT CCMS Web 6.1. The guide teaches how to collaborate with writers and sign off on content that you have verified.

IXIASOFT CCMS - ADMINISTRATION GUIDES FOR ON-PREMISE INSTALLATIONS

The administration guides are a how-to for customizing aspects of IXIASOFT CCMS. The guides are designed for administrators working with on-premise installations.

IXIASOFT CCMS - ADMINISTRATION GUIDES FOR DEDICATED SaaS INSTALLATIONS

The administration guides act as a how-to for customizing aspects of IXIASOFT CCMS. They are designed for administrators working with dedicated SaaS installations.

X