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-A14917 · Issue 230745

Improved repeat grid filtering performance for Microsoft Internet Explorer

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, a repeat grid with source as report definition was taking 30 seconds to show filter options, and canceling the column filter results could take over 90 seconds. The functions have been tuned with updated jQuery code to resolve the issue.

SR-A18236 · Issue 236897

Workbasket re-visit issue resolved

Resolved in Pega Version 7.2.1

After selecting a workbasket in the MyGroup drop down and launching the pop-up containing the workbasket details, an error in the closing reset function led to an issue where a second workbasket would need to be launched before it was possible to return to the first one again. This has been corrected.

SR-A18928 · Issue 241932

AddDays calendar logic updated

Resolved in Pega Version 7.2.1

The AddDays function in a Business Calendar was not working correctly because it did not have a default timezone. The Days RUF with 4 parameters ADDDAYS--(STRING,INT,BOOLEAN,STRING) has been set to use the GMT timezone in cases where the use business calendar parameter is sent as false.

SR-A19601 · Issue 238255

Workbasket re-visit issue resolved

Resolved in Pega Version 7.2.1

After selecting a workbasket in the MyGroup drop down and launching the pop-up containing the workbasket details, an error in the closing reset function led to an issue where a second workbasket would need to be launched before it was possible to return to the first one again. This has been corrected.

SR-A92126 · Issue 261816

Bulk Action transfers all selected records

Resolved in Pega Version 7.2.2

Not all of the selected cases were being transferred when using the Bulk Actions functionality to transfer. This was due to the pySelected values to not being updated in the clipboard. To resolve this, a Refresh other section has been added to Select Action in pzBulkProcessingActionSection to update the value when clicked.

SR-A102433 · Issue 271744

Optional warn forced for PersistSystemInfo

Resolved in Pega Version 7.2.2

When using com.pega.pegarules.monitor.internal.state.DatabaseInfoHandler.persistAllCurrentComponents(PRThread), errors are logged and the flow continues. As this may cause customer logs to fill up with errors, the function has been changed to warn forced and stacktrace will only be displayed if debug is enabled.

SR-A100503 · Issue 268474

Harness name field in flow accepts expression

Resolved in Pega Version 7.2.2

After upgrade, a harness issue was encountered where the generated flow was treating the pxFormName as String literal instead of Expression. This caused an error when trying to save a flow. To correct this, FlowFUA PopulateFlowActions function code used for Expression parsing in the harness has been updated.

SR-A11347 · Issue 250646

Updated authorization logic for Stream Assembly

Resolved in Pega Version 7.2.2

Triggering stream assembly was resulting in an "unauthorized"or "rule not found" exception relating to the rule existence validation code executed in the pzValidationSections RUF. This has been resolved with the addition of logic to the Stream Assembly function that runs a validation check for database authorization before opening the activity.

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-B3943 · Issue 279666

NewCorrSummary rule resolution modified for CommunicationType

Resolved in Pega Version 7.3

The Received Via section of the out-of-the-box NewCorrSummary rule was being mapped to the property rule CommunicationType despite that property rule being configured locally. This has been fixed by setting the function to take the class name using dictionary instead of section xml.

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