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-B12850 · Issue 283836

SMA Garbage Collector landing page updated to work with updated browsers

Resolved in Pega Version 7.3

SMA's Garbage Collector landing page was not working correctly on the latest versions of Chrome and other browsers due to the document.all JavaScript function being deprecated. The code has been updated to correct this.

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-B13020 · Issue 283559

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

SR-B13020 · Issue 283078

Upgrade App Schema generates unique index name IDs

Resolved in Pega Version 7.3

Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.

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-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-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.

SR-B14153 · Issue 284939

Only relevant records shown for work objects in select property picker

Resolved in Pega Version 7.3

The select property picker for all work objects with record identifiers was showing all records whether or not they were relevant. This was an issue where show relevant was being set to false when record identifier and show relevant was true in pyGetCategoryItems for all classes, and has been corrected by skipping this step for work object classes.

SR-B14288 · Issue 289182

Command line BIX extract works as expected for -l option

Resolved in Pega Version 7.3

When a BIX extract was generated using rule XML of the extract rule (-I) from the command line, the manifest generated had "pxExtractIdentifier" in an unexpected format. The command line option has now been modified to generate the extract with the correct pzInsKey of the rule.

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