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-172178 · Issue 655021

TransID updated to trim spaces

Resolved in Pega Version 8.7

While preparing newTransID from a response, special characters slipped into "newTransID" param value and generated an error. This has been resolved by updating the system to trim spaces from newTransID.

INC-172314 · Issue 650493

File selection dynamic layout added for Cosmos

Resolved in Pega Version 8.7

The Cosmos Files & Documents widget for managing content displayed the application's configured content sourcing repository, but the screen did not allow actually selecting a file from the repository. No browse option was available, and the submit button generated an error to select a file for upload. This was traced to a missing dynamic layout with file selection for Cosmos, and has been resolved.

INC-172483 · Issue 651710

Filtering updated for UI markup

Resolved in Pega Version 8.7

Filtering has been added to the UI code to preserve the browser display appearance but remove inappropriate or potentially insecure markup.

INC-172521 · Issue 651553

Email template content visible in user application

Resolved in Pega Version 8.7

An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.

INC-173238 · Issue 656504

Restored missing API call for icon navigation

Resolved in Pega Version 8.7

After logging in and searching for a bond, navigating to the home page without clearing the search string from the bond screen resulted in a pop-up warning to remove unsaved changes. Clicking on OK and then attempting to click on the list index number available below the table resulted in an error. Investigation showed pzCTkn was missing for the API calls triggered by clicking on the icon; this has been resolved by updating the pega_yui_connection.js file.

INC-173345 · Issue 655038

Check added for empty geolocation values

Resolved in Pega Version 8.7

Latency issues were traced to Geolocation-related errors in the log files. To improve performance, changes have been added to check for empty pyLatitude and pyLongitude before adding in the postdata of an async request.

INC-173382 · Issue 653442

Security update for previews

Resolved in Pega Version 8.7

Security updates have been made around the sanitizing of preview streams.

INC-173760 · Issue 658069

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

INC-173944 · Issue 660180

Cancel button on embedded GridRow cancels single action

Resolved in Pega Version 8.7

When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.

INC-174020 · Issue 650891

Performance improved for Directed Web Access (DWA)

Resolved in Pega Version 8.7

Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.

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