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-C57130 · Issue 402934

TokenRangePartitioner modified to avoid Cassandra timeouts

Resolved in Pega Version 8.1.2

The previous DSS settings caused the DDS dataset on Browse to create thousands of partitions. This caused thousands of files to be created for a file dataset which uses a DDS dataset as input. In order to reduce the number of partitions while still being able to take advantage of the changes to ensure Cassandra always reads from the local node and thus avoid the timeout, the TokenRangePartitioner will now create composite partitions with multiple token ranges (up to 60) per partition. This will reduce the number of files created by a factor of 60 reducing the number of files created from 60 - 100. Additionally, timestamp accuracy issue and batching for single case data flows have been fixed.

SR-C62475 · Issue 402873

Improved security on attachments added in Case and Pulse

Resolved in Pega Version 8.1.2

Data-Content-Image instances were getting created for attachments added in Case and Pulse. Since Data-Content-Image doesn't correspond to security once they are cached, they could be accessed by any authenticated user. To correct this, extensions have been added to stop generating Data-Content-Image while creating a pulse attachment post or case attachment.

SR-C73100 · Issue 411034

Synchronized block method added to load keystore set with RUF

Resolved in Pega Version 8.1.2

A recent enhancement allows for the SAML auth service to use a reference to an external file for the signing certificate keystore. When the keystore had the password set using a Rule-Utility-Function, rather than being static, there were intermittent login fails with the error "unable to process SAML WebSSO request1" on the screen, and the RULES logs contained thousands of entries of an error indicating "Password is wrong". It was sometimes possible to log in by starting a new browser sessions and trying again. This was an issue with the PasswordHash property being changed from a static to a non-static field: it was not thread safe, though each object got its own copy of the instance, because if two or more threads call the setPasswordHash() method on the same object, all of these threads tried to simultaneously update the passwordHash instance variable and incorrect results were seen. To correct this, the system will use a synchronized block when loading the entries into cache in the getKey() method - Caller function of KeystoreCacheImpl.java.

SR-C58241 · Issue 409217

Agent Access Group corruption resolved

Resolved in Pega Version 8.1.2

The Access Group used by agents was intermittently becoming corrupted. This was caused by a timing issue where sometimes the conclusion was built before the rulesets to the requestor were set up, resulting in the role being added to the RoleNotFound cache. To resolve this, the RoleNotFound cache has been removed so that every time a role lookup happens the system will check the database.

SR-C56652 · Issue 402945

Struts upgraded

Resolved in Pega Version 8.1.2

Apache Struts has been upgraded to version 2.5.17.

SR-C72225 · Issue 409998

Improvements to Services Tracer

Resolved in Pega Version 8.1.2

When clicking on tracer to get details of a page, a pop-up window opened up with a highlighted link (in blue color) to open the parameter page or the primary page, but clicking on either of these page names opened a blank window without any properties mapping. This was due to the underlying object missing required data because the Services related tracer events did not always have PRThread objects associated with them. The Tracer infrastructure expected the proper PRThread to be in the "ThreadContainer" but offered no option for providing the thread, and the ThreadContainer was not always populated when Services ran. To resolve this, the Tracer Event infrastructure has been refactored to allow specifying a PRThread in RULE-HTML-FRAGMENT TRACERTRACEEVENTSSCRIPTS. The constructor logic in TraceEventBaseImpl has also been modified so child classes can pass a thread instead of relying on ThreadContainer. The Node ID for tracer events will be set based on PREngineProvider instead of ThreadContainer, and the ServiceEvent Interface's methods have been updated to take pointers to PRThreads so that the tracer knows who/what is being traced. In addition, NPE protection has been added to RemoteTracerStub so Tracing Services will not crash the Tracer UI when running from eclipse / prwebpacked.

SR-C73131 · Issue 411758

SAML login rule form documentation updated to reflect usage with IDP

Resolved in Pega Version 8.1.2

SAML authentication was not working properly during login. This was traced to the assertion not being signed when SAML responses received from IDP require this, and was due to the check box under SP settings not being applied for POST binding. As a result, a local IDP configuration sent a signed response but not a signed assertion. To clarify this, the label message in the SAML rule form has been modified to read "Reject unsigned response and assertion" and the help documentation has been updated to reflect this usage.

SR-C74201 · Issue 412426

Fixed pyMemo overwriting set values with null

Resolved in Pega Version 8.1.2

The titles for correspondence and URL attachments were empty due to pyDefault setting pyMemo to "", overwriting the value that was previously set. This was caused by the Link-Object java generation code first setting the properties and later applying the DT. To fix this, the pyDefault DT will be applied for the Link-Attachment instance in activities Work-.AttachURL amd Work-.CorrAttach.

SR-C74954 · Issue 413140

Fixed column search function for Report Browser Data Explorer

Resolved in Pega Version 8.1.2

Searching/filtering for columns in the Data Explorer in the Report Browser was not filtering the tabs by the search string. This was an error caused by the unique ID changes for controls, and has been fixed by updating the getSearchTextElement() function in pega_report_events.js to use the name attribute rather than the ID attribute to identify the search bar. The tabClickCallback() has also been updated to not rely on window.event as it was causing discrepancies in Safari.

SR-C75689 · Issue 413136

restored to correct "pg empty after db.open" errors

Resolved in Pega Version 8.1.2

When opening the data page D_RepositorySettings, the error "pg empty after db.open" appeared in the logs. This was due to the data page referring to the files webwb/zchecked.gif and webwb/zchecked.gif in many sections of the data page rule form despite these files having been removed as part of a recent cleanup meant to reduce storage requirements. In order to resolve this error, the zunchecked.gif and zchecked.gif images have been added back and the error message generated in the RUF pzGetbase64encodedImagehas been improved to add the target filename: "error occurred while opening the image:webwb/zunchecked.gif"

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