SR-A20634 · Issue 248378
Added handling for missing blob from external data class
Resolved in Pega Version 7.2.1
When using an external data class, an error was generated complaining of "trying to retrieve property pxInsHandle from a fully exposed table that does not contain it". This happened because the external table did not have a blob column but did have pxObjClass and pzInsKey, and handling has been added to correct this.
SR-A20832 · Issue 239823
Fixed stateless SOAP timeout after upgrade
Resolved in Pega Version 7.2.1
After upgrade, stateless SOAP services were timing out. This was caused by lost values for the Max Active, Max Idle requestors count, and Max wait time in the service package. The configurations have been modified to retain these values.
SR-A21081 · Issue 230410
Strategy rule information added to tracer
Resolved in Pega Version 7.2.1
A tracer invoked with SOAP service --> Activity --> Flow --> Interaction rule --> Strategy was only showing the the executed components in its (reversed) execution order and did not show the execution strategy path. This has been fixed.
SR-A21098 · Issue 246780
Updated row delete authorization failure error message
Resolved in Pega Version 7.2.1
The delete button at the top of the ListViewEditor was correctly configured to delete or not based on permissions, but the proper error message did not appear when the edit attempt failed. The function will now show the message "You are not authorized to delete row." in cases where there was no permission to delete the instance.
SR-A21573 · Issue 241299
Security update for Web Service Policy RampartConfig signaturePassword
Resolved in Pega Version 7.2.1
Appropriate changes have been made to support password obfuscation in signaturePassword and userPassword elements of RampartConfig elements configured in Ws-Policy rule form.
SR-A21597 · Issue 241378
Request Only' I/O timeouts updated for Connect HTTP
Resolved in Pega Version 7.2.1
The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.
SR-A21792 · Issue 242548
Saver.addBatch updated to log exception details
Resolved in Pega Version 7.2.1
To improve diagnostics, an SQL exception in the Saver class will log the actual exception instead of a null pointer.
SR-A21935 · Issue 247142
Corrected data page Lookup logic
Resolved in Pega Version 7.2.1
While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.
SR-A22152 · Issue 247716
Report Def Filter using .pxObjClass returns all results
Resolved in Pega Version 7.2.1
Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.
SR-A22200 · Issue 241230
Bulk actions filters refresh corrected
Resolved in Pega Version 7.2.1
The values entered into the right side column of the bulk processing filters were not getting submitted to the clipboard when default filter conditions were changed. The refresh action has been updated to correct this.