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-C36835 · Issue 376391

Performance improvement for RetrieveReportData

Resolved in Pega Version 8.1

Unnecessary processing on pyReportParamPageName in the activity pxRetrieveReportData was causing poor performance. This has been improved by adding a check to skip unnecessary operations in cases where the report definition is invoked from a Data page.

SR-C36874 · Issue 382948

Target object handling updated for post-download anchor tags

Resolved in Pega Version 8.1

Once an attachment was downloaded, clicking on anchor tags with href as "#" triggered a browser history popstate event which navigated the page to the Work List. This was due to the code fixing on an incorrect event object, and changes have been made to resolve to the correct target.

SR-C36918 · Issue 382619

PageList properties for List assertion resolve to correct class

Resolved in Pega Version 8.1

Errors indicating "pyStepPage can not be empty for List card" occurred when attempting to save Strategy related Test cases. This was traced to the system not not resolving to the correct class instance type when loading PageList properties for List assertion in strategy related Test cases, and has been corrected.

SR-C36918 · Issue 382615

Truncation added to handle creation of test case label >64 chars

Resolved in Pega Version 8.1

Attempting to create a strategy-related test case failed if the test case label given was more than 64 characters. To better handle this limit, specific code has been added to form a test case label that will truncate it to 64 characters if the label of the test case exceeds that limit.

SR-C37168 · Issue 378659

Check added to ensure autocomplete off is honored

Resolved in Pega Version 8.1

Clicking on the Auto complete control in the Google Chrome browser automatically suggested values stored earlier. To fix this, a check has been added in order to handle browsers that do not honor the standard autocomplete value of "off".

SR-C37273 · Issue 379523

Support added for creation of tags in local alphabets

Resolved in Pega Version 8.1

In order to support the use of other alphabets to create tags in the KM application, validations of regular expressions have been moved from the pxCreateTag to a new activity called pyValidateTagName which can be overridden as needed.

SR-C37311 · Issue 375813

Changed refreshSurvey to use pega.util.event to get the event object

Resolved in Pega Version 8.1

An issue was seen where it was not possible to select an answer on a survey. This was due to Firefox not honoring 'window.event', and has been resolved by modifying refreshSurvey to use pega.util.event to get the event object instead of window.event.

SR-C37339 · Issue 377590

Catch block added for EOF exception in Connect-REST

Resolved in Pega Version 8.1

When running the data page with rest connector as source that invokes a Connect-REST with another service provider, the response was returned as empty. This was traced to an end-of-file (EOF) Exception generated when content encoding is gzip and chunked body is empty. To fix it, a catch block for EOF exception has been added to the copyToBuffer method so that it returns an empty byte array this case.

SR-C37540 · Issue 390176

Fixed Recent Work gadget display of work objects

Resolved in Pega Version 8.1

After upgrade, the work object in the Recent category was showing as Undefined when rendering the recent work gadget (Launch User/Manger portal, search for the Work ID). This has been resolved by defining the PegaWorkData JavaScript function in RecentWorkGadget non-auto control and using PegaWorkData instead of FormData.

SR-C37748 · Issue 379478

Connect-SOAP 'Request Only' call maps SOAP async call faults

Resolved in Pega Version 8.1

When a failure occurs on a Connect-SOAP configured as 'Request Only' with asynchronous processing, the failure was not logged or copied to the clipboard. This was standard behavior for Request-Only, but did not account for asynchronous calls where the status code was not correct for failed calls. This has been updated to correctly register the failed calls.

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