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-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.

SR-A20581 · Issue 242760

Added checks to pagelist indexes for processing and recovery

Resolved in Pega Version 7.2.1

Sporadically, work objects saved to the database generated the error "The Flow Action pre-processing activity pyPopulateCaseContentsWrapper failed: cannot be null or blank. page: . Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)" This happened when changes to Indexes in pagelists were getting overridden with another pagelist index, causing data to be lost on database save. A check has now been added to identify whether the entry has been processed in the current encode, and a hard check has been inserted to prevent data loss of page lists.

SR-A20593 · Issue 238898

Pagination added to Hotfix Manager

Resolved in Pega Version 7.2.1

If there were more than 10 uncommitted hotfixes, the Hotfix Manager was not able to display them all due to a page limit and pagination being disabled by default. The pagination footer has now been made visible to allow viewing of the full list of uncommitted fixes.

SR-A20603 · Issue 241334

Post-upgrade Connect-SOAP multi-ref mapping fixed

Resolved in Pega Version 7.2.1

After upgrade, the Connect-SOAP responses including multi-refs were not getting mapped correctly and there were problems viewing the response message from the SOAP service. This has been fixed.

SR-A20634 · Issue 248378

Added handling for missing blob from external data class

Resolved in Pega Version 7.2.1

When using an external data class, an error was generated complaining of "trying to retrieve property pxInsHandle from a fully exposed table that does not contain it". This happened because the external table did not have a blob column but did have pxObjClass and pzInsKey, and handling has been added to correct this.

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