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-B12783 · Issue 285395

Performance improvements for Data Designer Visualizer

Resolved in Pega Version 7.3

In order to improve performance of the Visualizer feature of the data designer, the loading behavior has been changed. Previously, the RD being executed for each node in the graph to get the reference properties was defer loaded; this potentially caused issues if the data was still being loaded in the background for the visualizer and an attempt was made to open BodySite. To fix this issue, the defer loading has been removed and the data will load on click of the "visualizer" button.

SR-B12857 · Issue 285462

Repaired REST Connections with proxy

Resolved in Pega Version 7.3

After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.

SR-B13040 · Issue 293380

Improved reliability for GetReference API

Resolved in Pega Version 7.3

A sporadic issue with the OOB getReference API caused a failure in obtaining the absolute reference for a parameterized data page. This was caused by a race condition in the page handler, and synchronization has been improved to ensure the proper name will be set into the data page.

SR-B13040 · Issue 293526

Null DPI check added for async page load

Resolved in Pega Version 7.3

A null pointer exception was being generated when a data page was being loaded from the asynchronous cache and some exception occurred while switching the access group or getting a definition. To avoid this, a check has been added for a null DPI.

SR-B13647 · Issue 291863

Security Policy updates to handle big strings

Resolved in Pega Version 7.3

The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.

SR-B13647 · Issue 291683

Security Policy updates to handle big strings

Resolved in Pega Version 7.3

The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.

SR-B13929 · Issue 289408

Instances Count updated to better handle external DB checks

Resolved in Pega Version 7.3

Opening the Data table list from the Designer studio DesignerStudio > Data Mode > Data Tables > Data Tables generated an exception related to obtaining a count of instances from an external DB. This has been resolved by adding a check which modifies the activity based on whether the call is to an internal or external DB.

SR-B13931 · Issue 286184

BIX extract Inskey error fixed for nested page lists

Resolved in Pega Version 7.3

BIX Extract was failing with the message "Inskey of the corrupt Instance" if it encountered nested page lists. To resolve this, the PropertyReferenceImpl.filter() method will add missing elements in cases with nested pagelists.

SR-B14109 · Issue 292263

Fixed autocomplete for strings containing plus sign

Resolved in Pega Version 7.3

Autocomplete was not working properly when a search string contained the '+' sign. When the search input was passed to the DB, the + sign was changed to + in the query and therefore did not return any results. This was due to the parameter being encoded twice as it was passed from autocomplete to the grid infrastructure, and has been resolved by preventing the unneeded encoding.

SR-B14129 · Issue 284313

JSON mapping updated to support page list class given as string value

Resolved in Pega Version 7.3

Connect Rest was not parsing the value of the Boolean property "isEligible" returned as part of a JSON response or mapping it on to the clipboard. This was traced to the unexpected scenario of the string "$ANY" being used as class for a page list and inside a pagelist Boolean property. To support this use, the JSONMappingUtils.java file mapObjectToPage method has been modified to handle the Boolean property before the generic else if condition.

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