Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us