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.

SR-D40762 · Issue 510368

ReloadSection passes event object explicitly

Resolved in Pega Version 8.3.1

After upgrade, 'replace current-model' was not working when used in a section with a link control that had an onClick event that was intended to launch a local action. Investigation showed that the link control was not working in the latest Google Chrome version, and this has been corrected by passing the event object explicitly to the reloadSection function in PZPEGA_UI_DOC_SUBMIT.js

SR-D41984 · Issue 510011

Added handling to correct '&' displayed as '&' in custom tab name

Resolved in Pega Version 8.3.1

When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.

SR-D42701 · Issue 510921

Cross-site scripting security added for Case Manager

Resolved in Pega Version 8.3.1

Cross-site scripting security has been added to the Document features in the Case Manager portal.

SR-D48887 · Issue 512944

Read-only text inputs remain read-only after browser refresh

Resolved in Pega Version 8.3.1

Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.

SR-D43141 · Issue 512433

Support added for iFrame Mashup resize when using SPA

Resolved in Pega Version 8.3.1

After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.

SR-D43468 · Issue 511642

Includes() function changed for Microsoft Internet Explorer compatiblity

Resolved in Pega Version 8.3.1

The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer , resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.

SR-D44546 · Issue 512598

Corrected opening collapsible rows with modal action inside a nested pane grid

Resolved in Pega Version 8.3.1

After expanding the second level of a collapsible row in a table and then collapsing the row back down again, trying to expand other rows in the table did not work and the error "Unable to get property 'target' of undefined or null reference" appeared on the console. This was an issue with a modal action configured inside a nested pane grid that was attempting to call a target key on an undefined object, and has been resolved by explicitly checking for the existence of the 'event' object before calling the 'target' key on it.

SR-D45527 · Issue 512324

Corrected comma in chat appearing as ',null,'

Resolved in Pega Version 8.3.1

When a comma was sent in chat, it appeared as ",null,". For example, " I am applying the loan now,null, thanks ". Investigation showed that this was caused by Pega code that was overriding a JSON parse native API, and it has been resolved by removing the override and handling the Pega parse via a different API.

SR-D46532 · Issue 512375

Aria-label added to 'clear search option' icon

Resolved in Pega Version 8.3.1

After applying a search in the reporting functionality, the Clear Search icon becomes active. In order to improve accessibility, an aria-label attribute for icon/image control has been added to this icon.

SR-D46545 · Issue 511851

Count of remaining characters in a text box made accessible

Resolved in Pega Version 8.3.1

In order to improve accessibility, aria-describedby has been added to the Text Area character counter span element's ID so the remaining number of characters to enter in the text field will be read by the screen reader.

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