SR-A98193 · Issue 266453
Black listed properties properly excluded from compare results
Resolved in Pega Version 7.2.2
After upgrade, properties that were included in the black list were showing up in the compare results. This was an error in determining which declaratives would be disabled when calling the applyIgnoreMap method directly, and has been fixed by removing declarative enabling / disabling from applyIgnoreMap, and moving them into the code for PageCompare.
SR-A77163 · Issue 252819
Associated rules locking fixed for PFM offer flow
Resolved in Pega Version 7.2.2
After using the "Release lock" option in the action menu for a flow (or offer rule from the Pega Field Marketing application), it was not possible to check-out the flow or offer and an error message appeared indicating another user had the record checked out even when that user did not see it in their own checkouts. This was traced to the "Release lock" feature not appropriately releasing locks on the associated rules, in this case, the binary that is generated in the background for the flow or offer. It was possible to work around this by opening the binary using the "Open stored flow image" option and then selecting "Release lock" in order to release the lock on the image, but the locking has now been corrected.
SR-A99969 · Issue 266109
Ruleset listing works without enabling UDFs
Resolved in Pega Version 7.2.2
All core Designer Studio features and Pega frameworks / applications are supposed to work without dependency on pr_read* UDFs, but an issue was found with attempting to list rulesets without enabling UDFs. This was due to the Designer Studio features used to list instances of a rule class performing behind the scenes filtering to exclude rules with pyMethodStatus = Internal pr Deprecated. Listing members of rule-ruleset-name then failed as this class does not have an exposed property pyMethodStatus. To fix this issue, a check has been added to decide if the rule type is rule resolved or not. If the rule is resolved, then there will be a check for pyMethodStatus exposed or not. If pyMethodStatus is not exposed, then it will fallback to old list view. In addition, a check was added to not to add filter conditions on pyMethodStatus for non-rule resolved rule types. The only exception to this is Rule-Utility-Library, i.e. even though library ruleform is non rule resolved, pyMethodStatus filter will be added.
SR-A100443 · Issue 266643
XSS filter added for Profile Full Name field
Resolved in Pega Version 7.2.2
An XSS filter was missing in the control PZWARNINGJUSTIFIEDOPERATORNAME. This has been fixed.
SR-A97999 · Issue 264513
Decision tree handles special characters in the property label
Resolved in Pega Version 7.2.2
Attempting to open a Decision Tree with special characters in the property label generated an exception. This was due to the property label code not properly handling characters such as $ and \ and has been fixed by using the Matcher.quoteReplacement function Instead of directly using the string in replaceAll.
SR-A91902 · Issue 260915
OrgChartShow logic updated
Resolved in Pega Version 7.2.2
Attempting to update the organization unit for an operator resulted in the error "The flow action pre-processing activity OrgChartShow failed". To resolve this, the logic for Data-Admin-.OrgChartShow activity, pyOrganizations (a page-list property to hold the tree structure of the organization) has been updated.
SR-A98319 · Issue 266117
All key value data supported for field mapping
Resolved in Pega Version 7.2.2
If a data type was configured with local storage where all the columns are keys, the validation error "Must specify a target for at least one source field that isn't a record identifier" occurred when attempting to import data. Previously, pzValidateUpdateFieldMappings expected at least one non-key field in data type configuration and did not consider the condition of having all fields be keys of the data type defined. To support this configuration, the function has been updated to find the count of properties which are keys and which are not and use a 'when' rule pass for the above scenario.
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.