Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-149517 · Issue 609476

Secure access for Activities

Resolved in Pega Version 8.5.3

Authentication requirements have been added to Standard activities.

INC-150038 · Issue 614829

Data Type local data storage snapshot history updated

Resolved in Pega Version 8.5.3

When a History Class Data object was created, two snapshots were made - one with value and another with no value. This was traced to a 'when' condition that evaluated whether to add history when deleting a record from records editor, and this issue has been addressed by removing the condition as the history-add step takes care of checking if there is a dedicated table or not.

INC-150151 · Issue 613414

Stream REST endpoint CORS support added

Resolved in Pega Version 8.5.3

CORS support has been added to the Stream REST endpoint. If a request contains an "Origin" header, the "Access-Control-Allow-Origin" header with the origin value (*.companyname.com) will be added to the response for Stream tier (/stream/view & /stream/click) calls.

INC-150610 · Issue 627428

Argument number exception handled for SERVICES-PAL log configuration

Resolved in Pega Version 8.5.3

An issue with being unable to configure the SERVICES-PAL log file has been resolved by adding handling for an unlogged "wrong number of arguments" exception.

INC-150633 · Issue 614514

Optimizing helper class enhanced to handle external databases

Resolved in Pega Version 8.5.3

Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".

INC-150704 · Issue 613441

Azure Repository connection updated

Resolved in Pega Version 8.5.3

Attempting to connect to Azure blob storage using SDK v8.6.4. SDK was not working. Investigation showed that the x-ms-version:2013-08-15 was set by default; the issue has been resolved by setting the x-ms-version to 2018-03-28, and Pega will be working with Microsoft support to understand what has changed at the Azure Storage end that introduced the issue.

INC-150809 · Issue 611856

Loading timing updated for openAPI content

Resolved in Pega Version 8.5.3

Open API content loading was taking too much time and interfering with working on other REST rule configurations. To resolve this, the loading of openAPI contents has been removed from the opening or saving of REST rule and shifted to lazy loading. Clicking on the openAPI tab will load the contents, and any modification in REST rule or service package rule will update the contents of openAPI when "Action->Refresh" is clicked.

INC-151043 · Issue 614872

Optimizing helper class enhanced to handle external databases

Resolved in Pega Version 8.5.3

Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".

INC-151228 · Issue 620602

Kafka updated

Resolved in Pega Version 8.5.3

Stream node errors were seen in the log file indicating "Invalid configuration. Undefined stream provider end point." This has been resolved by updating Kafka to v1.1.0.5, which was released to address this issue in WIndows environments.

INC-151426 · Issue 613089

JobScheduler initialization timing adjusted

Resolved in Pega Version 8.5.3

DDS nodes were ending up in a deadlock condition on restart, preventing them from joining the cluster. This has been resolved by ensuring the JobScheduler initialization task waits for Search to start up.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us