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-145535 · Issue 600784

Corrected layout group overlapping content

Resolved in Pega Version 8.6

When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.

INC-145939 · Issue 606897

Updated handling for ID value change during REST connection creation

Resolved in Pega Version 8.6

When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.

INC-146098 · Issue 633724

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.6

Keyboard short cuts used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-146223 · Issue 604465

Date column filter shows correct date/time for optimized code

Resolved in Pega Version 8.6

Two issues were seen when filtering a table that had the "Optimize Code" checkbox checked: 1) While filtering the date values in the table, the table showed one day less than the actual date based on time zone differences. When both the operator and server time zones are the same, the issue did not occur. 2) The filter always showed the time value as 00.00 irrespective of the property timestamp value. These were traced to the pyModes being incorrect for embedded properties, which has been resolved.

INC-146237 · Issue 608742

Corrected popover scroll for AnyPicker

Resolved in Pega Version 8.6

Using the AnyPicker control caused display problems. In the initial display of the selection list, the line of choices and the search field overlapped and they were displayed from the second line of choices which forced the user to scroll up to see the first line. After displaying the selection list, clicking outside the selection list without selecting anything to close the list and then displaying the selection again caused the options to be displayed from the 4th line, requiring a scroll up to see lines 1 to 3. This has been resolved to ensure the Scroll on Popover goes to the first element.

INC-146262 · Issue 603690

Handling added for new doc.write with Google Chrome 85

Resolved in Pega Version 8.6

Document.write was not working as expected on Google Chrome 85 due to the DOM elements not being updated. This has been resolved by updating the code to do doc.write by checking the if the document body has no child nodes in a time out.

INC-146429 · Issue 602291

Disabled control status made accessible to JAWS

Resolved in Pega Version 8.6

When using the Security Event Configuration page (tab) within Pega Dev Studio, the link elements used for 'Select All', 'Clear', 'ON' and 'OFF' were not providing the current State of the element to JAWS. In template rendering of Link control with a 'disable when' condition (server-side evaluation), when the control is disabled it was still accessible and screen readers were not reading the link as disabled. This has been resolved by adding tabindex="-1" and aria-disabled="true" for disabled Link control.

INC-146572 · Issue 603295

iniGadgets updated to support jQuery with Mashup

Resolved in Pega Version 8.6

Mashup gadgets were not loaded during browser refresh when the host page had a jQuery in it. This issue occurred while trying to find the gadget divs. There is an 'if' condition to check if $ is available in initGadgets method. In this scenario, this 'if' block was getting executed and mashup gadget divs were returned as empty. As a result. mashup was not getting loaded. This has been resolved by updating the iniGadgets method to check for jQuery instead of $.

INC-147245 · Issue 612866

Expand Pane icon responds to enter key when using JAWS

Resolved in Pega Version 8.6

In an Operator ID rule in Dev Studio, pressing the Enter key when focused on an Access Group expand icon caused the focus on the page to move to the top of the Contact Information frame (top left corner of the Frame). The only way to use the enter key to expand the pane without the refocus was to tab to the arrow icon and then tab a second time before pressing enter. This was traced to the expand caret icon being focussed twice due to the tabIndex for both the TD and SPAN elements holding the caret icon: TD had a focus element for accessibility of the grid, and SPAN had it for the expand pane accessibility. This has been resolved by adding a check condition before adding tabIndex to the first cell in the Grid.

INC-147537 · Issue 604641

JAWS reads error messages only once

Resolved in Pega Version 8.6

JAWS v18 was reading harness level error three times or more. This was traced to multiple error message divs being generated in the HTML, and has been corrected.

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