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-C65438 · Issue 406709

Added SAML parameter page generation for local use to bypass null auth object

Resolved in Pega Version 8.2

After defining any step which used parameters in the Post authentication activity of a SAML authentication service, the authentication failed with a java.lang.NullPointerException at com.pega.pegarules.session.internal.mgmt.Executable.putParamValue(Executable.java:3030). This was traced to local logic inserted to iterate through the SAML attributes that used a null parameter page. To resolve this, code has been inserted that will generate a new parameter page for the iteration rather than getting it from the authentication object.

SR-C69302 · Issue 407177

Support added for local datacenter only keyspaces for Cassandra

Resolved in Pega Version 8.2

In order to support multi-datacenter system (one Pega system) that spans two data centers but avoids the latency of attempting to connect from a node in data center 1 to a Cassandra node in data center 2, an enhancement has been added by way of the system setting dnode/cassandra_local_datacenter_keyspaces which allows specifying only local datacenter keyspaces as comma separated string. The default behavior is not changed.

SR-C71290 · Issue 410122

Removed automated cleanup of old DSS entries to resolve memory issue

Resolved in Pega Version 8.2

VBD was issuing an expensive query while attempting to clean up old DSS entries. The old entries were dynamically created with node ID as part of the setting key (vbd/pulse/{nodeid}, and vbd/cluster/{nodeid}). The cleanup logic attempts to get the list of all matching keys to delete by iterating the list of system settings and grabbing the ones that match these patterns. On some systems, there are enough system settings in the DB that it resulted in a memory issue. To avoid this issue, the automated cleanup process has been removed.

SR-C75689 · Issue 413135

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

Resolved in Pega Version 8.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".

SR-C57879 · Issue 406004

Updated parameter handling for SECU0001 alert for accuracy

Resolved in Pega Version 8.2

In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e, during inputProcessing where the current activity had not yet been set to the requestor state and therefore the currentactivity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.

SR-C66114 · Issue 408081

Resolved pg empty error after db.open and improved error message

Resolved in Pega Version 8.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".

SR-C71253 · Issue 409091

Resolved issue with PRAuth handoff to SAMLAuth

Resolved in Pega Version 8.2

When attempting to access a Portal with PRAuth, a null pointer exception was being generated instead of the system redirecting to SAMLAuth. This was traced to httpAPI.getAccessGroup() returning null when a DSS authentication/redirectguests/default was set to true, and has been resolved by fetching the access group from the thread instead of the HttpAPI.

SR-C68750 · Issue 402364

PEGA0066 alert sends data needed for MyAlerts use

Resolved in Pega Version 8.2

In order to facilitate the use of products like the MyAlerts application, the following data will be provided to PDC from PEGA0066 alerts to generate proper diagnostics information and propose solutions for issues with mobile client connections:pxClientErrorCode pxDeviceManufacturer pxDeviceModel pxOSName pxOSVersion pxHybridClientVersion pxInstallationId pxSynchronizationId pxSynchronizationTimestamp pxEnd The whitelisted parameters can be seen on the Alert Summary page in PDC.

SR-C51744 · Issue 406708

Corrected SAML SSO logout error

Resolved in Pega Version 8.2

When performing a SAML SSO Logout, an error appeared indicating some artifacts were missing. This was traced to an incorrect NameQualifier being generated with IDP in the logoff request, and has been fixed by modifying the code to include an SPNameQualifier attribute for the NameID element in the logout request. Namespace has been added for logout requests at the parent level instead adding it at each node element.

SR-C70146 · Issue 407966

Corrected SAML SSO logout error

Resolved in Pega Version 8.2

When performing a SAML SSO Logout, an error appeared indicating some artifacts were missing. This was traced to an incorrect NameQualifier being generated with IDP in the logoff request, and has been fixed by modifying the code to include an SPNameQualifier attribute for the NameID element in the logout request. Namespace has been added for logout requests at the parent level instead adding it at each node element.

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