Release Notes
Abstract
A comprehensive list of known issues for Major, Mode, and Fix Pack releases for the IBM OpenPages with Watson 8.3.
If you have questions about a particular defect, contact Customer Support.
Content
Tab navigation
|
Known Issues in IBM OpenPages with Watson 8.3 |
|
|
Number |
Description |
|---|---|
|
1. |
In an upgrade environment that uses System Views, several errors might occur if new 8.3 System Views reference fields that are not present in your environment. This issue primarily occurs with the new Admin views, which are intended to fill the roles that the Detail view played in the Standard UI. You know whether you have this problem if you get an error message about a Field or Field Group not being found, for a Field or Field Group you have never heard of.
Contexts where these errors might occur:
Workarounds:
|
| 2. |
The MRG OpenScale fields were relabeled to "Watson Studio", which caused the integration with OpenScale to no longer function correctly
Workaround:
Details of a workaround can be found in this technote:
Updating IBM OpenPages Model Risk Governance for integration with Watson Studio (OpenScale) |
| 3. | In an upgrade or migration environment, any existing reports that rely on Facts & Dimensions will not work because Facts & Dimensions have been removed from OpenPages 8.3 |
| 4. |
Some Reporting fragments might fail in OpenPages 8.3
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
| 5. |
The RCSA Process Alignment Helper fails because it contains a problematic Reporting Fragment
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
|
Known Issues in IBM OpenPages with Watson 8.3 FP1 |
|
|
Number |
Description |
|---|---|
| 1. |
In an upgrade environment that uses System Views, several errors might occur if new 8.3 System Views reference fields that are not present in your environment. This issue primarily occurs with the new Admin views, which are intended to fill the roles that the Detail view played in the Standard UI. You know whether you have this problem if you get an error message about a Field or Field Group not being found, for a Field or Field Group you have never heard of.
Contexts where these errors might occur:
Workarounds:
|
| 2. |
The MRG OpenScale fields were relabeled to "Watson Studio", which caused the integration with OpenScale to no longer function correctly
Workaround:
Details of a workaround can be found in this technote:
Updating IBM OpenPages Model Risk Governance for integration with Watson Studio (OpenScale) |
| 3. |
In an upgrade or migration environment, any existing reports that rely on Facts & Dimensions will not work because Facts & Dimensions have been removed from OpenPages 8.3
|
| 4. |
Some Reporting fragments might fail in OpenPages 8.3 or later
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
| 5. |
The RCSA Process Alignment Helper fails because it contains a problematic Reporting Fragment
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
| 6. | When a Questionnaire Assessment (QA) contains a 4 Stage Lifecycle and the out-of-the-box Questionnaire Assessment workflow is used, an error might occur when submitting the Questionnaire Assessment for approval Workaround: Details of a workaround can be found in this technote: Updating OpenPages Questionnaire Assessment workflow to avoid errors when submitting assessment for approval |
|
Known Issues in IBM OpenPages with Watson 8.3 FP2 |
|
|
Number |
Description |
|---|---|
| 1. |
In an upgrade environment that uses System Views, several errors might occur if new 8.3 System Views reference fields that are not present in your environment. This issue primarily occurs with the new Admin views, which are intended to fill the roles that the Detail view played in the Standard UI. You know whether you have this problem if you get an error message about a Field or Field Group not being found, for a Field or Field Group you have never heard of.
Contexts where these errors might occur:
Workarounds:
|
| 2. |
The MRG OpenScale fields were relabeled to "Watson Studio", which caused the integration with OpenScale to no longer function correctly
Workaround:
Details of a workaround can be found in this technote:
Updating IBM OpenPages Model Risk Governance for integration with Watson Studio (OpenScale) |
| 3. |
In an upgrade or migration environment, any existing reports that rely on Facts & Dimensions will not work because Facts & Dimensions have been removed from OpenPages 8.3
|
| 4. |
Some Reporting fragments might fail in OpenPages 8.3 or later
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
| 5. |
The RCSA Process Alignment Helper fails because it contains a problematic Reporting Fragment
Workaround:
Details of a workaround can be found in this technote: Running Reporting Fragment fails with 'OP-12013 The computation encountered an error' exception |
| 6. | When a Questionnaire Assessment (QA) contains a 4 Stage Lifecycle and the out-of-the-box Questionnaire Assessment workflow is used, an error might occur when submitting the Questionnaire Assessment for approval Workaround: Details of a workaround can be found in this technote: Updating OpenPages Questionnaire Assessment workflow to avoid errors when submitting assessment for approval |
| 7. | Cognos Reports and Dashboards supplied as part of IBM OpenPages Risk Management for ESG solution are not 100% translated for locales beyond US English. Workaround: Additional translation for untranslated fields can be applied manually on a report by report basis by using the methods described within the IBM OpenPages with Watson Report Authors guide – see Data Translation |
|
Known Issues in IBM OpenPages with Watson 8.3.0.2 IF1 |
|
|
Number |
Description |
|---|---|
| 1.* |
Customers that use the Loss Event Entry app should avoid upgrading to 8.3.0.2.1 as the app fails to load due to the upgrade of an internal component.
A correction to this issue is available in 8.3.0.2.2
|
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFUEU","label":"IBM OpenPages with Watson"},"ARM Category":[{"code":"a8m50000000ClALAA0","label":"Administration and Configuration"},{"code":"a8m0z000000boKeAAI","label":"Browser"},{"code":"a8m50000000CkpmAAC","label":"Cognos and Reports"},{"code":"a8m50000000ClDPAA0","label":"Database"},{"code":"a8m0z000000bqBjAAI","label":"Task Focused User Interface"}],"Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.3.0"}]
Was this topic helpful?
Document Information
Modified date:
20 December 2022
UID
ibm16562287