SR-A21487 · Issue 241066
Corrected GRANT generation for DB2 users
Resolved in Pega Version 7.2.1
When importing a RAP with a view into a DB2 10.1 LUW database, the GRANT statements were failing because of invalid syntax and the view creation was not executed. This was caused by the user name not being properly appended to the grant statement generation for DB2 users, and has been fixed.
SR-A21501 · Issue 242372
Search improved for case tags
Resolved in Pega Version 7.2.1
Search functionality for tags in cases was updated from Lucene search to elastic search, but the change class context was not properly set in all cases. It is now updated to run in workgroup as well as class.
SR-A21514 · Issue 242070
DateTime calendar displays time in report filter view
Resolved in Pega Version 7.2.1
The DateTime calendar was not displaying time in the pre-report filter screen while the same calendar displayed both date and time in the report viewer screen. This has been corrected.
SR-A21526 · Issue 244743
Decimal formatting kept in autocomplete
Resolved in Pega Version 7.2.1
In some installations, clicking on the auto-complete field caused the decimal format to be lost. For ex: an initial value of 21,000.00 becomes 21000.00. To correct this, the function reload of ajaxengine API has been modified to pass an extra parameter in signature of processOnBeforeSubmit function (of ui_doc_submit API ) that checks 'layouts2refresh' in the function "processOnBeforeSubmit".
SR-A21550 · Issue 241070
Removed unnecessary filtering on "&" in list item ID
Resolved in Pega Version 7.2.1
The unnecessary use of a XSS filter was causing a list item ID containing an ampersand ("&") to be encoded and displayed in a work tab as "(&"). This filter has been removed from this function.
SR-A21569 · Issue 242079
Corrected persistence of deleted requirements links with multiple actors
Resolved in Pega Version 7.2.1
When checking in a specification with more than one actor specified on it, deleted requirement links re-appeared after the rule was closed and re-opened. This was due to an unnecessary section refresh, which has been removed.
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-A21588 · Issue 241928
Name retrieval updated for node sub-units
Resolved in Pega Version 7.2.1
A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.
SR-A21595 · Issue 240889
Custom height settings retained for progress bars
Resolved in Pega Version 7.2.1
After upgrade, the settings contained in the final rule pzjquery_ui_progressbar_dotluv CSS were overriding custom height settings for progress bars. The code has been updated to ensure custom settings are retained.
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.