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.

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-B43400 · Issue 307258

Localization added for field value used in 'Enter a Short Description' validation message

Resolved in Pega Version 7.3.1

Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.

INC-207693 · Issue 700541

Documentation updated for large attachments permissions error

Resolved in Pega Version 8.6.4

When using the Microsoft Graph API to send an email which contained an individual attachment 3MB or larger, the error "The token contains no permissions, or permissions can not be understood" was generated. Because the Microsoft Graph API has an attachment size limitation, the Microsoft Graph API send email flow will switch to using the Office 365 Exchange Online API when that size limit is hit. The documentation for this has been updated to explicitly reflect that Office 365 Exchange Online API permissions must be enabled in the Azure Active directory app settings.

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