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-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-B33262 · Issue 289812

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-B35799 · Issue 293251

Alerts modified to correct logged interaction totals

Resolved in Pega Version 7.3

The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.

SR-B35799 · Issue 277230

Alerts modified to correct logged interaction totals

Resolved in Pega Version 7.3

The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.

SR-B35931 · Issue 293471

prpcUtils readme updated for importing to Oracle

Resolved in Pega Version 7.3

The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.

SR-B36418 · Issue 293162

More descriptive error message for RAP import

Resolved in Pega Version 7.3

In order to clarify that Schema migration does not support importing a table with the same name as an existing view or a view with the same name as an existing table, the code has been updated to throw a more descriptive exception.

SR-B36743 · Issue 293937

BLOB data save performance improved

Resolved in Pega Version 7.3

In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.

SR-B37039 · Issue 293524

Security upgrade for Struts2

Resolved in Pega Version 7.3

To improve security, Apache Struts2 has been upgraded to version 2.3.32 .

SR-B37139 · Issue 294520

Installation guide updated to reflect that ADM is supported on MS SQL.

Resolved in Pega Version 7.3

The installation guide has been updated to reflect that ADM is now supported on MS SQL server.

SR-B37306 · Issue 293862

Security upgrade for Struts2

Resolved in Pega Version 7.3

To improve security, Apache Struts2 has been upgraded to version 2.3.32 .

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