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 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-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-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-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-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-A19181 · Issue 240871
dropdown menu item names correctly persist after click
Resolved in Pega Version 7.2.1
Once a dropdown was selected from a number of menus in the user portal, the name of the clicked menu disappeared upon recheck. The API has been updated to read the tooltip from the icon element if it is not already present.