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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B51450 · Issue 313658

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 313738

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B69447 · Issue 317927

Attachment links with commas open in Google Chrome

Resolved in Pega Version 7.3.1

After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.

SR-B69447 · Issue 317951

Attachment links with commas open in Google Chrome

Resolved in Pega Version 7.3.1

After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.

SR-B39427 · Issue 309252

Export to Excel fixed for DT >50 records

Resolved in Pega Version 7.3.1

After upgrade, clicking the Export button on a decision table with more than 50 records was not sending the data to Excel as expected. This was traced to a Null Pointer Exception generated by encountering an unneeded step page, and the erroneous step has been removed.

SR-B53476 · Issue 313103

JBoss installation config documentation corrected

Resolved in Pega Version 7.3.1

Deploying JBoss in single-user configuration and starting Pega was failing with the error "Services with missing/unavailable dependencies". This was caused by an incorrect configuration, and was traced to an error in the documentation for JBoss that reverted the installation instructions to an earlier version. The JBoss documentation has been corrected to reflect that configuring the adminPegaRULES datasource is not optional. If dual user config is not needed, the same configuration as PegaRULES datasource should be used.

SR-B54273 · Issue 310624

Resolved requestor hang and JVM crash

Resolved in Pega Version 7.3.1

Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.

SR-B54273 · Issue 310713

Resolved requestor hang and JVM crash

Resolved in Pega Version 7.3.1

Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.

SR-B49166 · Issue 309799

Removed unneeded timestamp on DADN rule connection test

Resolved in Pega Version 7.3.1

Test connections were failing for a Data-Admin-DB-Name rule when the connection type was "Use Configuration in Preferences". This failure was caused by "tmp" being appended to the DB name for the connection test, causing the DB name to be different in the prconfig file. Because a timestamp is not required, this has been fixed by not appending it to the DADN name.

SR-B66439 · Issue 315454

prpcServiceUtils component updated to contain Linux Ant files

Resolved in Pega Version 7.3.1

The Ant file was missing in the prpcServiceUtils published in the below article : https://pdn.pega.com/exchange/components/remote-configuration-command-line-tool-prpcserviceutils The issue in the gradle script which caused the Ant file to be missed while creating zip file has been fixed.

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