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-129988 · Issue 197489

Updated API for postvalue checkbox handling

Resolved in Pega Version 7.1.8

In a Repeating Grid, the select all check box with PostValue action in the header was showing an HTML response message on reselect after deselecting all the individual checkboxes, and the master checkbox disappeared. This was caused by the wrong context page being sent and the API has been updated to fix this.

SR-130029 · Issue 197162

Localization added to filter control grid in Listviews

Resolved in Pega Version 7.1.8

Localization has been added to the popup opened on click of "Click to filter by" in Listviews.

SR-130067 · Issue 197823

Updated API for opening WB assignments on certain iPads

Resolved in Pega Version 7.1.8

On IOS 7.0.3 4th Gen iPads, attempting to open any workbasket assignments generated an "Empty Assignment Key" error. This was caused by the querySelectorAll browser API not returning correct results in this scenario, and has been corrected by modifying the evaluation method to use the document.evaluate method API.

SR-130101 · Issue 196914

Update to add portal compatibility for Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

A meta tag has been added to the frameset HTML rule to ensure compatibility with the Microsoft Internet Explorer 11 browser to access the User and Manager portals.

SR-127173 · Issue 192701

Resolved save error for custom date format

Resolved in Pega Version 7.1.8

A custom date entry given Display mode 'Text Input + Calendar' and the option 'Display value using read-only formatting' and using the format dd.MM.yyyy returned the error 'Entered date value is Invalid' when attempting to save. This was an issue where the processOnBeforeSubmit function code exists to replace the client formatted value with the value which need to be submitted but doSave was using the submitWhenFail API where it has its own logic to process elements. To resolve the issue, the system will call a common function from both places to obtain the proper setting.

SR-128261 · Issue 192779

Corrected accessibility for buttons assigned a menu role

Resolved in Pega Version 7.1.8

With JAWS accessibility active, navigating to a menu button titled "Other Actions" causes JAWS to read "Menu. To move through items press up or down arrow...O." If the JAWS instructions are followed, it reads out the caption/title of the next field rather than actually reading out the options in the menu. This was caused by JAWS not reading the label of a button which has popover window on click action and has the 'menu' role added to it. To resolve this, if there is a role in the button generation RUF, its value has been set to "menu".

SR-130147 · Issue 196723

pxCWOptionsMenu now localized

Resolved in Pega Version 7.1.8

Localization has been added for the section pxCWOptionsMenu.

SR-130249 · Issue 199071

Resolved validation error for modal window with right tabs

Resolved in Pega Version 7.1.8

Validation errors in a modal window could cause the user session to hang when the content of the modal window was configured to use a tab group with tabs positioned to the right. This was a div ordering error in the API, and a check was added for tab position right.

SR-130269 · Issue 197947

SmartInfo call updated for Listview in standards mode

Resolved in Pega Version 7.1.8

After upgrade, instances of SmartInfo configured on listview showed improper styles. This was due to the older version of the SmartInfo control being used when the document was in standards mode. The listview function has been updated to use the updated SmartInfo control for proper rendering.

SR-130363 · Issue 200006

Dynamic decimal place value setting added

Resolved in Pega Version 7.1.8

Previously, the 'pxNumber' control had Decimal Places set to 2. This setting became Auto in ML7, which resulted in no decimal values being displayed for whole numbers in some installations with custom settings after upgrade. To facilitate overriding this out-of-the-box function, a dynamic setting has been added: create a dynamic system setting rule with purpose "DecimalPlacesforpxNumber" in the ruleset "Pega-UMicrosoft Internet Explorerngine" with a given value from -1 to 10, and it will override the Auto value in the pxNumber control decimal places setting.

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