Known issues

Workarounds

The following issues in this release have workarounds.

Unable to install Publishing Document Builder 7.1 through the launchpad

First occurrence: 7.1

Internal ID: 81879

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.

Unable to update an older version of the Engineering Publishing client to Engineering Publishing 7.0.3 or 7.1 using the Installation Manager

First occurrence: 7.0.3

Internal ID: 80464

Problem: You are not able to use the update functions in the Installation Manager to update an older version of the Engineering Publishing client to Engineering Publishing 7.0.3 or 7.1 due to the Eclipse version upgrade.

Workaround: You can uninstall the older version of the Engineering Publishing client from Installation Manager and install Engineering Publishing 7.0.3 or 7.1 as a fresh installation.

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

Internal ID: 80434

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.

Engineering Publishing 7.0.3 and 7.1 are unable to access the data sources of Engineering Lifecycle Management 7.0.2

First occurrence: 7.0.3

Internal ID: 76143

Problem: When you try to generate a document with Engineering Publishing 7.0.3 or 7.1 by using data sources from the Engineering Lifecycle Management 7.0.2 applications, the document generation fails due to the TLS version mismatch.

Workaround:

1. Go to the Engineering Publishing installation path (%rpe_home%).
2. Open the rpe-studio.ini file in the studio folder and add the following flag to the file: com.ibm.engineering.pub.strictTLSversion="TLSv1.2”
3. Open the rpe-launcher.ini file in the launcher folder and add the following flag to the file: com.ibm.engineering.pub.strictTLSversion="TLSv1.2”
4. Save the file.

Limitations