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 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-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-A22147 · Issue 244096
Autogenerated prconfig sets v6 or v7 based on detection
Resolved in Pega Version 7.2.1
The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.
SR-A22263 · Issue 242102
Improved error reporting for PE install
Resolved in Pega Version 7.2.1
In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.
SR-A22354 · Issue 245861
prpcUtils honors 5.4 compatibility checkbox
Resolved in Pega Version 7.2.1
Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.
SR-A22672 · Issue 243213
Use Pega Log Analyzer in place of Alerts.xls Excel Template
Resolved in Pega Version 7.2.1
A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer
SR-A23134 · Issue 243870
Resolved upgrade exception caused by non-standard requestor setting
Resolved in Pega Version 7.2.1
Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.
SR-A23339 · Issue 247921
Non-versioned class rule forms updated during upgrade
Resolved in Pega Version 7.2.1
The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.
SR-A23979 · Issue 246353
Revamped help docs to clarify ServiceExport directory config
Resolved in Pega Version 7.2.1
An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.