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-202878 · Issue 713792

Handling updated for social messaging items with very large embedded images

Resolved in Pega Version 8.6.5

Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.

INC-211974 · Issue 706616

UpgradeInteractionCase modified to update work page on save

Resolved in Pega Version 8.6.5

After update, service cases were failing to unpend when using a custom data transform that accessed the D_CorrespondenceCase data page. Investigation showed the D_CorrespondenceCase data page was internally using the D_pxGetInteractionCaseDetails data page; this call upgraded and saved and committed the case but this commit released the lock which the custom data transform had acquired. Because this happened before accessing the CorrespondenceCase datapage, it led to an error while committing the service case details. To resolve this, the postprocessing activity "pyUpgradeInteractionCase" of D_pxGetInteractionCaseDetails has been modified to write the update on the work page as soon as a save is performed.

INC-188141 · Issue 678160

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-190855 · Issue 681093

Duplicate items resolved for questionnaires

Resolved in Pega Version 8.6.5

When there was only one question page for a questionnaire, the question page title was being displayed twice and the breadcrumb showed duplicate steps. When there was only one step in the screen flow, the survey navigation was hidden. This has been resolved.

INC-191756 · Issue 718551

Corrected dashboard focus highlighting

Resolved in Pega Version 8.6.5

Dashboard links like "My activities"/"My cases"/"Recent"/"Search” were displayed with a yellow focus highlight even though the user was not currently in those screens. Investigation showed the data-menu-id for control_menu was being appended with the workid until selecting another tab caused it to reset to its original value without workid. This change in menu-id was responsible for the issue with focus, and occurred only when render as single checkbox was unchecked. This has been resolved by removing workid from menuid and adding a unique id for the outside menu and inside case same menu.

INC-196186 · Issue 725412

Check added for repeating dynamic layout submit context

Resolved in Pega Version 8.6.5

The postprocess of a local action was not executing when the local action was in a table that contained a repeating dynamic layout, and a null pointer exception was generated. Investigation determined that when a repeating dynamic layout was used inside a grid, the submit action on the layout was incorrectly happening in the context of the grid. To resolve this, a check has been added to determine whether the repeating dynamic layout is inside a grid so the correct context is used.

INC-198784 · Issue 697526

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-199137 · Issue 708165

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-205394 · Issue 706788

Hidden subprocess steps highlighted in screen flow navigation

Resolved in Pega Version 8.6.5

When a subflow was used as a last step within a screenflow and the subflow steps navigation links were hidden, the subprocess step was not highlighted as current. To correct this an update has been added that will highlight the circle on the navigation for a subprocess set as last step with substeps hidden, and the lines on the navigation step will be highlighted on the left side for a subprocess set as a step other than the last step and which has substeps hidden.

INC-206058 · Issue 709517

Property label correctly highlighted after validation failure

Resolved in Pega Version 8.6.5

The property label was not changing to red after validation failed. This has been resolved.

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