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-D60447 · Issue 522751

Corrected unexpected save warning when switching tabs

Resolved in Pega Version 8.1.8

When using the Interaction Portal, entering case data on one open tab and then switching to another open tab caused the system to display a Save warning message as though the Tab has been closed instead of switched. This has been resolved by updating the system to skip the dirty alert when bPrompt is false in the Ajax Container container case.

SR-D61560 · Issue 539472

Support added for multiselect control with SmartTip for iPad

Resolved in Pega Version 8.1.8

When using a multiselect list control to a lproperty with Smart Tip configured, choosing one item on an iPad and then trying to tap or drag down the vertical scrollbar caused all listed items to disappear. To resolve this, the multiselect control has been updated to handle the popover exit on smart popover hover along with arrow key navigation support for tablets.

SR-D62038 · Issue 529156

Multiselect control security improvements

Resolved in Pega Version 8.1.8

Control_multiselect and multiselectresults have been modified to include protection against unauthorized javascript execution.

SR-D64244 · Issue 532981

Support added for recording with sIngle-option radio button inside a repeating grid

Resolved in Pega Version 8.1.8

Recording a test case was not working when a single option radio button (i.e., radio button control with property of type boolean) was configured inside a repeating grid. In this case, it was found that the Radio button markup did not have a data-test-id attribute for non-template single option; this has been added.

SR-D64667 · Issue 531805

Cursor issue resolved for tab within expandable row

Resolved in Pega Version 8.1.8

When pressing the “Tab” key on an expanded row, the cursor was not moving inside the expanded part. This has been fixed by adding a check to get the correct first focusable element.

SR-D64945 · Issue 534322

Accessibility enhanced for multiselect

Resolved in Pega Version 8.1.8

Aria attributes for multiselect items and container have been added to enhance accessibility.

SR-D65034 · Issue 529564

Check added for malformed query on F5 refresh

Resolved in Pega Version 8.1.8

A 500 Internal Server Error occurred when F5 was clicked to refresh the screen. This was traced to a malformed URL that was missing the '?' before the query parameters, and has been resolved by adding a check in the pzpega_ui_dynamicContainer_lite js file replaceHistory method that will insert the question mark if it is not present.

SR-D67012 · Issue 537307

Invalid dropdown time will retain entered time

Resolved in Pega Version 8.1.8

If a datetime control using dropdown mode and a timeofday property had a validation error, on refresh the current time was being set in the dropdown. This occurred when selecting only one part of the time property (only minutes or only hours), and included an error indicating that the provided time was not a valid time of day value. To resolve this, an update has been made so that if this combination has a validation error, on refresh setting the user-entered time will be given in the dropdown instead of the current time.

SR-D68776 · Issue 535466

Improved Timezone sync between operator setting and server

Resolved in Pega Version 8.1.8

When the operator timezone was empty, it defaulted to America/New_York in client side code. To better sync client and server, changes have been made so that when an empty timezone is seen, the system will retrieve the timezone from the server configuration.

SR-D71355 · Issue 537007

Support added for dynamic CSS class reference in optimized grid

Resolved in Pega Version 8.1.8

When using the property pyStatusWork in an optimized grid, it was not possible to set a color code for different work statuses. This worked on an unoptimized grid. This has been resolved with the introduction of a dynamic CSS feature. This control can be changed to an autogenerated control like "Formatted text" and apply color coding through classes. To use this, a property value must be specified in cell classes in the presentation tab of the table cell, and then populate each result of a data page with that property which contains some class value appropriate for status value. CSS must be written for the different classes (class name is stamped on <td> in markup).

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