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-118307 · Issue 172330

Integers with embedded spaces now prompt screen edit during validation

Resolved in Pega Version 7.1.7

If an Integer property was populated with a number with spaces ("12345 67890"), it generated the validation error "** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)". A numeric value with embedded spaces will fail during conversion to Integer, but this will now be caught with a screen edit in the same way a non-numeric character would be during screen validation.

SR-118528 · Issue 175205

Fixed server error alert generated by portal logout

Resolved in Pega Version 7.1.7

A "Server Error " error was being generated when logging off from "List views/Summary Views" in the Portal Dashboard. This occurred when the request to unload the page reached PRPC after the endsession completed and the request to unload was unable to find the associated session on the server as it has been already invalidated. The Wizard_MainWindow HTML rule has been modified to smooth the timing and clear the clipboard properly.

SR-118675 · Issue 172991

Corrected duplicated validation errors

Resolved in Pega Version 7.1.7

In some cases, validation error messages were being duplicated in the display. This was traced to code in the dynamic display being executed twice, and has been corrected.

SR-118722 · Issue 175625

Excessive length of filter window corrected

Resolved in Pega Version 7.1.7

In work object Audit window, the History table -> Description column filter window is appearing very long. This was caused by an inadvertent change to the listview function in conjunction with the Time column filter, and has been fixed.

SR-118725 · Issue 174420

Corrected focus for filter window using WAI

Resolved in Pega Version 7.1.7

With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.

SR-118884 · Issue 172536

Create Work correctly encodes Japanese characters

Resolved in Pega Version 7.1.7

When Japanese characters are passed as parameter to Create Work action, the newly created work item was registering cryptic characters instead of the expected Japanese characters. This was traced to a deprecated API, and has been corrected.

SR-119130 · Issue 173876

"?" character allowed in URLs with get requests

Resolved in Pega Version 7.1.7

When specifying an Alternate Domain URL for a link, if the URL contained a GET request followed by parameters ("?get&p1"), the URL was modified by SafeURL to include an "=%26" between the "?" and "get" ("?=%26get&p1") (%26 is url encoding for an ampersand & ). In order to ensure alternate URLs are properly processed when they contain "?", a check has been added.

SR-119158 · Issue 175351

Amended login caching to be compatible with new versions of Firefox

Resolved in Pega Version 7.1.7

When using the latest versions of FireFox browser (32+), there was a problem with logging in again after logging out. This was caused by a change in the cache engine for Firefox, and the system has been updated to compensate for the difference in caching.

SR-119239 · Issue 173898

Max limit error localized and variable added for unsaved work items

Resolved in Pega Version 7.1.7

In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization.

SR-119537 · Issue 174774

Improved speed for deleting repeat grid rows with Dynamic Select

Resolved in Pega Version 7.1.7

When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.

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