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-167254 · Issue 651529

Reports database configuration documentation updated

Resolved in Pega Version 8.4.6

Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database.

INC-177323 · Issue 672423

Search string wildcard use documentation updated

Resolved in Pega Version 8.4.6

The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.

INC-190130 · Issue 678543

Help information updated for using Elastic Search with Report Definition

Resolved in Pega Version 8.4.6

The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity.https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index

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.

INC-172944 · Issue 662828

Skin rule circumstancing article added

Resolved in Pega Version 8.6.4

An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.

INC-176462 · Issue 657412

Dashboard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.6.4

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

INC-180100 · Issue 662894

Scrollbar persists for multiselect

Resolved in Pega Version 8.6.4

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183672 · Issue 701868

Corrected vertical scroll bar for iPad Mashup page

Resolved in Pega Version 8.6.4

After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.

INC-186081 · Issue 675207

Report filter popup displays correctly

Resolved in Pega Version 8.6.4

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

INC-187196 · Issue 680749

Resolved Ajax popup alert for optimized iOS table

Resolved in Pega Version 8.6.4

When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.

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