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-127915 · Issue 203511

Resolved NPE for URLEncryption in grids

Resolved in Pega Version 7.1.9

When URLEncryption is enabled in a grid scenario, the property reference was not generated as expected. In this scenario, the AjaxTrackID was not being passed from client to server due to it being a new harness load where normally a new AjaxTrackID would be created at the server end. To resolve this, the pzActionOpenURLInWindow API has been updated.

SR-128119 · Issue 202650

All localization errors displayed as expected

Resolved in Pega Version 7.1.9

When localization wizard generated errors during translations import, it only displayed one in the UI. This was an issue with the errors pagelist not being fully populated with values correctly in pzImportTranslations Activity, and has been resolved.

SR-129722 · Issue 204564

Removed extra white space appearing with Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.9

Using Microsoft Internet Explorer 8, extra white space appeared above the "Next" button in a screen flow when a declare expression was fired. This has been fixed.

SR-130340 · Issue 204442

Corrected date selection highlight for Date-Medium control

Resolved in Pega Version 7.1.9

When Date-Medium control was used in a section and configured with onchange->refresh section, selecting any date other than today's date and opening the calendar pop up again caused the selected date to not be highlighted in the pop-up. To resolve this, datetimecalendar.js has been modified to set the proper date in cases of cal.dateFormat == 3 (Date-Medium and DateTime-Medium control).

SR-130340 · Issue 207380

Corrected date selection highlight for Date-Medium control

Resolved in Pega Version 7.1.9

When Date-Medium control was used in a section and configured with onchange->refresh section, selecting any date other than today's date and opening the calendar pop up again caused the selected date to not be highlighted in the pop-up. To resolve this, datetimecalendar.js has been modified to set the proper date in cases of cal.dateFormat == 3 (Date-Medium and DateTime-Medium control).

SR-130963 · Issue 201149

Corrected Dynamic Select with refresh section

Resolved in Pega Version 7.1.9

Dynamic Select with refresh section was causing an unexpected change of focus in the Pega Survey component of the Care Management Framework (CMF), resulting in an erratic scrolling behavior for pages that have many questions that dynamically update the survey section by adding or removing questions. When these selections are made, the screen was consistently scrolling to the bottom of the question list. This was caused by a previous change made to focus the element based on ID to enhance accessibility, but this was missing the necessary accessibility check to limit it. That has now been added.

SR-131132 · Issue 205659

New 'when' rule added to enhance visibility conditions for embedded sections

Resolved in Pega Version 7.1.9

After upgrade, only the OK and Cancel buttons were displayed when editing a navigation rule. This was caused by a "pzShowPropertyPanel" section included in a "pzNavigationMain" section with a visible 'when' that was configured with both || and && causing exceptions while executing the expression. To handle this scenario, a new 'when' rule Embed-Rule-Navigation-Element.pzShowVisibleCondition has been created to be used in the pzNavigationMain section.

SR-131228 · Issue 202735

Local template use corrected for 'add item' in repeating grid

Resolved in Pega Version 7.1.9

In repeat grid with options "Expandable rows" and "Override default template", adding a row by action "Add item" resulted in the local template being replaced by the standard "pyGridRowDetails" template. In other cases (e.g. when use action "Edit item") user's custom template was used. To resolve this, templateName generation has been added for expanded pane configuration to check for local templates first before defaulting to the ones provided.

SR-131332 · Issue 204592

Resolved error on tab switching in DS portal

Resolved in Pega Version 7.1.9

After logging into Pega Designer Studio and launching a portal, performing a switch role/portal in the opened portal and then clicking on the Designer Studio tab closed the secondary portal tab. This was resolved, but an additional problem arose with an error being generated for the tab that was opened previously before switching applications when trying to save or modify the availability of already opened rules in the dev portal. This had to do with the API used to clean up the threads, and has been corrected.

SR-131825 · Issue 202123

Removed duplicate special character encoding on FieldValue validation

Resolved in Pega Version 7.1.9

A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.

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