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-103429 · Issue 136984

Rule-Service-Java authentication in a stateless session re-enabled

Resolved in Pega Version 7.1.7

When exposing Rule-Service-Java through a service package, a proxy jar file is created. If the 'Requires Authentication' option was checked on the service package, the generated java did not contain the required code to pass through the username/password and authentication failed. This method of passing credentials via proxy method parameters was previously withdrawn for the stateless processing mode, but the java code has been reinstated to enable authentication for a stateless session if this method is desired.

SR-108346 · Issue 166436

Corrected purging for History and Attachments

Resolved in Pega Version 7.1.7

A problem was found with purging the History and Attachments for cover and folder items. This was traced to history tables using datetime columns as key properties: many databases round these values to less precision than PRPC uses, and the keys did not match. The purgeitems function has been updated to delete the instance specifically and bypass recalculating the InsKey.

SR-111889 · Issue 157259

Some SOAP calls with WSTRUST generated exceptions in customized environments

Resolved in Pega Version 7.1.7

In some heavily customized environments, a SOAP connect call using the WSTRUST element generated an exception. This was due to uneven handling of the local custom elements in the SOAP STS request, and has been resolved by adding a method to pick up all custom code based on the tag in policy document.

SR-112535 · Issue 164337

Portal rendering errors under z/OS

Resolved in Pega Version 7.1.7

Under z/OS, new installations were missing the login icon and the portal was not rendered correctly. This did not impact system performance. The problem was traced to an index setting in the DDL generation, and has been fixed.

SR-113384 · Issue 162788

Explicit schema mapping could cause migration script errors

Resolved in Pega Version 7.1.7

While running the migration script, the presence of a custom rule table that explicitly mapped the Data-Admin-DB-Table schema could cause the script to fail. This was caused by the GRANT statements in the SQL script not having the proper assignment for the user name with the "USER" keyword; a group name that is the same as the user name that we are trying to GRANT rights to was ambiguous. The workaround was to temporarily map the custom table to an empty schema, then manually copy this table to the RULES schema afterward, but this issue has been addressed by updating how privileges are granted for the table, procedure and function elements in a split schema.

SR-113703 · Issue 163067

Custom root certificate support added to Connect-REST

Resolved in Pega Version 7.1.7

Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.

SR-115779 · Issue 167907

Custom root certificate support added to Connect-REST

Resolved in Pega Version 7.1.7

Configuring a Connect-HTTP/REST rule that connects to a server using custom root certificates caused the error "javax.net.ssl.SSLPeerUnverifiedException". To remedy this, REST / HTTP now supports the merging of custom and jvm trust stores and runtime support for SSL in REST connectors.

SR-114109 · Issue 164313

Corrected Connect-Java ability to run in parallel

Resolved in Pega Version 7.1.7

Using connect-java in RunInParallel mode was failing with the error "couldn't resolve the required java object". This was found to be an error in copying objects from the primary page in RunInParallel mode that did not properly retain the references for the Java wrapper objects. There was a workaround to use the "If possible, use a valid object handle" option, but this error has been fixed.

SR-114438 · Issue 168461

Inbound mail processing for work creation refactored for subject line checking

Resolved in Pega Version 7.1.7

Some issues were found with the handling of inbound emails for work object creation. The activity CreateAndManageWorkFromEmail was incorrectly checking for an email subject line pre-condition and creating a new work object if the condition was not met. The CreateAndManageWorkFromEmail function has been refactored to correct this.

SR-114575 · Issue 168078

Search criteria passed to Report Definition

Resolved in Pega Version 7.1.7

The values entered in search criteria fields were not being passed to report definition, so the results were not shown in the Grid layout report. This was caused by an additional check on the classname of the parameters page while resolving filter values which are parameters, and has been resolved.

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