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-A23694 · Issue 246996
Timeliness functions modified to return 0 in place of NULL
Resolved in Pega Version 7.2.1
The "Timeliness" function aliases returned NULL for all the CASE statements that returned false, but NULL value using the AVERAGE summarize function in a report definition returned an incorrect result. The following Function Aliases have been updated to return a 0 instead of NULL when the result is false: - pxSLAAgeByClassTimeliness - pxSLAAgeTimeliness - pxSLAHistoryTimeliness - pxSLAAssignTimeliness
SR-A9921 · Issue 222554
Updated PDF generation to minimize font conversion temp file creation
Resolved in Pega Version 7.2.1
When HTML containing Chinese characters is converted to PDF using HTMLtoPDF, files like "+~JF690731093475584931.tmp" were created in the temp folder for each conversion and were not cleared after PDF is generated. This has been fixed by modifying the PDF utility to create only one fonts.properties file.
SR-A13187 · Issue 226047
JSON mapping performance enhanced
Resolved in Pega Version 7.2.1
JSON mapping performance has been enhanced with the addition of a native JSON property cache along with the introduction of a DSS to skip all unnecessary intensive checks if the JSON node name is found to be valid. This will be handled through a DSS JSON/useNativeAPI which when set uses adoptJSONObject/adoptJSONArray() as the API for inbound JSON parsing. Please note that if the DSS is set, homogeneous arrays are only supported with valuelist configuration in connectors. Heterogeneous arrays are not supported when DSS is set.
SR-A18694 · Issue 246976
Method changed for locating Word Templates folder
Resolved in Pega Version 7.2.1
The method used to obtain the Word templates folder always lower cases the folder path, but this poses a problem for the Turkish locale when the path contains capital I with no dot. Turkish has two variants of I - one with dot and one without dot. To resolve this, the Office templates folder path will be determined based on a combination of certain registry keys dependent on the Word version.
SR-A16938 · Issue 232832
Hardcoded DDL date replaced with dynamic string for Postgres compatibility
Resolved in Pega Version 7.2.1
The PostgreSQL DDL generator for install and upgrade in PRPC 7.1.9 created a PL/pgSQL containing the direct date value "01/01/1990". In some versions of Postgres 9.3, this caused a datestyle mismatch execution error when datestyle was set to "iso, ymd" on the postgresql.conf side. This has been resolved by replacing the hardcoded date value with a to_date function that uses an appropriate format string.
SR-A16406 · Issue 237367
Validation handling added for complex criteria values
Resolved in Pega Version 7.2.1
Incorrect validations were appearing when trying to save a List View rule with a criteria value that uses a property embedded in the pxResults page of a declare page in the Value field of the Content tab and that listed the top level declare page in Pages & Classes. This was due to the unusual structure of this referred property not automatically having the necessary links to retrieve the necessary pages and classes, and handling has been added for this special scenario.
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-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-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.