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-154458 · Issue 620210

Calendar picker placement corrected for Ajax container

Resolved in Pega Version 8.3.6

When using inline edit and clicking date picker, the calendar popover was displayed in a blank space away from the position of the date picker. This was due to a popover inside a screenlayout having scrolltop and scrollleft values added to the popover position; in the case of an Ajax container these values resulted in incorrect position of a popover. To resolve this, adding the scrolltop and scrollleft will be bypassed if the element where the popover is attached is inside a Ajax Container.

INC-154564 · Issue 617349

JAWS reads the table header and filter options separately

Resolved in Pega Version 8.3.6

When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Chrome from the way it reads them in Microsoft Internet Explorer, and has been resolved.

INC-156826 · Issue 625437

Logic updated for adding new child/sibling to hierarchical paginated tree/grid

Resolved in Pega Version 8.3.6

When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.

INC-156912 · Issue 627486

Updated accessibility for Rich Text Editor navigation in a modal dialog

Resolved in Pega Version 8.3.6

When navigating through a Rich Text Editor while in a modal dialog, it was expected that once focus was brought to the RTE Toolbar (Alt+F10), pressing Escape on the keyboard would bring the focus back into the RTE text area and the cursor would appear. However, when this RTE was within a modal dialog, pressing Escape closed the modal dialog entirely. This has been resolved by updating the code to stop the Escape key event propagation from the RTE toolbar when in a modal dialog.

INC-157353 · Issue 624010

Handling added for autoclose of assignment in tabbed MDC

Resolved in Pega Version 8.3.6

After configuring an Ajax container in a section using tabs and max doc defined as 8 with 'doClose' set after processing has been completed, finishing the assignment caused the work item tab to stop working. Checking the console showed a script error was being thrown. Investigation showed that when the doClose action was triggered and tried to find the activeTabs in MDC, the target element being fired was null. This has been resolved by adding a condition for the doClose to handle the combination of autoclose and tabbed MDC that will close the current Ajax container div before proceeding.

INC-157662 · Issue 631998

Accessibility updates added for images and icon controls

Resolved in Pega Version 8.3.6

In order to improve accessibility, aria-hidden has been added to button and link controls for decorative images, and the alt attribute will be generated by the icon control only when the icon source is Image. The icon control has also been updated to set accessibility roles based the following:if actions are configured -> role=button if no actions are configured -> role=img if type is url/phone/email -> role=link

INC-157737 · Issue 631687

Added ability to support multiple domains for users

Resolved in Pega Version 8.3.6

Previously, the DSS setting MultiTenant/CrossTenant/DomainName supported just a single domain. In order to support multiple domains for internal and external users, an enhancement has been adde so that given two domain values provided as comma-separated values in “MultiTenant/CrossTenant/DomainName” DSS setting, pzSetCrossTenantDomain will determine the correct domain value using pxRequestor.pxReqServer.

INC-157776 · Issue 633239

Corrected layout issues with Dynamic Group layout

Resolved in Pega Version 8.3.6

After loading a large number of tabs in Dynamic Group Layout (default), navigating to the last tab caused the right icon to be disabled on any of the 20+ tabs and the margin-top value increased from 0 to 24px. This has been resolved.

INC-157795 · Issue 624671

DateTime dropdown control will retain entry on validation error

Resolved in Pega Version 8.3.6

For a Date Time control with display mode as dropdownlist, choosing just a month or a day from the dropdown and refreshing the section resulted in an invalid date validation and the field being set to the current date. Choosing the date from the calendar icon or filling in all three drop downs worked as expected. This has been resolved by updating the datetime control so that if a dropdown mode with property as type DATE has a validation error on refresh action, the user-entered data will show in the dropdown instead of the current date/time.

INC-157860 · Issue 633946

Corrected error message display in right-to-left locales

Resolved in Pega Version 8.3.6

When using the standard report definition view in the Arabic (ar_AR) locale, error messages for a filter condition were displayed with an incorrect extended horizontal scroll bar with white space. This was traced to the legacy popover styling causing an issue with locales that display text from right to left, and has been resolved by setting the default overlay left to 0PX for these locales.

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