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-A3008 · Issue 219945

Check added to handle Next button disable for repeat grid

Resolved in Pega Version 7.2

The 'Next' button on a modal dialog was not disabled correctly when launched from a repeat grid due to the wrong "currentPageSize" being passed to the server when using an expand pane grid. A check has been added that will handle the expand pane grid and return the right "currentPageSize".

SR-D81341 · Issue 546006

Scroll bar scrolls to element automatically with Set Focus

Resolved in Pega Version 8.1.8

An issue with the Scroll bar not scrolling automatically to the correct element when using Set Focus has been resolved by including element select logic in settimeout.

SR-A733 · Issue 207631

Edited Propositions retain format

Resolved in Pega Version 7.2

When updating a Proposition using the "Edit" button, the format was lost, however updating the proposition using the "Bulk Edit"-> 'Edit in Excel' button preserved the formatting. This has been addressed by making the default UI control for the text values a Text Area, which maintains the multi-line format.

SR-A5880 · Issue 216627

Updated error label highlighting for reused sections

Resolved in Pega Version 7.2

The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.

SR-A8520 · Issue 217466

Updated error label highlighting for reused sections

Resolved in Pega Version 7.2

The error highlighting was inconsistent when a section was being re-used in the same screen. This was an issue with the use of multiple controls with the same label (label for=xxx) in the form, leading to only the first control?s label being highlighted in red. This has been fixed by looking at the label closest to the error element.

SR-A2960 · Issue 218751

Asynch loaded data pages correctly pulled into main thread

Resolved in Pega Version 7.2

After using Load-DataPage, using Connect-Wait to synchronize with child requestor caused the data page to be loaded again when it was referenced instead of the system bringing the asynchronously-loaded data page forward. This was caused by differing value handling during the cache key building for ADP load, and has been corrected.

SR-A6523 · Issue 214991

Handling added for storing email addresses with special characters

Resolved in Pega Version 7.2

When attempting to store an encoded email address with special characters to the database, an exception was thrown and the process failed. This was found to be a database/data management issue related to executeRDB expression parsing the SQL query first, using "\" as an escape character. The subsequent JDBC driver execution also used ""\"" as an escape character

SR-A4720 · Issue 212436

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.

SR-A4720 · Issue 212449

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.

SR-D76291 · Issue 541013

Check added for Repositories before saving attachment

Resolved in Pega Version 8.1.8

When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.

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