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-A18813 · Issue 236196
Support added for auto-generated numeric IDENTITY columns in RD
Resolved in Pega Version 7.2.1
Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.
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-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-A19167 · Issue 242469
Modified decision table handling for Connect-REST
Resolved in Pega Version 7.2.1
Authorization problems in opening the pyOutboundIdentifierDecoder decision table were causing Connect-REST failures. While it is recommended to only initialize the decision tables for legacy mapping DSS(json/legacyMapping) and not initialize the decision tables for normal JSON mapping, ServiceHelper and RulegeneratorREST have been updated with a check to properly handle the presence of decision tables.
SR-A19172 · Issue 236714
Managed unique constraint violation error for BIX
Resolved in Pega Version 7.2.1
When running multiple extracts using agents and pxExtractDataWithArgs at the same time, a unique constraint violation error was produced in the logs. This occurred when the extracts had the same time stamp down to the millisecond and an entry is added to the pr_log table when each extract starts. The pzInsKey for two extracts that run at the same time was identical, thus leading to this error. To resolve this, the thread name will be appended when the extract is run from an activity.
SR-A19281 · Issue 235998
Dialogue handling updated for WS-Security Profile password
Resolved in Pega Version 7.2.1
The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.
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-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.