Known issues

The following issues and limitations are known for IBM® Engineering Lifecycle Optimization - Publishing 7.2 release.

Workarounds

The following issues in this release have workarounds.

Unable to install Publishing Document Builder 7.1 through the launchpad

First occurrence: 7.1

ID: Internal

Problem: When installing Engineering Publishing 7.1 through Publishing Document Builder 7.1 launchpad, it fails.

Workaround: While installing Publishing Document Builder using the steps in Installing Publishing Document Builder on a server for your organization, instead of the step-3 and step-4, perform the following steps and then continue with the remaining steps as is:
  1. Go to Installation Manager.
  2. Go to File > Preferences > Repositories and click Add repository.
  3. Copy the extracted pub_version_win_linux/PUB directory and paste into the above mentioned in step 2.
  4. Follow the prompts to complete the process and then click Install.
When Document Builder is configured with Jazz® Team Server authentication, the behavior of Engineering Workflow Management, Engineering Rhapsody® Model Manager and Engineering Test Management is different from IBM DOORS® Next and GC

First occurrence: 7.0.3

ID: Internal

Problem: If the Publishing Document Builder is configured with Jazz Team Server authentication, the data source URLs use credentials or cookies from the session. Hence, if the username and password are not provided in the connection, the document is generated successfully. The behavior of Engineering Workflow Management, Engineering Rhapsody Model Manager, and Engineering Test Management is different from Engineering Requirements Management DOORS Next and GC::
  • For Engineering Requirements Management DOORS Next and GC, the delegated Resource selection dialog is directly opened. No authentication is required.
  • For Engineering Workflow Management, Engineering Rhapsody Model Manager, and Engineering Test Management, instead of a delegated picker dialog, a link to log in is displayed. When you click the login link, a separate browser page opens for JTS authentication.
Workaround:
  1. Open Publishing Document Builder. Ensure that the Publishing Document Builder is configured with Jazz Team Server authentication.
  2. Add the connection.
  3. Select the URL of the data source.
  4. Select common providers and click Go.
  5. Enter the username and password before you select the resource in the picker.

Limitations

Note: For Engineering Publishing version 7.1 SR1 interim fix 4 and later, a new transform is integrated into Engineering Publishing for document generation. You can switch between the new and older transform or remove the older transform entirely, without impacting the functions provided by the new transform.
If Apache POI flag is enabled in Engineering Publishing, certain functions, output formats and properties are not supported.
You can enable the -Dcom.ibm.elm.enable_apache_poi=true flag in your configuration to test new components. However, this option disables the following functions and output formats for Microsoft Excel and Microsoft Word.
  • For Microsoft Excel:
    • Alternative text for images
    • Double-line border for images
    • Image placement in comments
    • Table placement in comments
    • Region
    • .xls file format
  • For Microsoft Word:
    • Font family and color of page number in footer
    • Math equation
    • Paragraph foreground density
    • Paragraph outline
    • Image watermark
    • Table indentation
    • Text border
    • Region with Text element
    • .doc file formats
    Note: Table of content is supported in Microsoft Word, however you need to manually confirm the TOC updates. Upon adding a table of contents in a Microsoft Word document in Engineering Publishing configured with Apache POI, a dialog box appears to confirm updating fields that reference other documents. Click Yes to proceed. If another dialog box appears to confirm the table of contents update, click Yes (in Windows) or OK (in Mac OS).
  • The Import Word to Template function is disabled and not supported in Engineering Publishing when Apache POI is enabled.
  • The PDF output format is not supported.