SR-A21017 · Issue 239317
Parameter label mismatch corrected for import
Resolved in Pega Version 7.2.1
During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.
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-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-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-A22816 · Issue 246151
Message clearing CME error fixed
Resolved in Pega Version 7.2.1
A Concurrent Modification Exception error as thrown in logs when navigating to from one row to another row in tree grid due to a data page being loaded while trying to clear messages in a page. This has been resolved by disabling auto populate while in the process of clearing messages in a page.
SR-A22933 · Issue 241566
Check added to resolve Google Chrome-based value localization error
Resolved in Pega Version 7.2.1
A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.