SR-A21526 · Issue 244743
Decimal formatting kept in autocomplete
Resolved in Pega Version 7.2.1
In some installations, clicking on the auto-complete field caused the decimal format to be lost. For ex: an initial value of 21,000.00 becomes 21000.00. To correct this, the function reload of ajaxengine API has been modified to pass an extra parameter in signature of processOnBeforeSubmit function (of ui_doc_submit API ) that checks 'layouts2refresh' in the function "processOnBeforeSubmit".
SR-A21550 · Issue 241070
Removed unnecessary filtering on "&" in list item ID
Resolved in Pega Version 7.2.1
The unnecessary use of a XSS filter was causing a list item ID containing an ampersand ("&") to be encoded and displayed in a work tab as "(&"). This filter has been removed from this function.
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-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-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.
SR-A21810 · Issue 241087
PreClose updated to better handle inactive DC documents
Resolved in Pega Version 7.2.1
The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.
SR-A21905 · Issue 242013
Post value handles editing existing RTE
Resolved in Pega Version 7.2.1
On Change event, the Post Value action was not working when editing RTE that had some content already present in it. This was a harness logic issue, and has been corrected.