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-A102790 · Issue 271337

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A95044 · Issue 269629

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A95044 · Issue 270120

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A96815 · Issue 266585

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A96815 · Issue 269518

Max_HostConnections accepts DSS

Resolved in Pega Version 7.2.2

Previously, the connection manager was hard-coded to default to two connections. In order to allow for more flexibility, the Instantiated Connection manger has been updated to allow DSS to to set the number of Max_HostConnections.

SR-A88158 · Issue 257566

Improved REST/JSON mapping response

Resolved in Pega Version 7.2.2

Slow performance was seen when mapping REST response JSON when the Properties involved were not created by the REST Integration Wizard, or when the data in the response has keys that did not match qualifiers/properties. This was due to a large amount of redundant database lookups occurring during the mapping process, and this process has been tuned for better performance.

SR-A98376 · Issue 265578

SET-COOKIE enhancement allows mapping to property value

Resolved in Pega Version 7.2.2

Support has been added for REST service response headers to be configured with multiple SET-COOKIE headers where the cookie can be mapped to a property value populated with the standard cookie format along with other attributes like name, path, expiry etc. .

SR-A92260 · Issue 259866

GRS supported for JMS Listener ID

Resolved in Pega Version 7.2.2

Support has been added to use a global resource reference setting for the JMS listener Requestor ID field.

SR-A76100 · Issue 254315

GRS supported for JNDI settings in JMS Listener

Resolved in Pega Version 7.2.2

Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.

SR-A88782 · Issue 263961

GRS supported for JNDI settings in JMS Listener

Resolved in Pega Version 7.2.2

Support has been added to use global resource reference settings for the JNDI server field and the initial context factory field value in the JMS listener during test connections.

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