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-C23138 · Issue 367878

PRPushServlet response corrected to 400 when disabled

Resolved in Pega Version 8.1

PRPushServlet is used to establish a WebSocket connection with the Pega server. When server-push is disabled, the Push engine won't get initialized and will return an empty response by logging a warning message ("Request arrived for requestor:[%s]. But PushEngine has not started." ). Unexpectedly, this process was returning HTTP status 200 instead of 400. This has been corrected.

INC-137882 · Issue 599140

Hazelcast will be used to determine node presence

Resolved in Pega Version 8.4.4

When calling logoff from the end user portal, sporadic PresenceStandardLifeCycleListener exceptions were seen during high load periods. This was traced to changes made in the Service Discovery behavior: when there is an issue with the node and heartbeats are missed, the node goes to Safe Mode. This caused the topology to change and trigger clearing off presence sessions, but the node still received service requests and this issue was seen. To resolve this, an updated has been made so the system will rely on the Hazelcast listener instead of service discovery to determine whether a node has left.

SR-C24201 · Issue 373198

Updated logging to stabilize ServiceAPI use

Resolved in Pega Version 8.1

When using “ServiceAPI” for other integrations within the application, setting ServiceAPI to “Fatal” caused the loss of visibility on issues with other components of the application which use ServiceAPI. This was traced to excessive logging for authentication failures from ServiceAPI, and has been resolved by changing error logging to Warn or Debug at various instances.

SR-D39956 · Issue 511638

Corrected method IF use with shortcut function

Resolved in Pega Version 8.4

After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved.

INC-133951 · Issue 584147

Try catch added for templated refresh when

Resolved in Pega Version 8.4.4

After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.

INC-153108 · Issue 614358

Added check to maintain disabled textarea 'when'

Resolved in Pega Version 8.4.4

The disabled text field became editable when the "Run required condition on client" checkbox was enabled. This has been resolved by adding a check for pyDisabled property to get the correct status for textarea control.

SR-D24651 · Issue 495766

Proper assignment instructions sent when transferring

Resolved in Pega Version 8.4

Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).

INC-175630 · Issue 653863

Application selections only announced when visible

Resolved in Pega Version 8.7

The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.

SR-C16961 · Issue 357154

BasicLocaleImpl logic updated to use ConcurrentHashMap

Resolved in Pega Version 8.1

To improve performance, the logic for com.pega.pegarules.exec.internal.util.BasicLocaleImpl has been changed to use ConcurrentHashMap instead of HashTable.

SR-C17056 · Issue 356994

Memory use performance improvements for surveys

Resolved in Pega Version 8.1

The inline scripts for question shape have been eliminated and the dynamic generated arguments process has been moved to the global survey namespace. This enables the download of one common script for all question screens to conserve memory usage.

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