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-176971 · Issue 658300

Web Mashup works from nested iframe

Resolved in Pega Version 8.7

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

INC-177104 · Issue 666334

Resolved-by field reflects queue processor close

Resolved in Pega Version 8.7

When a case was resolved by the queue processor, for example when the SLA ended and a case was automatically Resolved-Withdrawn by the system, the "Resolved by" field was blank. This was caused by the pyOperatorInfo control looking for the system account user data in the application users pool, and has been resolved by updating the control to display the localizable "System" name in this scenario.

INC-177263 · Issue 655829

isFutureDate edit validation fires correctly

Resolved in Pega Version 8.7

The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.

INC-177852 · Issue 658653

Added UI handling for error message on Delegated data table

Resolved in Pega Version 8.7

It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll.

INC-178116 · Issue 660565

Article on configuring display options for a harness updated

Resolved in Pega Version 8.7

The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.

INC-178417 · Issue 670114

Flag reset added for grid with 'Expand When'

Resolved in Pega Version 8.7

A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.

INC-178639 · Issue 658054

Improved accessibility for Autocomplete Role

Resolved in Pega Version 8.7

Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.

INC-178658 · Issue 657388

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.

INC-179378 · Issue 661173

Repeating Layout renders correctly after update

Resolved in Pega Version 8.7

Repeating dynamic layout was not working properly after update. This was caused by a missing active class, and was traced to changes made in the pzpega_ui_layoutgroup function where reload happens on close of a modal dialog. To resolve this, a safe check has been added to setInActiveLayout in layoutgroup.js.

INC-179478 · Issue 662927

Handling updated for progressive load on scroll in repeating dynamic layers

Resolved in Pega Version 8.7

When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate.

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