SR-A19351 · Issue 238052
Caching added to improve login speed
Resolved in Pega Version 7.2.1
In order to improve login performance, caching has been added for the following classes accessed from the database on every login: DATA-ADMIN-SECURITY-AUTHSERVICE DATA-BROADCAST DATA-ADMIN-SECURITY-KEYSTORE
SR-A19355 · Issue 235876
Landing page Header correctly displays VBD Planner
Resolved in Pega Version 7.2.1
The Pega Marketing portal header was overlapped by the VBD Planner header, creating problems accessing the buttons on the portal header. The newly developed VBD Planner client, running as a control, did not take portal layout into consideration, and the header has been adjusted so the portal header is exposed properly.
SR-A19363 · Issue 243522
Edit validate does not clear date field on error
Resolved in Pega Version 7.2.1
When submitting a flow action, the edit validate rule fired and caught the error, but then the date field value was unexpectedly cleared. The resetDatetimeHidden API has been modified to resolve this.
SR-A19406 · Issue 236911
Pega0031 debug tool stack trace updated
Resolved in Pega Version 7.2.1
When an activity was run which performed a show-html/show-stream twice, the first PEGA0031 alert was raised with no stack trace. The second instance of show-html/show-stream would log the PEGA0031 alert along with the stack trace of this interaction, and the first would not be seen. This was caused by the improper clearance of the pxHTMLStream property on the thread page at the end of the HTTP interaction and has been fixed.
SR-A19421 · Issue 237693
Corrected tab group issue when '&' present in tab title
Resolved in Pega Version 7.2.1
Depending on the browser, the drop down function to view the list of tabs was performing inconsistently if '&' was present in a tab title. This was an issue with the character not being encoded, and the dynamic container handling has been updated to correctly display the tab with '&' and all tabs behind it.
SR-A19464 · Issue 237977
Improved null value handling for navigation rule
Resolved in Pega Version 7.2.1
In cases where no pyValue property was given in the navigation rule, the preactivity of a navigation rule (scenario: item list & action:create work) was always passing the first parameter value to the rest of the parameters. This was due to missing handling for a null value; a check was added, but the handling has been further expanded to reset the string holding the pyvalue of pre activity params.
SR-A19478 · Issue 242241
Fixed truncation in tooltips text
Resolved in Pega Version 7.2.1
When the title attribute for an expand/collapse header was specified with apostrophes and single quotes, the text which displayed in the tooltip message was truncated at the punctuation. For all the tooltips that get displayed, if the text contains an apostrophe (e.g. "Today's Work"), the tooltip truncates the text at the apostrophe (e.g. "Today"). This did not occur very often in English, but was a much more obvious problem in other languages. For example, the word for "today" in French is "Aujourd'hui", so on tooltips, this was truncated to "Aujourd". To fix this, code has been added to escape the special characters for the tooltip messages.
SR-A19495 · Issue 237132
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-A19503 · Issue 240455
Added configuration field for SOAP response without credentials
Resolved in Pega Version 7.2.1
The system was having difficulty processing a SOAP response if the service did not return an authentication header in the SOAP envelope. This happened when connecting to a SOAP service configured with ws-security username policy which sends only the username but not the password in the SOAP envelope. To correct this, the setting options.setProperty(com.pega.apache.ws.security.handler.WSHandlerConstants.ALLOW_USERNAMETOKEN_NOPASSWORD, "true"); has been added; this option is specific to a connector and is available on the ws-security profile rule form to configure the setting based on the site's SOAP service username policy.
SR-A19512 · Issue 238622
Standardized date time used for memo history compare
Resolved in Pega Version 7.2.1
History compare displayed unexpected results for the pxSaveDateTime for a Rule-Application record when a memo was added and then it was compared to another record in the history log. The comparison logic was not looking at the save time of the memo, but rather the save time of the rule itself, resulting in the mismatch. This has been resolved.