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.

INC-208499 · Issue 702516

Corrected Ajax container scrollbar with tabs

Resolved in Pega Version 8.5.6

The scroll bar was not working as expected for a pyCaseWorker Section configured with an Ajax container and "Show as tabs". This has been resolved by overriding the div[data-mdc-recordid] with overflow-x: auto style to get the proper horizontal scroll in the Ajax container.

INC-208848 · Issue 703875

Cosmos landing page configuration icon updated

Resolved in Pega Version 8.5.6

In order to allow changing the Cosmos landing page configuration icon, the harness has been made available. The default icon has also been updated.

INC-209071 · Issue 706041

Other Currency resolves value in Pega DX

Resolved in Pega Version 8.5.6

When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.

INC-210760 · Issue 708530

Corrected malformed URL

Resolved in Pega Version 8.5.6

The function used in the session timer to log off the user was not working consistently, and attempting to discard a checked-out delegated Rule did discard the rule. Both issues reported the error "HTTP Status 400 - Bad request". This was traced to a badly formed URL, and has been resolved by wrapping the URL with SafeURL_createFromURL.

INC-172944 · Issue 662828

Skin rule circumstancing article added

Resolved in Pega Version 8.6.4

An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.

INC-176462 · Issue 657412

Dashboard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.6.4

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

INC-180100 · Issue 662894

Scrollbar persists for multiselect

Resolved in Pega Version 8.6.4

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183672 · Issue 701868

Corrected vertical scroll bar for iPad Mashup page

Resolved in Pega Version 8.6.4

After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.

INC-186081 · Issue 675207

Report filter popup displays correctly

Resolved in Pega Version 8.6.4

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

INC-187196 · Issue 680749

Resolved Ajax popup alert for optimized iOS table

Resolved in Pega Version 8.6.4

When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.

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