Table of contents

Limitations and known issues for OpenPages

Encryption of external databases
The database setup script for external databases, setup-extdb.env, does not encrypt the database when you use the -e option.

To work around this issue, encrypt the database after you run the setup-extdb.env script.

Applies to: 8.203.0

OpenPages® Loss Event Entry email notifications
Email notification are not sent by OpenPages Loss Event Entry and no error messages are displayed.

Applies to: 8.203.0

Functional differences
The following OpenPages with Watson™ features are not supported in OpenPages for Cloud Pak for Data
  • The ability to open and edit Microsoft Office files directly from OpenPages is not supported.
  • The Standard UI is not supported.
  • Full text search (global search) is not supported.
  • Field level encryption is not supported.
  • Some aspects of the administrative user interface are not available, such as the Environment Comparison and Background Processes user interfaces.
  • The ability to shorten the OpenPages application URL is not supported.

Applies to: 8.203.0

Long strings
Long string fields (string fields that contain more than 4000 bytes) have the following limitations:
  • Filtering on long string fields in views, dashboards, workflows, and calculations is not supported.
  • Creating public filters or personal filters that are based on long string fields is not supported.
  • Querying long string fields via the REST API is not supported.

Applies to: 8.203.0

Reporting

Integration with Cognos® Analytics is not supported. Cognos reports, report fragments, and computed fields are also not supported.

Applies to: 8.203.0

BC Plan Details link

In the Business Continuity (BC) Plan task view, the Print BC Plan Details link does not work and gives a Bad request error. The error occurs because the BC Plan Details report is a Cognos report, which is currently not supported in OpenPages on Cloud Pak for Data.

Applies to: 8.203.0

Timestamps use UTC

Timestamps use UTC. For example, when you run jobs in the Scheduler, the execution timestamp is in UTC, rather than in local time.

Applies to: 8.203.0