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-136793 · Issue 585603

Updates made to display busy indicator correctly in Google Chrome 84

Resolved in Pega Version 8.5.1

The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.

INC-135906 · Issue 582901

Harness open handling added for tabs with apostrophes

Resolved in Pega Version 8.5.1

A javascript fail resulted when attempting to open any harness with an apostrophe (') in the name. This was a missed use case, and has been resolved by updating the PegaCompositeGadgetMgr file with a check and appropriate handling.

INC-135594 · Issue 581779

Smart Tip displays correctly with double quotes

Resolved in Pega Version 8.5.1

After configuring a Smart Tip action which used a selected field value as tip source, the double quotes in the tool tip caused it to not be displayed. This has been resolved by escaping double quotes when a field value is configured in Smart Tip.

INC-131774 · Issue 577047

Resolved focus for new s-case

Resolved in Pega Version 8.5.1

After creating an s-case by using the keyboard, the focus jumped to add task instead of newly added s-case page. This was traced to the 'if' condition in focusFirstElement method becoming true for all touchable devices including desktop with touch enabled, causing the focus method on the first element to not be executed. This has been resolved by adding an additional conditional to check whether the device has touch enabled and is a mobile device.

INC-135061 · Issue 579540

Save on modal close works as expected

Resolved in Pega Version 8.5.1

After upgrade, a repeating dynamic layout with a modified modal dialogue template that had an added save button to it was not working as expected. This was traced to a change in the operations order for the modal save and close, and has been resolved.

INC-131225 · Issue 579734

Child cases correctly created on mobile app

Resolved in Pega Version 8.5.1

After upgrade, creating a child case from the device generated the error "Failed to reset case type. Not starting optional process : undefined" when launching a "nestedRDL" case and clicking on the "CreateCase1" button on the top. This has been resolved by updating the harness action API to read the harness purpose from DOM instead of the harness context for the HC case.

INC-135098 · Issue 578485

Corrected paste/drag and drop upload with rich-text editor

Resolved in Pega Version 8.5.1

After upgrade, the CK Editor was not correctly adding the image when using cut and paste or drag and drop: only the image uploader button was working. This has been corrected by adding code to conditionally upload the image to the server while doing a paste in rich-text editor control.

INC-136518 · Issue 582571

Elapsed time available for an AJAX event duration

Resolved in Pega Version 8.5.1

An enhancement has been added which will capture a start of queue event for an AJAX event. This can be added to the existing end of queue event information and be used to calculate the event duration via Pega Web Analytics.

INC-130790 · Issue 580590

Special character handling added to App Studio column headers

Resolved in Pega Version 8.5.1

Changing the order of columns in App Studio was destroying the section, causing it to not be able to render unless it was restored. Investigation showed this was caused by an exception in the getIfPresent function due to the presence of special characters after a period (.) that were not considered valid identifiers. To resolve this, the GenerateCellContent Rule-Utility-Function has been updated to better parse the property identifier of the column header value.

INC-127658 · Issue 568625

Corrected 1 day discrepancy for non-template DateTime

Resolved in Pega Version 8.5.1

Date values in DateTime controls in a custom filter section of a report definition were reduced by one day after drilling down into drilldown report and navigating back to the main report. Investigation showed that when the non-template version of datepicker was configured with a date property, it displayed the value using read-only formatting with allow text entry set to 'No'. This caused the operator time zone to be used to format the value while data-value used the default timezone(GMT). To resolve this, and update has been made so that while generating markup in non-template for the date property the default timezone will be used whereas the datetime property will use the server timezone.

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