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-A18899 · Issue 236697
Operator ID screen messages localized
Resolved in Pega Version 7.2.1
Localization has been added for error messages generated in the Operator ID Screen.
SR-A18902 · Issue 237052
Updated tab generation for failed 'when'
Resolved in Pega Version 7.2.1
When visible 'whens' were configured on accordion, the content was not properly displayed below the header if the 'when' condition was false. This was caused by an error in the generation of defaultTab based on visible 'when's, and the GenerateTabbedSectionLayout RUF has been updated.
SR-A18905 · Issue 233955
OrgName error resolved for MobileOffline:Obj-Open-By-Handle
Resolved in Pega Version 7.2.1
If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.
SR-A18905 · Issue 235333
OrgName error resolved for MobileOffline:Obj-Open-By-Handle
Resolved in Pega Version 7.2.1
If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.
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.