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-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-A99155 · Issue 253246

Mobile dirty page handling corrected

Resolved in Pega Version 7.2.2

When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.

SR-A76763 · Issue 251569

Ensured Dirty pop up appears for mobile log off

Resolved in Pega Version 7.2.2

While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return if dirty to resolve this.

SR- · Issue 270969

Mobile Client Cache populated with pyWorkPage info

Resolved in Pega Version 7.2.2

While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.

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