SR-A93295 · Issue 260100
Page-Copy given 'when' rule for assembler switch
Resolved in Pega Version 7.2.2
Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.
SR-A91393 · Issue 259616
Performance improvement for header/body mapping with ConnectSOAP
Resolved in Pega Version 7.2.2
Poor performance was seen when doing both header and body mappings to Parse XML rules from the Connect-SOAP ruleform. The order of the mappings has been reversed to allow for the the prPutAll call to be performed on the far smaller header mapping.
SR-A87950 · Issue 260162
SOAP over JMS works for JBoss EAP
Resolved in Pega Version 7.2.2
Previously, Connect-SOAP did not support the use of local resource references in Connect-SOAP over JMS in order to deploy on JBoss. These were supported in Connect-JMS. This has been fixed by adding support to create context with local resource references in the prAxisJMSTransport.jar.
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. .