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-130352 · Issue 199182

Corrected Microsoft Internet Explorer error for opening harness in a popup

Resolved in Pega Version 7.1.8

Configuring a button click to launch a harness in a pop-up with the Microsoft Internet Explorer 11 browser caused the error "Internet Explorer cannot display the webpage." The cause was an errant space included in the pega.u.d.url for this browser, and the GenerateHarnessHTML and GenerateLayout RUFs have been updated.

SR-131269 · Issue 200188

Fixed Harness buttons and screen resize issue

Resolved in Pega Version 7.1.8

Harness buttons were not fixed, and the screen was resizing to unviewable height on changing to screen layout. To resolve this, CSS changes have been applied to the pzbase-browser - CSS and pzbase-ie9 - CSS files to include selector for dynamicContainer div inside workarea div in not size to content mode. The rule applied is position: absolute.

SR-122860 · Issue 183998

Added conversion of Turkish characters for Google Chrome

Resolved in Pega Version 7.1.8

Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex.  Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.

SR-122860 · Issue 182083

Added conversion of Turkish characters for Google Chrome

Resolved in Pega Version 7.1.8

Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex.  Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.

INC-155406 · Issue 638706

Clipboard security updated

Resolved in Pega Version 8.7

Security has been enhanced for clipboard properties by restricting registration for readonly properties.

INC-157367 · Issue 637948

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-157448 · Issue 638925

Latitude and longitude populated for CreateWork history

Resolved in Pega Version 8.7

After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.

INC-160805 · Issue 640854

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-160839 · Issue 643470

Session timer corrected

Resolved in Pega Version 8.7

Configuring pxsessiontimer in the Portal header to log users off after 30 minutes was not working as expected: users were still logged in the next day or after keeping the session idle for more than 30 minutes. After waking up the system, it was possible to search clicking on the search results resulted in being logged out. This was traced to the ShowLogoffTimer activity not being correctly registered, and has been resolved.

INC-161480 · Issue 629627

Confirmation button works on dirty alert

Resolved in Pega Version 8.7

The "Ok" button on the discard changes alert was not working. 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