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.

SR-A20300 · Issue 239490

SLAs agree in assignment gadget and action area

Resolved in Pega Version 7.2.1

An assignment created with an SLA of 2 years was showing different SLA info in assignment gadget and action area. On the assignment list gadget, the deadline displayed was "1 year 12 months from now" which is correct. On the top right corner of the action area it says, "Due in 1 year 11 months from now". This has been fixed by modifying the base calculations of the pyAssignmentTimeLimitDeadline control.

SR-A20336 · Issue 240862

Corrected SLA name set with passed value

Resolved in Pega Version 7.2.1

The SLA name was not correctly set on the assignment page during creation if the field was left empty for a passed value to fill. This has been corrected.

SR-A20346 · Issue 242973

Cell height/width rounded in "," decimal locales

Resolved in Pega Version 7.2.1

Localization for areas that use "," as the decimal separator led to errors indicating the height/width of a merged cell of Free Form layout was a non-integer value. To avoid this, the design time JS will round the measurement for cellWidth and cellHeight.

SR-A20352 · Issue 242962

Scroll handling updated for autocomplete results popover

Resolved in Pega Version 7.2.1

Issues were found with the scrolling handling of an autocomplete popover opened inside a modal window. The pzpega_ui_popover.js has been modified to attach a scroll handler for modal dialog scroll, and code has been added in the clickaway handler to reposition the popover during scroll.

SR-A20391 · Issue 240293

Set enter key use for Google Chrome pagination

Resolved in Pega Version 7.2.1

In Google Chrome, the enter key was not working on the pagination gadget if the report was opened in a new window, but tab would fire the page change. Functionality has been added to the GridActivePage control to create the expected behavior.

SR-A20444 · Issue 238240

BusyIndicator masking fixed for Microsoft Internet Explorer and Firefox

Resolved in Pega Version 7.2.1

BusyIndicator masking was not working properly in Microsoft Internet Explorer and Firefox due to using the scrollTop property which does not work for body elements in these browsers. This has been fixed by adding a browser check and calculating scrollTop from documentElement.

SR-A20450 · Issue 239606

Locale validation step added to match accepted formats

Resolved in Pega Version 7.2.1

It was noticed that if a locale was specified on the Operator rule using a hyphen rather than an underscore (such as en-GB vs en_GB), the operator defaulted to the US locale for date and time formats and no check or error would be generated. To ensure expected behavior, a step has been added to validate the format of locale to match either "blank", xx, or xx_XX.

SR-A20470 · Issue 240001

Twitter harvesting enhanced

Resolved in Pega Version 7.2.1

Data recovery has been improved for Pega Customer Service Social Engagement customers harvesting Twitter streaming data. If a steaming data set fails for any reason, whether due to disconnecting of the API for a short period, server failure, or for any other scenario where Tweets are not ingested in real time, the data recovery capability will fetch missed Tweets within a given set time window of recent Twitter historical data. This is done through an activity to create a Twitter search data set which can then be used to work act as a data source for the data flow. Additionally, logic has been added to identify the appropriate language for short inputs (one or two words).

SR-A20504 · Issue 241375

Queue type validation updated in MDBListener

Resolved in Pega Version 7.2.1

Queue type validation failed when testing connectivity in MDBListener if the pyResourceName was set with queue name and there was no pyResQueueName defined in the page. To handle this, the getString function will use the pyResourceName instead of pyResQueueName.

SR-A20569 · Issue 238382

Mandatory date and amount fields validation performed before reset

Resolved in Pega Version 7.2.1

Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, and has been fixed.

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