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-166444 · Issue 642112

FlexModalTemplate Modal window size consistent

Resolved in Pega Version 8.6.1

The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.

INC-166706 · Issue 647478

Handling added for Rich Text Editor base tag in email

Resolved in Pega Version 8.6.1

Clicking on an email interaction case from the worklist was not opening the case. This was traced to a base tag present in Rich Text Editor content which impacted security protections, and handling has been added to remove this tag.

INC-167611 · Issue 652467

Business users can move dashboard widgets on production portal pages

Resolved in Pega Version 8.6.1

Business users were not able to use "Edit dashboard" to move dashboard widgets in production portal pages. This was a missed use case of using an operator with different security level, and has been resolved by using the control pzUserDashboardIncludeScript instead of including pzpega_dashboard script directly in the UserPortal harness.

INC-167747 · Issue 649655

PDF generation corrected

Resolved in Pega Version 8.6.1

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-168414 · Issue 641034

Web Mashup works from nested iframe

Resolved in Pega Version 8.6.1

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

INC-168695 · Issue 643015

String conversion logic updated for toFixed function

Resolved in Pega Version 8.6.1

The toFixed function of pzpega_ui_formatNumber.js was incorrectly converting a string while formatting the value. This potentially caused the UI to hang until manually refreshed. To resolve this, the logic has been updated to convert the string to a number before calling toFixed().

INC-169012 · Issue 651256

VMWare workspace One Mobile support added

Resolved in Pega Version 8.6.1

Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.

INC-169203 · Issue 645694

Robotics Desktop Automation correctly runs on subsequent tabs

Resolved in Pega Version 8.6.1

When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.

INC-169796 · Issue 649261

Null check added for pyModes setting

Resolved in Pega Version 8.6.1

The column filtering function was not working after update from Pega 8.1 to Pega 8.5. This was traced to pyModes being set as null for page group properties, and has been resolved by adding a null check before adding the type to avoid getting an improper result from the Formatter Rule-Utility-Function.

INC-169866 · Issue 653549

View content type updated to FIELD

Resolved in Pega Version 8.6.1

After update table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after update to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.

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