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-171663 · Issue 655244

MashUp dynamic parameters article updated

Resolved in Pega Version 8.5.5

The documentation for MashUp best practices has been updated to clarify that dynamic parameters sent from the client side using "pega.web.api.setAuthenticationParameters" API will be sent as part of the query parameters and won't be part of the encrypted hash as this hash is generated on the server end while generating the mashup code in the mashup channel.

INC-172178 · Issue 655020

TransID updated to trim spaces

Resolved in Pega Version 8.5.5

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-173238 · Issue 656503

Restored missing API call for icon navigation

Resolved in Pega Version 8.5.5

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 655037

Check added for empty geolocation values

Resolved in Pega Version 8.5.5

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 653441

Security update for previews

Resolved in Pega Version 8.5.5

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

INC-173944 · Issue 660182

Cancel button on embedded GridRow cancels single action

Resolved in Pega Version 8.5.5

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 650889

Performance improved for Directed Web Access (DWA)

Resolved in Pega Version 8.5.5

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.

INC-175322 · Issue 658649

Focus set correctly on the modal window in theme-Cosmos

Resolved in Pega Version 8.5.5

In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.

INC-175394 · Issue 661457

Date Time format corrected for Chinese locale

Resolved in Pega Version 8.5.5

The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone.

INC-175814 · Issue 657821

Runtime edit saves section to correct class

Resolved in Pega Version 8.5.5

When the active thread had an Ajax container embedded in it and a runtime edit was made of a section in the Ajax container thread, the section was saved into the parent thread's work object class. This was an unsupported use case, and has been resolved by adding support for runtime editing of sections from an embedded Ajax container.

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