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-A15627 · Issue 232738

JBoss shutdown errors resolved

Resolved in Pega Version 7.2.2

During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.

SR-A97991 · Issue 263957

Index reference synchronizer upgraded to capture previously shipped rulesets during upgrade

Resolved in Pega Version 7.2.2

During upgrade, some sites were seeing an SQLIntegrityConstraintViolationException error. This was caused by the presence of rulesets (e.g. PegaUVU, PredictiveAnalytics-UI) that were once shipped but are no longer, but that have rules that are still shipped. To correct this problem, the index reference synchronizer has been upgraded to capture those previously shipped rulesets.

SR-A98390 · Issue 252437

Scheduled report cleanup error resolved

Resolved in Pega Version 7.2.2

Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.

SR-A99040 · Issue 268520

Cleared email field in FieldMarketer campaign remains blank

Resolved in Pega Version 7.2.2

If the Email field of a FieldMarketer campaign was cleared and saved, closing and then reopening the session filled the email field with the Operator ID, which is not a valid email address. This was traced to Operator Email always defaulting to OperatorID if empty, and the activity has now been modified to not set the email field if empty.

SR-A88491 · Issue 252281

Localization added for "Summary for" and "Edit Dashboard"

Resolved in Pega Version 7.2.2

Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.

SR-A88491 · Issue 240995

Localization added for "Summary for" and "Edit Dashboard"

Resolved in Pega Version 7.2.2

Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.

SR-A88491 · Issue 251537

Localization added for "Summary for" and "Edit Dashboard"

Resolved in Pega Version 7.2.2

Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.

SR-A77514 · Issue 239717

@baseclass!pyMemo has been made available

Resolved in Pega Version 7.2.2

Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.

SR-A87928 · Issue 255259

Fixed cataloging for v5 hotfixes

Resolved in Pega Version 7.2.2

Recent modifications to obtaining catalogs for supporting additional products (i.e. frameworks) caused a regression in being able to check dependency information on v5 hotfixes, preventing DL files from being created for them. This has been fixed.

SR-B5634 · Issue 274715

Stack frame handling made more robust

Resolved in Pega Version 7.2.2

Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.

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