SR-A21378 · Issue 245075
Resolved Interaction Portal unexpected close
Resolved in Pega Version 7.2.1
In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.
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-A22198 · Issue 244738
Empty access groups handling added for organizational instance
Resolved in Pega Version 7.2.1
If an unauthenticated access group was configured in the organizational instance, errors occurred because the organization instance access groups are only considered for session authorization once the user is authenticated. This will now be handled through a validate activity change in the Data-admin-organization to honor the emptiness of access groups
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.
SR-A22458 · Issue 243317
Plus '+' sign encoding corrected in connect-HTTP
Resolved in Pega Version 7.2.1
Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.
SR-A22722 · Issue 246998
pxDereferenceEndpoint Activity can be overridden by the customer
Resolved in Pega Version 7.2.1
The generic pxDereferenceEndpoint Activity that applies to the Rule-Connect-REST class was not the functionality desired by the customer, so they wanted to be able to change it, but it was set to ?Final? and couldn?t be changed. The availability of the pxDereferenceEndpoint Activity has now been set to ?Available? so that customers may override it in any RuleSet. (No logic changes have been made to this activity.)