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-153721 · Issue 613661

Visual natural labels exposed to JAWS in REST wizard

Resolved in Pega Version 8.4.4

Get/Post/Put/Patch/Delete checkboxes were not properly read by the REST Integration Wizard when when tabbing through the checkboxes with JAWS enabled. When tabbing to each, “Tab – Select this method if it is supported at the endpoint” was read for each checkbox, and no information was given regarding what method each checkbox was for. When any helper text is configured, an aria-label attribute with helpertext message is generated. This aria-label will override any other native labeling mechanism (label - id mechanism), which is this case caused the control label to not be announced. To resolve this, the system will remove the aria-label attribute when helper text is configured and will add the helpertext div ID in aria-describedby for accessibility.

INC-153783 · Issue 612993

Cross-site scripting protection update

Resolved in Pega Version 8.4.4

Cross-site scripting protections have been updated for labels.

INC-154205 · Issue 618735

Corrected wrap text for Cosmos radio buttons

Resolved in Pega Version 8.4.4

When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.

INC-154458 · Issue 620211

Calendar picker placement corrected for Ajax container

Resolved in Pega Version 8.4.4

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 617350

JAWS reads the table header and filter options separately

Resolved in Pega Version 8.4.4

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 Google Chrome from the way it reads them in IE, and has been resolved.

INC-154680 · Issue 619027

Moment timezone library update

Resolved in Pega Version 8.4.4

In order to reflect updates such as Brazil discontinuing DST time, the moment timezone libraries have been updated to the latest available version.

INC-154855 · Issue 616002

Updated expression handling when not using client side validation

Resolved in Pega Version 8.4.4

After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.

INC-156992 · Issue 619707

Show-stream/html repaired for custom portals

Resolved in Pega Version 8.4.4

After upgrade, show-stream/html in activity was not getting executed properly on custom portals. ShowDesktop was modified in 8.1 for AssociateRequestor implementation. As part of that, the custom portal step was moved to the new activity pzPopulateRequestor which is invoked from ShowDesktop. The JUMP condition in step is exiting the pzPopulateRequestor activity, but not ShowDesktop as was the case in the previous versions. To resolve this, the JUMP condition (.pyDesktopType=="Custom") has been added in ShowDesktop at the pzPopulateRequestor call step.

SR-69015 · Issue 619995

Unescaping characters implemented for expressions

Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6

An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.

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