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-B33387 · Issue 298483

Incorporated synchronized timestamp function for addWarning

Resolved in Pega Version 7.3

When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.

SR-B33678 · Issue 292086

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B33678 · Issue 292524

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B33962 · Issue 291929

Overview rendering enhanced for multiple subcases

Resolved in Pega Version 7.3

When a case was created with two subcases, assignment of one of the subcases was not getting rendered in the overview section. This was caused by the pzLoadNestedCasesForClass checking contains on pyID and has been resolved by changing the function to check on pzInsKey. Also in step 5.4, the appending of pyID has been changed to pzInsKey.

SR-B34248 · Issue 293070

Performance improvements for Work-Cover-.pyLoadMyCases

Resolved in Pega Version 7.3

Performance issues in Work-Cover-.pyLoadMyCases were traced to code in pyLoadMyCasesNested that made an unnecessary page copy and triggered several data page loads. To improve response time, the page copy activity has been removed and the system will instead use a Boolean value to determine whether to read data from the DB or from the clipboard page.

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-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-B37923 · Issue 295190

null-pointer exception fixed for ForceCaseClose

Resolved in Pega Version 7.3

An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.

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