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-B35117 · Issue 292760

Split-for shape "open flow" works as expected

Resolved in Pega Version 7.3

When working with a flow that contains a Split-for each shape which loops pyWorkParty and executes a flow on Data-Party class, an error was generated if there was a right-click on the sub-flow shape and "Open flow" was chosen. The sub-flow opened properly if there was a right-click on the sub-flow shape, "View Properties" was chosen, then a click on the "Open" icon right of the flow name. This was traced to the Top Class being passed for opening the flow rule in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" class. To fix this, the class has been changed from Top to ".pyPageClass" in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" to open the flow rule

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-B36134 · Issue 294119

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36134 · Issue 294006

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36134 · Issue 294147

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

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

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