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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B51449 · Issue 308503

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 308504

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 313658

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 313738

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B15685 · Issue 317888

Mobile autocomplete dropdown selections fixed

Resolved in Pega Version 7.3.1

When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.

SR-B71308 · Issue 319409

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B71308 · Issue 320806

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B66996 · Issue 312205

Access control policy logic added for non-work/data/assign classes

Resolved in Pega Version 7.3.1

As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.

SR-B66996 · Issue 315524

Access control policy logic added for non-work/data/assign classes

Resolved in Pega Version 7.3.1

As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.

SR-B55119 · Issue 312817

Handling added for absent property in Access When

Resolved in Pega Version 7.3.1

Configuring Access Control Policy to automatically restrict access to certain records by including an Access When rule to compare a custom property (.Consultant) on the OperatorID (Data-Admin-Operator-ID) page generated an exception if that property did not actually exist on the current operator. This has been resolved by revising the security policy engine to handle the exception.

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