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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-149375 · Issue 607830

Adjusted email listener behavior for authentication failures

Resolved in Pega Version 8.6

After upgrade, email listeners were not staying up during connection outages. This was traced to the handling of authentication failures when trying to reconnect, and has been resolved by changing the disconnected listener state to sleeping and raising an alert for authentication failures.

INC-149382 · Issue 612426

Loading timing updated for openAPI content

Resolved in Pega Version 8.6

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-149466 · Issue 607611

Fixed alias assigned to custom categories to handle Oracle limitations

Resolved in Pega Version 8.6

When trying to access CHAT via interaction portal, Oracle SQL was fired with incorrect syntax. This was traced to an Oracle limitation of 30 characters on the length of the table name, table alias name, or column name in database versions prior to 12.2. This is caused an SQL exception if the Pega class name was more than 30 characters. To prevent this, a fixed alias has been assigned to the custom category table.

INC-149517 · Issue 609474

Secure access for Activities

Resolved in Pega Version 8.6

Authentication requirements have been added to Standard activities.

INC-149849 · Issue 612261

DSN message mapping corrected

Resolved in Pega Version 8.6

Original-text-html was not correctly mapped to .pyInboundEmail.pyOriginalTextHtml . This has been resolved by removing an incorrect null check encountered while setting original-text-plain mapping for the DSN message while handling a DSN ReturnedMessagePart of type message/rfc822 and updating the handling for text parts which are not null.

INC-150038 · Issue 614826

Data Type local data storage snapshot history updated

Resolved in Pega Version 8.6

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 613413

Stream REST endpoint CORS support added

Resolved in Pega Version 8.6

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-150271 · Issue 608943

Fallback added for calculating date after upgrade

Resolved in Pega Version 8.6

After upgrade, the date value returned from Stored procedure failed to be mapped to "date" type property. Stored Procedure was used to get data from an external Oracle database and then handed to a Data Transform to map the values. When the Data was fetched from the store procedure, the date properties were mapping correctly, but when these values were mapped from the clipboard into the usecase using a Data Transform, the data for date properties was becoming corrupted. This was traced to logic differences between the versions: 8.2 generated resolveToDate while in 8.5 generates resolveToBigDecimal. In this case, resolve to big decimal was being called with aType='D' and aValue=20200918, and the 20200918 number was being interpreted as days since 1 Jan 1970 instead of as a date. This has been resolved by adding a fallback for the date calculation.

INC-150610 · Issue 627427

Argument number exception handled for SERVICES-PAL log configuration

Resolved in Pega Version 8.6

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 614513

Optimizing helper class enhanced to handle external databases

Resolved in Pega Version 8.6

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".

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