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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-164924 · Issue 639022

Serbia added to country codes list

Resolved in Pega Version 8.7

The CountryCode for Serbia (SRB) has been added to the existing country codes.

INC-164979 · Issue 650155

Column values displayed in modify filter of grid

Resolved in Pega Version 8.7

Column values were not displaying in the modify filter after cancelling the ‘due date apply filter’ condition in grid -Go to My Work -> Work Queue -Apply filter condition for Program and Country/region columns. This was traced to the pysymbolic date value being posted after selecting and before applying the filter, and has been resolved.

INC-165277 · Issue 645168

PDF generation corrected

Resolved in Pega Version 8.7

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

INC-165964 · Issue 656814

Harness context set for modal dialog on interaction portal

Resolved in Pega Version 8.7

An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct.

INC-165992 · Issue 657691

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

INC-166322 · Issue 640272

Previously collapsed item in hierarchy list retains status

Resolved in Pega Version 8.7

The last collapsed item in the hierarchy list was expanding while trying to expand and select a new item. This was traced to the submit request for the previous request being sent while clicking on the next item, and has been resolved by adding a flag so that if the ModalAction is "JUMP" the system will not expand the collapsed nodes.

INC-166444 · Issue 642114

FlexModalTemplate Modal window size consistent

Resolved in Pega Version 8.7

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 647474

Handling added for Rich Text Editor base tag in email

Resolved in Pega Version 8.7

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 652468

Business users can move dashboard widgets on production portal pages

Resolved in Pega Version 8.7

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-167704 · Issue 671630

Email timing updated to ensure content captured

Resolved in Pega Version 8.7

Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.

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