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-132569 · Issue 595176

Resolved case detail overwrite

Resolved in Pega Version 8.6

In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.

INC-132670 · Issue 585775

JAWS reads optimized table rows correctly

Resolved in Pega Version 8.6

When using JAWS2020 on Google Chrome on a PegaWAI enabled application and traversing an optimized table using Table shortcuts, the first row of the table was never read, and columns were read with the headers, but with unnecessary verbiage. For example, if column "Name" had an entry "Adam", JAWS read out "Name press enter to sort , Adam" instead of just "Name Adam". JAWS reads the data columns based on aria-rowindex: because it treated the header as the first row, it directly went to the row with aria-rowindex 2. In the second issue, the complete header group was read by JAWS because there was no aria-label. These have been resolved by modifying the aria-rowindex attribute for first data row accessibility by JAWS, and aria-label has added to the header group to restrict what is read out while navigating across the data columns.

INC-132771 · Issue 584962

MultiSelect properly handles refresh section

Resolved in Pega Version 8.6

On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.

INC-133576 · Issue 590326

Expandable Grid behavior corrected

Resolved in Pega Version 8.6

Expanding any row in master details was collapsing a previously expanded row. This has been corrected.

INC-133923 · Issue 600299

JAWS correctly reads headers of optimized tables

Resolved in Pega Version 8.6

Table column headers were not being read correctly with JAWS2020 and Google Chrome when using the "Tab" key to traverse the headers of an accessibility enabled application (PegaWAI ruleset included) that had an optimized table. This has been resolved by adding enhancements to enable keyboard navigation as per the WCAG standards of grid navigation for optimized tables.

INC-133944 · Issue 586017

Future DateTime Property picks operator time zone

Resolved in Pega Version 8.6

When selecting the DateTime in a property field configured to accept future data input, the input failed validation due to the DateTime field being compared with the System time zone (IST instead of the operator time zone. This has been resolved by adding a condition to honor the operator time zone in isFutureDate validation, and to fall back to the browser time zone if necessary.

INC-133978 · Issue 587699

Overlapping columns fixed in ReportViewer

Resolved in Pega Version 8.6

When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.

INC-134634 · Issue 584947

FSM Mobile app correctly starts phone call after closing Google

Resolved in Pega Version 8.6

When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.

INC-134891 · Issue 589870

Logoff set to use root context

Resolved in Pega Version 8.6

The thread name was changing from Standard to DSCPA_DemoStudio on click of log-off, resulting in unexpected behavior if the user logged in again. To resolve this, an update has been made to trigger logoff in root context.

INC-134893 · Issue 587170

Added check for localeDb properties in dateTimeUtils

Resolved in Pega Version 8.6

On click of the Approval/Finish assignment submit button, a blank screen appeared and no further progress could be made. This was traced to an issue with the operator locale not being properly set by the html fragments that initialize the locale for use in dateTimeUtils. This has been resolved by adding a check for properties in the localeDb object.

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