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-D73224 · Issue 542629

Case manager portal links working with SVG file

Resolved in Pega Version 8.5

After modifying the pyPortalHeader to show a custom logo in the Case manager portal by saving the pyapp-logo.svg file into a ruleset and uploading the logo, none of the Case manager portal links or menus were working and a console error appeared. Investigation showed the SVG file stream was decoded and then encoded using the Base64Util.encode and decode, which was adding new line characters. To resolve this, step 4 in Rule-File-Binary.UploadFile Activity has been modified to remove the Base64 encode and decode.

SR-D71944 · Issue 543731

Resolved data page loop in templatized UI

Resolved in Pega Version 8.5

A Layout Group was configured with six dropdowns sourced to Parameterized datapages with "disable automatic refresh" unchecked; every next dropdown depended upon the previous property, and the previous property was sourced as parameter, and so on until last dropdown. When the value in the dropdowns changed, the section kept refreshing and the portal became unresponsive. This was traced to the combination of a Datapage as the source to the dropdown with "disable automatic refresh" unchecked and expression evaluation as well. Templatized UI has 'visible when' expressions for all the properties inside the top level page. Changing the first one fired refresh on the next one, and the next one's refresh fired the other drop down refresh until it became recursive. This did not occur in non-templatized UI as it does not have expression IDs and there are no recursive calls. This issue has been corrected by modifying how the temporary mapping is populated by the reloadCells API in Expression Evaluator to prevent unwanted cell refreshes.

SR-D42437 · Issue 513648

Pulse @mention will avoid triggering search request if no suggestion list is available

Resolved in Pega Version 8.2.5

Search threads were causing requestor Lock Exceptions due to poorly optimized queries sent to ElasticSearch when a Pulse mention was attempting to look up a person (e.g. "@"+typing) and the search of case objects to match to that search were performing poorly. To resolve this, an update has been made to avoid triggering requests if the suggestions list is not available for the search query.

SR-D45828 · Issue 518020

Added variable null check to resolve refresh condition on dynamic layout not working

Resolved in Pega Version 8.2.5

Given a setup where a parent section had several section includes, one of which had a property that was set to refresh and disable another section when the property changed, on change the refresh action was not working and hence the disabling did not work. Refreshing the browser corrected the behavior. Javascript errors were noted on the console. This has been resolved by adding a null check on the variable to avoid exceptions.

INC-182137 · Issue 662488

Multistage Prediction Logic improved

Resolved in Pega Version 8.7

When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.

INC-188124 · Issue 672587

Multistage Prediction Logic improved

Resolved in Pega Version 8.7

When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.

INC-163914 · Issue 668846

Improved Agile Studio passivation recovery

Resolved in Pega Version 8.7

When an Agile Studio session was passivated, the error "SECU0008 : CSRF Detected and Blocked" was seen. Reactivating the session resulted in a blank page. This was traced to the clearing of requestor level registrations added for that particular thread, and has been resolved by adding a new flag to identify if a thread is passivated along with the necessary structure for the conditionalized clearing of requestor level registrations based on this flag.

INC-177512 · Issue 657015

Hazelcast packages expanded for Java9+ with kubernetes

Resolved in Pega Version 8.7

Hazelcast warnings were seen in cluster logs when Hazelcast was run in embedded mode or c/s mode on a java modular environment i.e. java 9+ which noted that performance and functional impact issues may result if certain internal modules of java are not given reflection access. This update provides the necessary access to some additional java internal modules/packages per the Hazelcast recommendation.

INC-164641 · Issue 649391

Table header aria label updated

Resolved in Pega Version 8.7

In a PegaWAI enabled application with the NVDA screen reader, a table header column which had filtering enabled was read as "Column Name Enter to Filter" on the first focus, but the filter operation did not work on hitting enter. When focus was moved to the second tab, the filter worked as expected. This was traced to an incorrect aria-label in the table header description, and has been resolved.

INC-184109 · Issue 671195

Handling updated for customDateTime formatting

Resolved in Pega Version 8.7

When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.

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