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-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.

SR-D38946 · Issue 507905

Dragresize plugin removed from RTE for better Microsoft browser compatibility

Resolved in Pega Version 8.3.1

When a messge was sent through Pega chat while using the Edge web browser, the text field where the message was entered before the send button was pressed did not get cleared. This was traced to the Edge browser throwing a Permission Denied error while attempting to access a detached DOM element. To resolve this, the 'dragresize' plugin has been removed from RTE as its implementation is not compatible with Microsoft Internet Explorer 11 and Edge.

SR-D39455 · Issue 508604

Shortened URLs (bit.ly) supported with custom image size

Resolved in Pega Version 8.3.1

Marketing offers were very slow to load, often generating requestor lock exceptions due to the wait time. This was traced to one cell in one section that housed a company logo: the source to icon had a shortened "bit.ly" URL when the ImgaeIO API in Java expected the actual URL as its input. The API could not convert the shortened URL to the actual URL, resulting in the retries and connection failure. To resolve this, 'javax.imageio.ImageIO' invocation will happen only when the image size is auto. If custom height and width are used to display an image, Pega will not depend on the Java library and the system will be able to resolve the shortened URL.

SR-D45415 · Issue 510911

RemoveThreadLEvelPages modified to preserve primary page for current action

Resolved in Pega Version 8.3.1

The Job Scheduler Executions drill down showing success/fail results was inconsistently showing results for the wrong jobs when sorting by column (job name). Unsorted, it opened the correct results. This was traced to the pyRemovethreadLevelPages activity removing all pages including datapages on doUIAction, causing any action performed on the UI after sorting the grid to open a wrong page. This was an issue for both the Job scheduler page and the Queue processor page. To resolve this, the pyRemovethreadLevelPages activity has been modified to not remove the data page if it is the primary page for the current action.

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