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-B3263 · Issue 275060

Performance improvements for opening pop up grid dialog box

Resolved in Pega Version 7.3

Performance improvements have been made in opening the pop up dialog box in pzPerformGridAction by executing the copying logic only if the page is read-only.

SR-B3280 · Issue 279492

Resolved skimming error

Resolved in Pega Version 7.3

Errors were getting thrown on the screen while performing minor ruleset version skimming of one version into a new ruleset version which was higher than the ruleset version mentioned in the application rule. This was due to the target version not having the correct context because the application didn't yet exist or because the operator was not logged into the target context. In order to resolve this, the messages in the page will be cleared before skimming to avoid validation. It is then recommended to log into the new application and use the Application Validation tool to validate the newly created rulesets application.

SR-B32839 · Issue 292388

Performance improvements for headless decisioning

Resolved in Pega Version 7.3

Performance issues were seen in Service Pega 7.2 related to scaling vertically when used for in a headless decisioning scenario. The code has been refactored to remove redundant calls to requestors in ServiceAPI, HttpService, SOAPUtils and SOAPService as well as additional classes and other classes to correct this.

SR-B33262 · Issue 289895

IACAuthentication security improved

Resolved in Pega Version 7.3

The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.

SR-B33262 · Issue 290338

IACAuthentication security improved

Resolved in Pega Version 7.3

The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.

SR-B33686 · Issue 295039

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-B33919 · Issue 291326

NexFlow requestor performance improvements

Resolved in Pega Version 7.3

The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.

SR-B34134 · Issue 292328

Bulk upload logic improved for SAI contact creation

Resolved in Pega Version 7.3

While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.

SR-B34134 · Issue 292929

Bulk upload logic improved for SAI contact creation

Resolved in Pega Version 7.3

While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.

SR-B34134 · Issue 292787

Bulk upload logic improved for SAI contact creation

Resolved in Pega Version 7.3

While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.

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