SR-A21588 · Issue 241928
Name retrieval updated for node sub-units
Resolved in Pega Version 7.2.1
A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.
SR-A21595 · Issue 240889
Custom height settings retained for progress bars
Resolved in Pega Version 7.2.1
After upgrade, the settings contained in the final rule pzjquery_ui_progressbar_dotluv CSS were overriding custom height settings for progress bars. The code has been updated to ensure custom settings are retained.
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.
SR-A21613 · Issue 241399
Upgrade order modified for in-place schema migration
Resolved in Pega Version 7.2.1
An in-place update of a split-schema was generating SQL exceptions. Two issues were found: For the pr_index_circumstance_def table there was a bit column type which was not anticipated, and as a result the constraints/indexes were not detected as being already installed and the application of the generated DDL failed when it tried to create them. The secondary issue was that the DDL generated by the update script was sorted so that all of the drops happened first, causing a situation where the pr_page_store_PK was trying to be dropped at a point where it did not exist. The resolution is to issue all drops first to avoid the dependency issue, then let the Schema Manager determine order so it performs the rule schema updates first and then performs the data schema updates during in-place upgrades.
SR-A21629 · Issue 243799
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index,Associations,Sub Report,Functions and Embedded Properties.
SR-A21636 · Issue 240162
Fixed auto-complete use in iPhone Opportunity creation
Resolved in Pega Version 7.2.1
Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.
SR-A21636 · Issue 241236
Fixed auto-complete use in iPhone Opportunity creation
Resolved in Pega Version 7.2.1
Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.
SR-A21703 · Issue 241076
Cross-browser checks added for disabled checkboxes
Resolved in Pega Version 7.2.1
The Checkbox Caption was not properly not disabled on Microsoft Internet Explorer when the checkbox was disabled due to a missing definition for the parent element. Extra condition have been added to find the disabled value of radiobutton and checkboxes regardless of browser.
SR-A21705 · Issue 243428
Corrected unexpected scroll after smartinfo
Resolved in Pega Version 7.2.1
After a smartinfo box is shown for a particular column in a repeat grid, hovering on the column caused the mouse indicator to go to the bottom of the section, i.e. the screen goes down even when not scrolled down. This was caused by a focus issue, and has been corrected.
SR-A21741 · Issue 248725
Fixed drilldowns and filtering with encrypted property
Resolved in Pega Version 7.2.1
After encryption of a property, filtering and drill down reports stopped working. "TAB" space is added as first character along with encryption data to store a textencrypt property type in the database, but while performing the drill down the TAB key is not appended. Instead "/t" character is added which does not fetch the results. To fix this, the JavaScript has been modified to ensure "\t" isn't added so drill down activity will get the proper results.