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-129015 · Issue 196408

Cleaned up section reload on change

Resolved in Pega Version 7.1.8

In a section with a drop down on which an onChange event was added and a refresh section is set as the action, the refresh section calls a data transform and no activity call. However upon execution, there was a pop up with the error message 'Illegal Argument Exception'. When the activity is cleared the section rule should remove the parameter, but the preactivity params were not cleared in the clipboard even after clearing the activity. This has been corrected.

SR-129075 · Issue 197719

Sorting corrected for mixed column types in virtual RD grids

Resolved in Pega Version 7.1.8

If a grid contained both dynamic and static columns, the sort icon did not change after clicking on a column to change the sort in a virtual report definition grid. This was due to a missing CSS style for the static columns in this scenario, and a check has been added to look for multiple column types.

SR-129080 · Issue 199016

Ensured correct clearing for error in DateTime control field

Resolved in Pega Version 7.1.8

If there was an error on the Datetime control field present in a repeat grid, correcting the value in that Date field and then adding another row that follows the one containing the error generated a popup error message and it was not possible to set the date. The issue was in the drop down display mode, which re-rendered an invalid field as empty but the corresponding input had the same invalid value. That caused the new submit with empty values (which is valid) to produce the same error due to the input present in the client. To resolve this, the invalid hidden input for will now also be reset.

SR-129101 · Issue 195816

Smoothed error handling for operator password change process

Resolved in Pega Version 7.1.8

After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.

SR-129101 · Issue 195933

Smoothed error handling for operator password change process

Resolved in Pega Version 7.1.8

After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.

SR-129159 · Issue 196998

Replaced missing OperatorID page for LDAP tab thread

Resolved in Pega Version 7.1.8

The OperatorID page in the clipboard was not visible in the tab thread when logged in through LDAP though it was visible in other threads or when not using LDAP. This was an error, and has been corrected.

SR-129171 · Issue 195047

Corrected error in order of operations for Numeral builder

Resolved in Pega Version 7.1.8

The Add function in reporting was not returning the proper result when included in an equation with multiple order of operations. This was an error in the Numeral function builder, and has been corrected.

SR-129211 · Issue 195705

Ensured expected deadline priority styling in workbasket

Resolved in Pega Version 7.1.8

The WorkBasket summary for the current WorkGroup on the Case Manager Portal was going straight from "normal" (green) styling to "urgent" (red) styling once one of the assignments in the WorkBasket went past Goal but had not yet passed Deadline. The intended behavior should show a "medium" styling until such time as one or more of the assignments is past Deadline. Once past Deadline, the styling should then be "urgent". The incorrect benavior was caused by an ordering problem in the Deadline and GoalTime columns, and code has been inserted to ensure proper behavior.

SR-129230 · Issue 196382

Text input handling updated for Microsoft Internet Explorer10/Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

When the control for a text box is set to "Integer" and Type is set to "Number" in the Presentation tab while using the Microsoft Internet Explorer10 orMicrosoft Internet Explorer 11 browser, the text was grayed out while typing and any entered text disappeared on blur. This was an issue where If the input type was a number and a placeholder was given, the placeholder was not behaving properly. However, without the placeholder any non-numeric character entered would disappear. To resolve this, the JavaScript for the text input has been updated to render properly for these browsers.

SR-129232 · Issue 197812

LiveUI inspector enhanced to uncover elements inside non-Live UI frames

Resolved in Pega Version 7.1.8

Issues were found with inspecting elements inside non-auto sections from Live UI; Live UI inspector did not point to the relevant UI component, but rather pointed to the header level, causing frames inside an iframe without Live UI Code to be ignored even if they did have elements that could be inspected by Live UI. In order to ensure all elements are caught, code changes have been inserted to loop over all child frames and recall itself with the next frame to cover all elements that can be inspected by Live UI.

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