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-174321 · Issue 664240

SSLContext created using protocol from REST connector rule form

Resolved in Pega Version 8.4.6

After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.

INC-184756 · Issue 667323

Static assembler correctly creates temp directory

Resolved in Pega Version 8.4.6

Static Assembly CLI was failing while creating a temp directory. This was traced to an issue with staticAssembler.xml, and has been resolved. In addition, security improvements have been added to the XML transformer.

INC-190722 · Issue 676403

Ruleset Restoration Utility repaired

Resolved in Pega Version 8.4.6

Attempting to use the standard Ruleset Restoration utility after update was resulting in a "Status:fail Operator:Unauthenticated or not available Node:No ID available" error message. This was a missed use case for the refactoring done around importing rules, and was caused by the utility calling the deprecated Importable.isValidImport() method. This has been resolved by updating the import activity to restore its functionality.

INC-184798 · Issue 703269

PRconfig added for JVM user/password

Resolved in Pega Version 8.7.1

The setting Dcom.sun.management.jmxremote.local.only=true has been added for use when JMX authentication is enabled by providing jmxuser/password through prconfig.

INC-194348 · Issue 703374

Resolved multiple copies of Pega0050 alerts

Resolved in Pega Version 8.7.1

The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.

INC-195580 · Issue 684492

Delay Factor updated to allow values < 1.0

Resolved in Pega Version 8.7.1

After modifying the "Delay factor" parameter on a queue processor rule and and clicking the "Save" button, refreshing the page caused the value of the "Delay factor" parameter to change. This has been resolved by updating the delay calculation strategy to support factors < 1.0.

INC-196478 · Issue 683130

CORS policy updated for GET streams

Resolved in Pega Version 8.7.1

CORS (Access-Control-Allow-Origin) support has been added to handle Stream calls during GET requests.

INC-153631 · Issue 613851

Table selector updated to handle complex autocomplete dropdowns

Resolved in Pega Version 8.7.1

Whenever an autocomplete and a table were in different sections, only the first 40 results were visible in the dropdown and the other spaces were shown as blank. The issue did not occur if the table and autocomplete were in same section. This was traced to a specific configuration where Section A had an autocomplete inside the dropdown list and autocomplete was enabled to show the results in a table (presentation tab) and Section B, which contained a grid, was included in Section A in the same autocomplete dropdown list. This has been resolved by updating the table selector in ui_grid so it uses the correct dom elements.

INC-172944 · Issue 662829

Skin rule circumstancing article added

Resolved in Pega Version 8.7.1

An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.

INC-176462 · Issue 657411

Dashoard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.7.1

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

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