SR-A18909 · Issue 235146
Strategy and data flow behavior more consistent
Resolved in Pega Version 7.2.1
Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.
SR-A18920 · Issue 235519
Corrected positioning of autocomplete popover on mobile
Resolved in Pega Version 7.2.1
When using Safari, the autocomplete popover on mobile devices was not correctly positioned. A browser check has been added, and this has been fixed.
SR-A18928 · Issue 241932
AddDays calendar logic updated
Resolved in Pega Version 7.2.1
The AddDays function in a Business Calendar was not working correctly because it did not have a default timezone. The Days RUF with 4 parameters ADDDAYS--(STRING,INT,BOOLEAN,STRING) has been set to use the GMT timezone in cases where the use business calendar parameter is sent as false.
SR-A18952 · Issue 236936
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-A18959 · Issue 236651
Corrected results display for upgraded pysearchResultWork filters
Resolved in Pega Version 7.2.1
When applying the pysearchResultWork filter on the native work objects search bar, some results were not displayed as expected after upgrade. This was caused by an error in setting the property for ad hoc cases inside a child activity, and has been fixed.
SR-A18998 · Issue 236896
Document updated for WAS JNDI dataSourceAdmin binding identifiers
Resolved in Pega Version 7.2.1
Page 80 of the Pega 7.2 Platform Upgrade Guide describes the procedure to create the JNDI binding identifiers for dual-user configuration. In that description, the String value for the following identifiers is not correct. prconfig/database/databases/PegaDATA/dataSourceAdmin prconfig/database/databases/PegaRULES/dataSourceAdmin The string value should be the "the JNDI name of the Admin data source for the data/rule schema" instead of "the schema name of your data/rules schema" The same issue is present in the Pega 7 Platform Installation Guides for WebSphere, and both documentation areas have been updated.
SR-A19075 · Issue 236452
Corrected class structure created by SOAP Integration Wizard
Resolved in Pega Version 7.2.1
An issue was found in the class structure created by the SOAP Integration wizard after upgrade. This has been fixed by updating the pyCreateGenerationRequest data transform to append servicename.
SR-A19079 · Issue 237094
Made date-time control height consistent
Resolved in Pega Version 7.2.1
Control height was inconsistent for date time controls that did not allow text entry, depending upon the control type and presentation setting. This was particularly noticeable when dynamic layout was configured with "inline double" or "inline triple". Extra padding of 2px was found in the non-text-entry control, and this has been removed to make it align to what it is in the text-entry-allowed date time.
SR-A19104 · Issue 237289
Ability added to set TTL on data sets
Resolved in Pega Version 7.2.1
An enhancement has been added to Data Flow datasets to allow setting the Time To Live (TTL) on DDS stores from the canvas. This allows setting an expiry date on cached data, which is essential when working with large streams of data.
SR-A19159 · Issue 237816
Enabled custom parameter input for PushBodyCountVar
Resolved in Pega Version 7.2.1
After importing custom markup language based on JSP 2.0 tlds and mustache templates and writing a custom HTML rule to generate JSP, the error s were generated relating to the default value of aTagPushBodyCountVar parameter. To enable the custom input, the generateCustomStart() method has been modified to use a passed-in parameter by way of aTagPushBodyCountVar instead aVisitor.getPushBodyCountVar().