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-212623 · Issue 709549

HTML attachments conditionally shown in email listener cases

Resolved in Pega Version 8.6.4

When Rich text/html (non-plain text) emails were ingested in email, the original mail was not getting added to the case. Investigation showed that the pzCreateTriageWork activity had an explicit delete step to remove any attachment that started with 'email-content'. Since the HTML attachment name starts with 'email-content', it was deleted in above activity. This has been resolved by adding a when rule named 'pyLinkEmailTriageContentHTML' which will conditionally show email-content.html.

INC-213247 · Issue 708870

Title attribute added for disabled icons

Resolved in Pega Version 8.6.4

The disabled icon control in non-template mode used the tempTitle attribute instead of title, interfering with accessibility because no information was available to screen readers. This has been resolved by adding the aria-disabled attribute to the disabled icon control.

INC-215582 · Issue 712286

Cosmos calendar icon handles allow entry set to no

Resolved in Pega Version 8.6.4

When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.

INC-215912 · Issue 711380

Corrected links being replaced by KM rich text editor

Resolved in Pega Version 8.6.4

When brackets/parentheses were encountered in URL links in the rich text editor used in Knowledge Management, those links were removed and replaced with a # (pound symbol). This was due to a legacy cross-site scripting security mitigation, and h as been resolved.

INC-216358 · Issue 712230

Auto Complete working in Mobile Browser configuration

Resolved in Pega Version 8.6.4

Autocomplete was not working in the mobile browser when logged in as a user and configured with display mode:"in-a-table" and "display as full screen in mobile" disabled. Autocomplete results will always display in List mode in the mobile browser, but with the configuration "in a table" selected and "Display results full screen on phone" unchecked, pzGetACData (which gets called for List mode) was not registered and returned a 403 response. To handle this, the conditions file ActionAssembly.java has been removed so pzGetACData will always be registered.

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.

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