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.

INC-147873 · Issue 610865

Custom header character encoding for Subject added

Resolved in Pega Version 8.5.5

Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.

INC-161645 · Issue 634639

Java Bean import updated to handling differences in Java 7 and Java 8

Resolved in Pega Version 8.5.5

The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.

INC-163292 · Issue 635839

Portlet service deprecated

Resolved in Pega Version 8.5.5

Portlet authentication services have been removed from the standard installation package. The IAC service has been restored.

SR-D84122 · Issue 547965

Added min INT comparison for BrowseByKeys

Resolved in Pega Version 8.3.3

Running the dataset with the Browse option worked as expected, but running it using BrowseByKeys operation and giving a negative value caused results to not be populated. To resolve this, a minimum INT value comparison has been added.

SR-D84099 · Issue 547824

Atmosphere library updated

Resolved in Pega Version 8.3.3

Multiple setAttribute exceptions were logged related to the Atmosphere component, indicating "The request object has been recycled and is no longer associated with this facade." Investigation showed that since the request object was destroyed, an illegalstateexception was thrown. To resolve this, the Atmosphere library has been updated to version which contains the fix for this error.

SR-D64608 · Issue 544386

Corrected filedownload extension header issue

Resolved in Pega Version 8.3.3

Filedownload header contained plain non-ascii characters which caused a security violation issue. This has been resolved by removing the filedownload header from the HTTP response when the sendfile API is used with inputstream to download a file.

SR-D60284 · Issue 550558

Delete Requestor method updated for use with CMT

Resolved in Pega Version 8.3.3

JMS MDB Listeners with Container Managed Transaction (CMT) enabled in Websphere 8.5 had global transactions fail. To initialize a JMS-MDB listener, a requestor of type APP is used. Upon the service being fully initialized, the requestor is removed by executing a delete operation followed by a COMMIT. However, in this scenario, the initialization operation is running within a CMT context and a SQLException was raised indicating that the commit was not allowed. To resolve this, the delete requestor method has been refactored to take into account the CMT context so the commit is not executed if the transaction is managed by the container.

SR-D74921 · Issue 551786

Error condition will close WebSocket connection

Resolved in Pega Version 8.3.3

An async listener has been added that will close the WebSocket connection when an error condition is encountered.

SR-D53835 · Issue 524212

Handling added for custom authentication in embedded mashup

Resolved in Pega Version 8.3.3

After embedding the Mashup gadget in an external application, at browser refresh a Cross-Origin Read Blocking (CORB) warning appeared and the gadget did not load as expected. A second refresh cleared the error. Investigation showed that when custom authentication is configured, 'use SSL' is checked in Authentication service. That meant that when the user was authenticated, the redirection was not considering the query string entered before authentication and the CORB warning was issued due to a change in response. Because there is special handling for the above use case and post-authentication redirection does not happen through the normal flow (HttpAPI), this issue has been resolved by honoring the query string stored in requestor (entered by user) while redirecting.

SR-D87605 · Issue 547295

Indexes and tables updated to improve purge query performance

Resolved in Pega Version 8.3.3

Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us