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-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 231480
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-A21830 · Issue 244836
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
SR-A21830 · Issue 246779
Improvements made to History Compare
Resolved in Pega Version 7.2.1
The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.
SR-A22067 · Issue 243520
Corrected passing Current Parameter Page in Collections
Resolved in Pega Version 7.2.1
When attempting to call a rule in a Response Actions entry on a Collection flow, the configuration panel would not submit when "Pass Current Parameter Page" was checked and there were required parameters on the rule being called. This was traced to an unneeded validation being performed, and has been resolved.
SR-A22090 · Issue 243573
Activity method loading works with encryption
Resolved in Pega Version 7.2.1
Activity method loading was not working with URLEncryption enabled. This was a problem with populating the parameters with the encryption function in use, and has been fixed by making use of SafeURL to prepare the querystring of the URL.
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-A22234 · Issue 243871
Resolved CME error for case withdrawal
Resolved in Pega Version 7.2.1
When withdrawing a case, pxForceCaseClose was throwing Concurrent Modification Exception. This has been fixed.
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.