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.

SR-B87575 · Issue 334798

Fixed PRAppLoader issue with IBM JVM

Resolved in Pega Version 7.4

When deploying a new application containing a web service client configured with WebSphere security, unexpected ClassCastExceptions were generated in the IBM code during the web services call. This happened when the WebSphere app server was combined with Pega and another application deployed in it: Pega was overriding some classes loaded by the the app server and causing a conflict. To resolve this, a system property (com.pega.pegarules.bootstrap.ENABLE_IBM_SOAP_OVERRIDES) has been introduced to accommodate disabling the use of the hard coded list of SOAP implementation and instead delegate to the JVM / META-INF/services directory for the SOAP implementation. The EAR has also been modified to include the SOAP javax.xml.soap.* files.

SR-B87944 · Issue 339290

Apache Struts compatibility update

Resolved in Pega Version 7.4

Compatibility with Apache Struts 7.3.1 prsysmgmt.war file has been added.

SR-B88554 · Issue 340561

Performance improvements for opening a Data instance

Resolved in Pega Version 7.4

Logic improvements have been made to improve the performance of opening a Data instance from rule explorer.

SR-B88704 · Issue 335781

BIX Execution History lines are clickable

Resolved in Pega Version 7.4

The history lines in the Execution History tab for BIX extractions are now clickable as per the help documentation.

SR-B88847 · Issue 349609

SQL query modified to ensure pyClusterAddress integrity

Resolved in Pega Version 7.4

If the Full Text indexer was run for re-indexing and the already-running PRPC elastic search master index node was restarted, the node started up with the full text indexer becoming the master node. This was traced to a DB query that is fired to get the list of index nodes that need to be fed to the ES cluster for unicast discovery; only SQLServer is insensitive to the case values sent, and Oracle/DB2/PostgreSQL had issues retrieving the value "NONE" when it was uppercase. To resolve this, the SQL Query has been modified to have the right value for pyClusterAddress during elastic search indexing.

SR-B89104 · Issue 336236

Branch review page shows full rule name on hover

Resolved in Pega Version 7.4

As part of a previous fix, the pyDescription field which held the truncated version of rule name was removed and the original full rule name was used instead. This same substitution has now also been added to the branch review page, allowing the system to display the complete rule name on hover of the visible rule name.

SR-B89567 · Issue 340261

Logic reworked for case advancement

Resolved in Pega Version 7.4

The logic in function pega.process.engine.canAdvance was incorrectly calling pega.process.caseType.getNextTask before running the execPostProcessHook or the subFlowPostProcessHook functions, leading to missing properties needed by the decision shapes in the flow. This has been fixed.

SR-B89621 · Issue 336849

Abstract Push Engine logic fixed for passing portalname

Resolved in Pega Version 7.4

The error "AbstractPushEngine ERROR - Portal Name could not be retrieved from request" was being logged every 15 seconds. The JS layer was passing the request parameter, but the logic in AbstractPushEngine.validateRequest() was mistakenly reading it using the getHeader() method rather than getParameter() method. This has been corrected.

SR-B89621 · Issue 328119

Abstract Push Engine logic fixed for passing portal name

Resolved in Pega Version 7.4

The error "AbstractPushEngine ERROR - Portal Name could not be retrieved from request" was being logged every 15 seconds. The JS layer was passing the request parameter, but the logic in AbstractPushEngine.validateRequest() was mistakenly reading it using the getHeader() method rather than getParameter() method. This has been corrected.

SR-B89625 · Issue 342129

Clipboard clears on form submit, plus performance improvements

Resolved in Pega Version 7.4

Progressing through an application questionnaire was causing clipboard size to increase without being cleaned. This was due to a page clearing request not being triggered, and the harnessonbeforeunload method has updated to trigger pyDeleteDocumentPg on submission of the form in topnavigation portal. In addition, performance improvements have been made to this process.

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