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.

SR-116764 · Issue 199322

modal dialog retains fixed size when traversing a flow

Resolved in Pega Version 7.1.8

When a modal is configured to have different formats, those formats were missing upon going to the next assignment. This was caused by the format of the modal being reset Configured Modal Format was not being applied once we process flow in modal dialog. This has been fixed by passing the modalStyle parameter to the modal dialog callback.

SR-117272 · Issue 186154

Alignment issues fixed for grid headers with wrapped text

Resolved in Pega Version 7.1.8

After enabling the wrap text option for the grid headers, the headers were not properly aligned. This was caused by the height calculation being based on grid cell offset-height. The height calculation is not required as the CSS attribute word-wrap: break-word will be enough for the word wrap option and the grid cell height for the header text will be calculated by the browser automatically, and the explicit height calculation has been removed.

SR-117345 · Issue 179910

"Edit in Excel" handling corrected for delegated decision tables

Resolved in Pega Version 7.1.8

"Edit in Excel" was not working correctly on a decision table if it was delegated to a WorkManager portal from a traditional portal. After clicking on the edit button two pop ups appeared, and the Excel sheet was not visible after the pop ups were dismissed. This was traced to an issue with ActiveX where the server was not getting a fully-qualified URL in cases of open portal threads, and a check has been added to ensure proper handling.

SR-117827 · Issue 186000

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-117827 · Issue 183888

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-117877 · Issue 178627

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-117877 · Issue 175972

Report on implementation classes corrected for descendant class

Resolved in Pega Version 7.1.8

Report definition was not using implementation class even when 'report on descendant class' was checked. This was caused by an access group changed in RAQ not being reflected into DAQ. When a Data-Admin-Requestor has a Access group which isn't the default, the default authentication doesn't occur and as such the application data page isn't created for the requestor. The lack of an application page causes the code to not determine the associated implementation class for the report definition. This has been changed to use the access group from DAQ only if it is newer than RAQ.

SR-117931 · Issue 181714

Resolved clipboard conflict for obj-open-by-handle

Resolved in Pega Version 7.1.8

Doing an obj-open-by-handle or obj-open-by-handle/copy on work objects containing properties that reference data pages caused errors about non modifiable pxObjClass properties and non matching clipboard property modes. This was caused by a clipboard conflict, and has been addressed by handling the clipboard property as set value for feature property.

SR-118044 · Issue 178369

Corrections and enhancements made to Outlook meeting requests

Resolved in Pega Version 7.1.8

Using the function 'SendEmailMessage' to send an Outlook meeting request was only generating an email instead of the full meeting invitation. This was traced to unimplemented code and has been corrected. In addition, enhancements have been added to the FormatMeetingRequest RUD to set RSVP options for TO & CC recipients, and the PRODID flag value has been parameterized.

SR-118160 · Issue 175398

Email Listener performance improved

Resolved in Pega Version 7.1.8

A mismatch in time values was causing Email Listener to be extremely slow in some complex installations. This has been corrected to improve performance.

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