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-A21096 · Issue 241281

Clarified dynamic text handling to better support localization

Resolved in Pega Version 7.2.1

The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.

SR-A21096 · Issue 239803

Clarified dynamic text handling to better support localization

Resolved in Pega Version 7.2.1

The use of properties and multiple field values to show dynamic text caused an issue where separate field values (3 fvs) were created for each part of a sentence and the context was not being correctly kept during localization. To resolve this, the system now uses a single field value with parameters.

SR-A21098 · Issue 246780

Updated row delete authorization failure error message

Resolved in Pega Version 7.2.1

The delete button at the top of the ListViewEditor was correctly configured to delete or not based on permissions, but the proper error message did not appear when the edit attempt failed. The function will now show the message "You are not authorized to delete row." in cases where there was no permission to delete the instance.

SR-A21109 · Issue 243685

Circumstanced decision table calls base table

Resolved in Pega Version 7.2.1

A circumstanced decision table configured to call a base rule (decision table) in an 'otherwise' clause was not working when the inputs called did not match any rows. This was an issue with Decision Trees and Decision Tables not calling the base class properly when VTable is enabled, and VTable has been turned off for these two rule types.

SR-A21196 · Issue 241336

RAP data pages made consistent across environments

Resolved in Pega Version 7.2.1

It was found that the Data pages for a RAP (rule-admin-product) deployed from dev1 to dev2 differed from the results of the same RAP deployed to demo if it contained a PageList(P1) inside which there is a PageList(P2) property that refers to Data Page (list type). This was caused by a handling difference between the two environments, and checks have been added to ensure consistent results.

SR-A21196 · Issue 233151

RAP data pages made consistent across environments

Resolved in Pega Version 7.2.1

It was found that the Data pages for a RAP (rule-admin-product) deployed from dev1 to dev2 differed from the results of the same RAP deployed to demo if it contained a PageList(P1) inside which there is a PageList(P2) property that refers to Data Page (list type). This was caused by a handling difference between the two environments, and checks have been added to ensure consistent results.

SR-A21266 · Issue 239797

Ensured default display after grid takes effect in tree grid without explicit erase

Resolved in Pega Version 7.2.1

Old configurations were still visible after choosing ?Default (display after grid)? unless the value of the section name was explicitly erased. This was due to the generated java code that still contained the data displaying the values in fields it did not consider empty, and the handling has been corrected to resolve this.

SR-A21298 · Issue 239141

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

SR-A21298 · Issue 240041

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

SR-A21304 · Issue 242768

Corrected Case Stages rendering on Perform harness

Resolved in Pega Version 7.2.1

After upgrade, the case stages were not rendered properly on the Perform harness. This was an issue with the InsHandle parameter and has been fixed.

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