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-A11534 · Issue 227038

ExecuteSLA activity modified to avoid requeue errors

Resolved in Pega Version 7.2.1

When a broken process SLA was requeued, it went back into the broken queue because the underlying problem assignment was never marked as repaired on requeue. When execution of SLA fails, the assignments are marked as problem assignments in ExecuteSLA activity. The ExecuteSLA activity has now been changed to avoid creating a assignment error by instead using Obj-Cancel to roll back the assignment submission so items can be requeued directly from the SMA portal.

SR-A11665 · Issue 229766

Fixed Bulk Process deselecting some sorted items

Resolved in Pega Version 7.2.1

In Internet Explorer using Bulk Processing, after selecting a column to re-order and several individual items resulted in unexpected checkbox results where certain selected items were deselected and not processed. These items could later be processed individually. The logic has been updated to ensure proper checkbox handling with all browsers.

SR-A11690 · Issue 234461

Filtering added for bulk workbaskets

Resolved in Pega Version 7.2.1

Workbasket filtration has been added for bulk actions workbaskets.

SR-A11695 · Issue 229147

EXCEPTION_BLACKOUT time calculation fixed

Resolved in Pega Version 7.2.1

When calculating the time for the EXCEPTION_BLACKOUT period in EmailListener, the dimensions were incorrect due to errors in the sleep time observed when email listener failed to establish connection. This has been fixed.

SR-A11817 · Issue 233321

Skim_Validate rule made available

Resolved in Pega Version 7.2.1

In order to resolve issues with Offer flow rules not being moved after skimming the ruleset, a new version of Skim_Validate was added to Rule-Obj-Flow-Offer, deleting all steps except for the call to Rule-.Skim_Validate. To make this function fully available, Skim_Validate has now been marked as available to allow extending the activity to a rule form.

SR-A12114 · Issue 227211

Customization added to conflict dialogue

Resolved in Pega Version 7.2.1

An enhancement has been added to conflictDialogTextTemplate to allow customization.

SR-A12209 · Issue 230428

Updated Module Indexing to avoid duplicates

Resolved in Pega Version 7.2.1

Module indexing was not unique, potentially creating a problem with the Module Group where the same index could be created for two different document. This has been resolved by changing showDocument to use the thread id to build the module id so that it will be consistent and unique.

SR-A12319 · Issue 226251

Repaired code generation for Single Page property reference

Resolved in Pega Version 7.2.1

Referencing a Single Page property in a Rule-Utility-Function parameter of type ClipboardPage generated Java that created a Clipboard Property at runtime, resulting in a ClassCastException. The code generation process for this was incorrect, and has been repaired.

SR-A12342 · Issue 226223

Standard System Usage Summary report updated with Daily Usage Table

Resolved in Pega Version 7.2.1

When the Standard System Usage Summary report was run, no users were shown even though users were able to access the system. The Hourly and Daily Usage Reports show data collection, but this was not propagated to the Summary report. This was an issue caused by the Summary Report not accepting values from the Daily Usage table, and schema updates have been made to fix this.

SR-A12357 · Issue 230904

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and 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