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-D25972 · Issue 501481

Handling added for custom error message in post-authentication activity

Resolved in Pega Version 8.3.1

The error message in post authentication activity was always appearing as 'Login terminated because a post-authentication activity or policy failed' irrespective of the actual message being conditionally set in the activity based on post authentication logic. Investigation showed that the parameter page in the SSO post-authentication activity was not being passed to the 'pzShowAuthPolicyError' activity due to the post-authentication activity executing in authenticated context whereas the HTML fragment executed in the un-authenticated context. In order to support this use, post-authentication activity will set the error message on a predefined property and propagate that to the HTML fragment by appending the error message as a query parameter in the redirect exception URL post-authentication failure.

SR-D42406 · Issue 510668

Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage

Resolved in Pega Version 8.3.1

When using Connect-REST with pyRequestAttachmentPage, Polish characters like "ó" or "ł" were converted to "?". This did not happen when pyRequestAttachmentPage was not used. This was due to the post request body using a multipart handler that ignored the charset being passed in and considered it a respective enum type for Application/json internally instead. This has been resolved by adding support for charset UTF-8.

SR-123581 · Issue 188015

Scrolling corrected for Safari on mobile devices

Resolved in Pega Version 7.1.8

When using the global search on a tablet or mobile device, the results are displayed in a modal pop up in the browser. However, scrolling was not working when using Safari on a mobile device. To correct this, the Search Panel CSS and js were modified to enable scroll support on mobile devices.

SR-129159 · Issue 196998

Replaced missing OperatorID page for LDAP tab thread

Resolved in Pega Version 7.1.8

The OperatorID page in the clipboard was not visible in the tab thread when logged in through LDAP though it was visible in other threads or when not using LDAP. This was an error, and has been corrected.

SR-D30272 · Issue 499438

Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue

Resolved in Pega Version 8.3.1

After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.

SR-D45865 · Issue 513017

Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue

Resolved in Pega Version 8.3.1

After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.

SR-124952 · Issue 189563

Resolved HTMLtoPDF font load error

Resolved in Pega Version 7.1.8

When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.

SR-124952 · Issue 189565

Resolved HTMLtoPDF font load error

Resolved in Pega Version 7.1.8

When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.

SR-126775 · Issue 189860

Resolved HTMLtoPDF font load error

Resolved in Pega Version 7.1.8

When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.

SR-127932 · Issue 194420

Paragraph rules library modified for JSP tags

Resolved in Pega Version 7.1.8

A paragraph Rule created with some 'when' conditions and property references showed random contents updates after saving and check-in using the source button. This was traced to the use of a newer library for Paragraph rules that was not able to handle Pega JSP tags like "pega:when" or "pega:foreach", causing ckeditor to remove the content. This has been addressed.

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