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-119725 · Issue 176399

Smoothed Report Definition handling for missing or incorrect ObjClass

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

In some situations, a Null Pointer Exception was being generated after a call to a report definition on the Report Content Page. This occurred when given a target results page with a missing or incorrect pxObjClass. The code has been modified to generate the error "Invalid Report Content Page" instead of the NPE if the ObjClass is incorrect, or to complete the processing if the ObjClass is empty.

SR-119858 · Issue 175151

Adjusted code to prevent double-localization when using Google Chrome

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When utilizing a locale that uses commas instead of points to demarcate decimals in numbers, editing any numbers in a skin caused extra zeros to be added to the numbers. When using Google Chrome, if an input type is a number, Google Chrome by default will localize. The control is also localizing the value after reload, so localization is happening twice. In order to resolve this, If the input type is text, only control localization will happen.

SR-119869 · Issue 176176

Access Role Editor link errors fixed

Resolved in Pega Version 7.1.7

When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.

SR-119909 · Issue 176760

Fixed page toggle when a grid contains an error

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

It was not possible to navigate to a different page in a grid when a validation error existed on any page.The error could be corrected if it occurred on the current page and paging ability would return, but if the error as in a different page it was not possible to navigate to correct it. This was traced to code which prevented moving to another page if there was an error on refresh. While there was a workaround, the code has been updated to allow moving to another page unless the error occurs on the current step page.

SR-119926 · Issue 177335

Smoothed handling of dynamic select with refresh section

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

In the course of server-side prep of the list for a Dynamic Select (via a long running activity wrapped up with a per interaction refreshing Declare page), the Refresh Section event is getting fired. This causied the properties bound to Dynamic Select controls (either in read-only or editable modes) to lose their values. This was resolved by modifying the dynamic select code to load the dynamic select values and set default value upon refresh action (even in case of readonly).

SR-119989 · Issue 176616

DateTime control logic improved for repeating grids

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

If a repeat grid was configured with 'pxDateTime' control for one of the columns, clicking the 'calendar' icon for the first time would not show the calendar. Thereafter, the calendar would appear on icon click. This was found to be an error in the javascript logic where the DatePicker function was returning false even if the event was from the DatePicker control. This has been corrected.

SR-120181 · Issue 177028

Lock msg "currently being modified by" now localized

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

An enhancement has been added to make the lock screen message " is currently being modified by " available for localization.

SR-120217 · Issue 177095

Resolved deleting rows where the InsKey contains spaces

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

Deleting rows from a Data Table was not working in Google Chrome or Firefox when using the associated DataTableClassEditor list view for the Data Table. Clicking the delete icon calls javascript to retrieve the insKey of the row to be deleted, but if the insKey had a space it was being encoded as " " and then did not match the passed insKey to determine the row to be deleted. In order to prevent this problem, the javascript has been updated to correctly handle the space character.

SR-120321 · Issue 176135

CPU efficiency improved for SmartInfo popup

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

In order to maintain a low demand on the CPU, the smartinfo popup has been modified to not maintain itself in a ready state.

SR-120505 · Issue 177090

GetNextWork Tab title 'Next" now localized

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

On performing GetNextWork in CaseManager Portal, the label 'Next' is displayed as the Tab title temporarily before opening the work object. This label has now been made available for localization.

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