SR-A95686 · Issue 262970
Check added to prevent deletion of needed application
Resolved in Pega Version 7.2.2
If the browser Requestor Type rule for the system referenced an access group that requires an application that was recently deleted, developers were able to continue working, but once logged out it was not possible to log in again and an error related to authentication appeared. To prevent this, validation has been added to ensure that no applications are deleted that are utilized by access groups that are referenced by BROWSER Requester Type rules.
SR-A99040 · Issue 270067
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-A87913 · Issue 256339
Operator can add Favorites regardless of locale
Resolved in Pega Version 7.2.2
It was not possible to add Favorites to the Operator Profile if the operator was logged on with a locale other than English. This was traced to the handling of pyAddAsFavoriteTo as a text property with table type as local list: the favorites dropdown is sourced from a data transform (pzMyFavoritesPreLoad) which gives localized values of the dropdown items, but the corresponding property pyAddAsFavoriteTo was being sourced from a local list and failed the localization comparison. To resolve this, pzMyFavoritesPreLoad DT has been modified to retain both localized value and actual value so pzMyFavorites section will properly localize without losing the original property value.
SR-A77514 · Issue 253486
@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-A80686 · Issue 256090
StartCase correctly searches parent cases
Resolved in Pega Version 7.2.2
Test cases created for pyStartCase flow are saved with insname as pyStartCase, but during "record from assignment" parent test cases are searched with the flow name where the assignment is present. That resulted in no parent test cases being returned. To fix this, the activity has been modified so the parent test cases are searched to pass "pyStartCase" as a Top Level Flow Name when using "record from assignment" from pyStartCase flow.
SR-A95291 · Issue 273667
Deprecated Access Groups documentation updated
Resolved in Pega Version 7.2.2
The documentation lead-in to the Deprecated Access Groups section has been updated for clarification: These access groups are retained after upgrades to support applications created in Version 4.2 and Version 5.X systems. They are deprecated and not recommended for continued use. These access groups appear only on systems that are upgraded from PRPC 6.x or earlier.
SR-A88270 · Issue 261496
Memo text picks up translated value
Resolved in Pega Version 7.2.2
The localized text was not being correctly picked up when trying to capture the history of an instance using pyTrackSecurityChanges trigger and DataTransform and referencing the Pagelist values in DataTransform. To resolve this, the RUF addMemoForSecurityChangeTracking has been updated to better handle page/page-list property, however, it is strictly one level nesting (parent page > child page). Embedded properties nested more than 1 level would not be handled by this code.
SR-A89757 · Issue 258597
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-A100376 · Issue 271177
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.
SR-A100376 · Issue 271369
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.