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.

INC-142589 · Issue 595489

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.4.3

After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.

INC-142714 · Issue 596554

Recent Cases from different applications available to open

Resolved in Pega Version 8.4.3

An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.

INC-143005 · Issue 596954

Fluid Overlay displays as expected in Firefox

Resolved in Pega Version 8.4.3

After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.

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.

INC-161937 · Issue 640264

VMWare workspace One Mobile support added

Resolved in Pega Version 8.7

Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.

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