SR-A99040 · Issue 268520
Cleared email field in FieldMarketer campaign remains blank
Resolved in Pega Version 7.2.2
If the Email field of a FieldMarketer campaign was cleared and saved, closing and then reopening the session filled the email field with the Operator ID, which is not a valid email address. This was traced to Operator Email always defaulting to OperatorID if empty, and the activity has now been modified to not set the email field if empty.
SR-A88491 · Issue 252281
Localization added for "Summary for" and "Edit Dashboard"
Resolved in Pega Version 7.2.2
Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.
SR-A88491 · Issue 240995
Localization added for "Summary for" and "Edit Dashboard"
Resolved in Pega Version 7.2.2
Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.
SR-A88491 · Issue 251537
Localization added for "Summary for" and "Edit Dashboard"
Resolved in Pega Version 7.2.2
Localization has been added for the formatted text in pyUserDashboardHeaderLeft, which presents "Summary for" on the Manager Portal, and for the caption fields on the "Edit Dashboard" menu.
SR-A77514 · Issue 239717
@baseclass!pyMemo has been made available
Resolved in Pega Version 7.2.2
Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.
SR-A87928 · Issue 255259
Fixed cataloging for v5 hotfixes
Resolved in Pega Version 7.2.2
Recent modifications to obtaining catalogs for supporting additional products (i.e. frameworks) caused a regression in being able to check dependency information on v5 hotfixes, preventing DL files from being created for them. This has been fixed.
SR-B5634 · Issue 274715
Stack frame handling made more robust
Resolved in Pega Version 7.2.2
Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.
SR-A75927 · Issue 252170
OnChange event fires correctly for pyAddress
Resolved in Pega Version 7.2.2
Using a pyLocationFieldOptional section that included pyAddress to get the real time address associated with the map would correctly update the address when the map marker was moved, but the OnChange event associated with the text box did not fire. This was due to the change event waiting until focus & blur events are dispatched on the referenced text input field. To correct this, the touch devices check in setAddressProperty function in pzpega_addressmap.js has been removed so that focus is fired and blurred after the change event is triggered. In addressmap js , the setAddressProperty function will dispatch change after focus & later will dispatch blur.
SR-A89757 · Issue 258099
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.
SR-A99155 · Issue 253246
Mobile dirty page handling corrected
Resolved in Pega Version 7.2.2
When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.