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.
SR-A93038 · Issue 264675
Service REST requestor memory leak resolved
Resolved in Pega Version 7.2.2
The Asynchronous mode of executing Service REST acquired requestors from the pool while executing the queued jobs but did not return the requestors to the pool properly, causing a memory leak due to the requestors persisting in the system and not closing down. This has been fixed.
SR-A79631 · Issue 258414
XML generation switched to literal mode to handle encoding
Resolved in Pega Version 7.2.2
The encoded format of + was appearing in the outgoing XML stream due to the stream being generated with normal mode instead of literal. This has been changed.
SR-A79631 · Issue 257900
XML generation switched to literal mode to handle encoding
Resolved in Pega Version 7.2.2
The encoded format of + was appearing in the outgoing XML stream due to the stream being generated with normal mode instead of literal. This has been changed.
SR-A77003 · Issue 252758
GetFileAttachmentContent validates with Data-WorkAttachment- instead of File
Resolved in Pega Version 7.2.2
The SetEmailAttachments activity step 3 (java step) called a RUF pxGetFileAttachmentContent that always validated the pxObjClass with Data-WorkAttach-File. In order to support other classes of attachment, the validation process has been changed to Data-WorkAttachment- instead of File.
SR-A87728 · Issue 257771
Improved null namespace handling for WSDL import
Resolved in Pega Version 7.2.2
The SOAP Connector (Wizard) functionality in the Pega product was implemented and tested with the assumption that the WSDL document provided for consumption would contain a target namespace. Though not technically required, the great majority of WSDL documents meet this description. However, when using an imported WSDL that has no namespaces, the pxParseWSDL activity was passing a reported null namespace to some Axis2 activities that were not capable of safely consuming Definitions with null namespaces. This resulted in a "StringIndexOutOfBounds" error. To create more stability with the additional activities, WSDLParser has been updated to use QName objects themselves whenever possible and set the target namespace for the Definition to "" when it detects that it is null.