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-B36254 · Issue 293924

Removed error appearing on multiple tabs

Resolved in Pega Version 7.3

On a multiple tab scenario when client side validation was triggered on a specific tab ad that layout was under a tabbed repeat in a section, a warning icon appeared on other tabs as well. This is due to marking for tab repeat not being supported at this time: in these conditions, the system will skip the marking error.

SR-B3633 · Issue 274006

Tab layout focus corrected for "show next error"

Resolved in Pega Version 7.3

The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.

SR-B36556 · Issue 301271

Internet Explorer text input focus fixed

Resolved in Pega Version 7.3

In IE, the mouse could not be used to return focus to a text field once there was text input followed by other clicks around the screen. This was traced to a grid inside the modal dialog launched by a button with an incorrect div that led to the text box losing editability. To resolve this, a check has been added.

SR-B36567 · Issue 296311

Full year date data made available to Excel for consistency

Resolved in Pega Version 7.3

Inconsistencies were seen in the handling of the year field on dates using Date or pxDateTime as a control, at times displaying the same input as 01/01/1917, 01/01/17, and 01/01/2017. To fix this, the date format in pzExport_Date_RD control has been modified from DEFAULT_DATE_SHORT to DEFAULT_DATE_SHORT_YYYY so the full year component is available for Excel.

SR-B36880 · Issue 294350

Fixed SmartInfo positioning

Resolved in Pega Version 7.3

When any action like Refresh section, Post Value, or set value was configured before the Show SmartInfo, the smartinfo was suppressed. This was because the TargetElement was coming as stale and positioning the smartinfo based on a stale element resulted in it not getting displayed. This has been fixed by adding code to update the latest target element before positioning the smartinfo.

SR-B3704 · Issue 276504

Added check for cancel modal in expand-pane grid

Resolved in Pega Version 7.3

A modal window would not close if the modal dialog was launched after a row of an expand-pane grid was expanded. The issue was caused by a call to an incorrect version of the cancel modal for this configuration, and a check has been added to ensure the proper version is used.

SR-B37923 · Issue 295190

null-pointer exception fixed for ForceCaseClose

Resolved in Pega Version 7.3

An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.

SR-B37958 · Issue 296563

Radio button error highlight fixed for grids

Resolved in Pega Version 7.3

When a radio-button was configured as mandatory in a grid column, submitting the page without filling in the mandatory field did not correctly highlight the error. This was caused by the system not being able to find the correct label for the associated elements, and code has been added to find the correct label when the radio button is inside a grid.

SR-B38101 · Issue 299647

Corrected DateTime corruption

Resolved in Pega Version 7.3

If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.

SR-B38262 · Issue 295697

Fixed case error in DayOfMonth property

Resolved in Pega Version 7.3

When trying to add a DateTime Property/Column with function 'Day of the month', an exception was generated. This was due to an error in the wrapper creating the Function Alias name 'DayofMonth' instead of the correct 'DayOfMonth', 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