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.

INC-190384 · Issue 676573

URL validation updated to handle custom token endpoints

Resolved in Pega Version 8.7

While saving an authentication profile with OAuth details, validation was failing for a valid URL given in the access token endpoint and revoke token endpoint fields. This was traced to the use of the Apache URL validator, which considered some domains to be invalid. To resolve this, the urlvalidator constructor has been updated to include a custom RegexValidator for access token and refresh token URLs.

INC-167704 · Issue 671630

Email timing updated to ensure content captured

Resolved in Pega Version 8.7

Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.

INC-149375 · Issue 607831

Adjusted email listener behavior for authentication failures

Resolved in Pega Version 8.4.4

After upgrade, email listeners were not staying up during connection outages. This was traced to the handling of authentication failures when trying to reconnect, and has been resolved by changing the disconnected listener state to sleeping and raising an alert for authentication failures.

INC-143193 · Issue 595938

Handling added for UI overlap issue

Resolved in Pega Version 8.4.4

Elements of the window "Test Case Record Configuration" were shifted into one another when the Application name was too long that it overlapped with the other UI Elements. This has been resolved by adding a style sheet with overflow hidden.

INC-166995 · Issue 642440

DeleteDocumentPg added to allow list

Resolved in Pega Version 8.7

During performance testing with CSRF settings enabled, a '403 Forbidden' error was seen in the network trace when FinishAssignment called pyActivity=pyDeleteDocument on close action. This has been resolved by adding pyDeleteDocumentPg to the list of allowed activities.

INC-190417 · Issue 675213

ModifiedGetEmailPosts data transform to better handle very large messages

Resolved in Pega Version 8.7

Blank emails were seen when the message was over 4000 characters. This was traced to an issue with initializing param.index2, and has been resolved by modifying the pxGetEmailPosts data transform to take param.index2=0 out of the loop for large emails.

INC-163043 · Issue 645390

PEGA SOAP Service MTOM attachment handling updated

Resolved in Pega Version 8.7

After configuring a PEGA SOAP service with the Enable MTOM checked, sending a SOAP request with attachment to the service returned an invalid request error stating "Value of content length header is greater than zero - [762], but this request has empty POST". Investigation showed that when the input request reached the getPostBytes method and inputstream tried to read it, there were no available bytes and end of file was detected. This was due to the inputstream having already been read in getMultiPartSOAPHandler() method in FileUploadHandler class. To resolve this, the system will update an 'if' condition in getPostBytes method to skip reading the request attachment when contentType is "multipart/related".

INC-194433 · Issue 679630

Key Value Store handling revised for greater backwards compatibility

Resolved in Pega Version 8.7

Previous optimization work done to reduce the size of the "nm" field when the hierarchy string is empty resulted in some Key Value Store records not being read from older systems during update. This has been corrected.

INC-168414 · Issue 641036

Web Mashup works from nested iframe

Resolved in Pega Version 8.7

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

INC-176971 · Issue 658300

Web Mashup works from nested iframe

Resolved in Pega Version 8.7

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

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