SR-A100572 · Issue 270091
getThread API respects Never create flag
Resolved in Pega Version 7.2.2
When setting initialization/persistrequestor = Never, a new thread was created on every getThread call where thread validation checks were not done. This allowed vulnerable thread names that were not checked and allowed to pass through. This was due to the getThread API not respecting the aCreateIfNotInDB flag, and has been fixed.
SR-A93593 · Issue 260733
Cross Origin mashup request fixed for Microsoft Internet Explorer /Safari
Resolved in Pega Version 7.2.2
When the mashup code hosted in domain1 was trying to access the PRPC content hosted in domain2, it failed when using Microsoft Internet Explorer and Safari but worked in Google Chrome. For a HTTP request whose response status is 303, the response headers given using Dynamic system setting "http/responseHeaders" were not being sent. This has been corrected.
SR-A102433 · Issue 271744
Optional warn forced for PersistSystemInfo
Resolved in Pega Version 7.2.2
When using com.pega.pegarules.monitor.internal.state.DatabaseInfoHandler.persistAllCurrentComponents(PRThread), errors are logged and the flow continues. As this may cause customer logs to fill up with errors, the function has been changed to warn forced and stacktrace will only be displayed if debug is enabled.
SR-A100923 · Issue 269979
Property null check added to TrackSecurityChanges
Resolved in Pega Version 7.2.2
When using the out-of-the-box TrackSecurityChangesLogic activity in an application to track the property changes, an Null Pointer Error was generated when saving the property. This was due to a missing null check for the property, and has been fixed.
SR-A100816 · Issue 268476
MinimumAgeForProcessing honored when requeuing Broken-Process
Resolved in Pega Version 7.2.2
When using the Requeue feature from SMA, queue items were not honoring the existing (previously used) value of pyMinimumAgeForProcessing, instead setting the value as -1 so, all attempts were happening immediately. This was an issue with the Repair API in QueueManagerImpl not honoring minimumAgeForProcessing if MinimumDateForProcessing already existed in the queue item, and has been fixed.
SR-A19800 · Issue 253412
Switching fixed for interaction type threads
Resolved in Pega Version 7.2.2
When working with interactions in the portal, switching the threads from one interaction to another to perform some action and then clicking on the interaction type to return to the original thread generated the error "Failed to find instance @baseclass.Perform of type Rule-HTML-Harness". This was caused by the system not checking to see if the top level page was already open when returning, and has been fixed.
SR-A76645 · Issue 253467
Added variable catch to IAC validation
Resolved in Pega Version 7.2.2
Whenever there was a pattern of aaa/$aaa/$aaa for thread name (more than one occurrence of delimiter "/$" ) in IAC, the request failed when submitting the modal dialog with the error "There has been an issue; please consult your system administrator". This was due to the intended validation for the IAC first request (does not have Access group) being performed on every request. To correct this, a catch has been added to ensure the validation happens only for a request without access group and with appname.
SR-A94493 · Issue 262430
JSON error resolved for empty section render
Resolved in Pega Version 7.2.2
While rendering a section, a JSON error was thrown in the console that prevented all click actions on the screen. Analysis showed this was due to an extra comma that was present when the page doesn't have any values, and has been fixed with a check that will only add the comma after DataPage scope after confirming the page is not empty.
SR-A96096 · Issue 264802
Tenant hash preserved for SOAP to accommodate load balancer SSL termination
Resolved in Pega Version 7.2.2
With Cloud 2.1, there was a need to set prconfig settings in order to accommodate SSL termination at the load balancer side, but the SOAP messages between a client (tenant) and PDC were having their tenant hash stripped by the engine. This was due to SOAP requests made to a specific Tenant by a monitored node (client) of PDC(MT) being redirected to a Shared tenant in PDC. To resolve this, even when "initialization/contextrewriteenabled" is set to true, the value for "pxReqPathInfo" will be set by HttpRequestMapper.buildRequestorDataFromHttpRequest() in the Map returned by it.
SR-A87407 · Issue 265098
XML stream assembly handles parentheses
Resolved in Pega Version 7.2.2
XML stream assembly was not properly handling parentheses; this has been fixed.