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.

SR-121331 · Issue 180473

Updated handling of Visio objects in Word files

Resolved in Pega Version 7.1.8

In order to cleanly present Visio images, they have been included as Visio objects in recent versions of the software and the objects were only viewable in Visio itself. This required switching back and forth from Word to Visio while viewing a document with Visio objects included, which was not ideal handling. In this release, the behavior has been further updated: The documentation will be generated server side, so no Visio glimpse will be possible in the app docs. The ERDs will still be included as embedded Visio files, but instead of the icon the system will present an embedded image. Clicking on the image will open Visio. Documentation has also been added to clearly indicate that Visio is required for a more detailed view of the ERD.

SR-121331 · Issue 184808

Updated handling of Visio objects in Word files

Resolved in Pega Version 7.1.8

In order to cleanly present Visio images, they have been included as Visio objects in recent versions of the software and the objects were only viewable in Visio itself. This required switching back and forth from Word to Visio while viewing a document with Visio objects included, which was not ideal handling. In this release, the behavior has been further updated: The documentation will be generated server side, so no Visio glimpse will be possible in the app docs. The ERDs will still be included as embedded Visio files, but instead of the icon the system will present an embedded image. Clicking on the image will open Visio. Documentation has also been added to clearly indicate that Visio is required for a more detailed view of the ERD.

SR-121429 · Issue 187948

Encoded handling for Chinese characters in SOAP

Resolved in Pega Version 7.1.8

Signature verification failed when a SOAP message contained multibyte Chinese characters. This was due to the engine passing platform specific request bytes instead of sending UTF bytes to the third party metro webservices code when signature is enabled. The JAR encoding has been modified to use the style it gets in the request in order to bypass third party platform decisions.

SR-121464 · Issue 182061

Editing privileges corrected for the clipboard

Resolved in Pega Version 7.1.8

An issue was found where it was possible to use the "Edit" option in the clipboard even when the clipboardViewerUpdate privilege is set "0" or blank. This has been resolved via rule check-in with a 'clipboardViewerUpdate on Edit' function to ensure proper privilege setting.

SR-121471 · Issue 179231

Potential XSS vunerability eliminated

Resolved in Pega Version 7.1.8

The system has been modified to enhance security and eliminate a potential XSS vulnerability related to adding a file attachment.

SR-121475 · Issue 188297

Row repeat behavior smoothed for HTML5

Resolved in Pega Version 7.1.8

After migrating, row repeat was expanding the width of all the cells each time the section was refreshed even if the width was selected as pixel (fit to content). Selecting "include HTML5 document type" option at the application level prevents the issue, but this issue has been addressed with the "Align Column With Data" Check box available on header cell.

SR-121501 · Issue 183603

Enhanced security for SQL exceptions errors

Resolved in Pega Version 7.1.8

In order to avoid a potential security vulnerability, the error messages generated by database exceptions have been made consistent for DB2 and Oracle and do not display SQL information in the log.

SR-121535 · Issue 188591

Autocomplete response tuned to resolve latency

Resolved in Pega Version 7.1.8

When the autocomplete list was displayed, a delay was seen between the focus highlight and the mouse pointer when using Google Chrome or Microsoft Internet Explorer 11. The highlight style is applied using CSS hover selector and the style is applied by the browser, so any delay is dependent on overall performance of the application in the browser, however the system has been optimized for performance and some memory leaks were tightened, and the overall application should display a noticeable improvement in response time.

SR-121588 · Issue 181232

Updated PDF conversion for latest versions of Microsoft Internet Explorer

Resolved in Pega Version 7.1.8

When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.

SR-121588 · Issue 176641

Updated PDF conversion for latest versions of Microsoft Internet Explorer

Resolved in Pega Version 7.1.8

When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.

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