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.

INC-207693 · Issue 700542

Documentation updated for large attachments permissions error

Resolved in Pega Version 8.7.2

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.

INC-217942 · Issue 716931

BIX article updated for XML extract rules

Resolved in Pega Version 8.7.2

The BIX article "Creating and running an Extract rule" has been updated to reflect that the "Get all properties" option fetches basic properties only, and that properties must be selected manually for non-BLOB tables.

SR-D85563 · Issue 551684

Dependencies of module.xml documentation update

Resolved in Pega Version 8.5.1

Documentation has been updated to include specifics about adding a dependency in Microsoft JDBC Driver 6.0., under dependencies of module.xml.

SR-D88570 · Issue 550104

Cleanup script topic moved to Post-Upgrade steps in deployment documentation

Resolved in Pega Version 8.5.1

The deployment guides have been updated to indicate that the cleanup script should only be run after the upgrade has been completed, as well as clarifying that this is only required if the clean up scripts have never been run previously.

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