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-176403 · Issue 653575

Security updated for buttons

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated for Button controls.

INC-176734 · Issue 655177

Invalid manual time value stops progress and displays error

Resolved in Pega Version 8.7

When an invalid time was manually entered, eg. 11, the system previously remained in an error state until the time was corrected. Post-update, the current time of the user's session / browser was populated into the time field when an invalid time was entered. Although the error still displayed, the current time was saved and the user could continue. This has been resolved by adding a condition to show the entered time value and not continue if the entered time value is invalid.

INC-176742 · Issue 657070

DX API JSON response maintains special characters

Resolved in Pega Version 8.7

When processing a Pega workflow with external UI through the DX API, entering some value with special characters like "(" and saving the case resulted in "(" being replaced with junk characters that were displayed on the UI when the case details were sent back from Pega. This was traced to special chars not being supported in the validation error message when displayed on c11n system, and has been resolved by consuming the 'message' value in the error object instead of localizedValue.

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.

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