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-157367 · Issue 637945

PDF generation corrected

Resolved in Pega Version 8.4.5

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-157404 · Issue 630692

Adaptive Model report information exports correctly

Resolved in Pega Version 8.4.5

Clicking export to Excel or PDF in the Prediction Studio Adaptive Model report was not working. Investigation showed the first double quote of the propositionName was getting replaced from & quot ; to "", which resulted in an error while performing openUrlWindow action. This has been resolved by adding a new helper handler, while creating context menu using Handlebars.

INC-157448 · Issue 638922

Latitude and longitude populated for CreateWork history

Resolved in Pega Version 8.4.5

After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.

INC-157662 · Issue 631997

Accessibility updates added for images and icon controls

Resolved in Pega Version 8.4.5

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-157699 · Issue 624595

Customer 360 Tabs load in Mozilla Firefox browser

Resolved in Pega Version 8.4.5

After upgrade from v8.1 to v8.4, the layout group's tab content was not loading as expected in the customer 360 view when using the Mozilla Firefox browser. Investigation showed this was due to the “role” attribute being removed from the header div by the on-hover showSmart tip action configured on the dynamic layout tabs. This has been resolved by updating the system to use data-role along with the role tab.

INC-157737 · Issue 631686

Added ability to support multiple domains for users

Resolved in Pega Version 8.4.5

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-157795 · Issue 624670

DateTime dropdown control will retain entry on validation error

Resolved in Pega Version 8.4.5

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 633945

Corrected error message display in right-to-left locales

Resolved in Pega Version 8.4.5

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.

INC-157957 · Issue 624207

Autocomplete correctly sets null values in clipboard

Resolved in Pega Version 8.4.5

When using an autocomplete control with display configuration "In a List", if a property value was null then the value of the property in the clipboard was set as “undefined”. This was due to the pzGetACData activity returning only properties with values and excluding empty properties, causing setProperty to use "undefined" when a property value was not found in the response. To resolve this, a condition has been added to the processAdditionalProperties method to replace an undefined value with an empty string.

INC-158129 · Issue 635304

Left navigation expansion made accessible for tab/keyboard actions

Resolved in Pega Version 8.4.5

The left navigation "aside" DOM element did not expand if reached with the keyboard tab actions, but did with mouse hover. This has been resolved by updating the selectors for focus within left nav and updating the script to collapse the menu pyAutoCollapseLists section.

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