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-A14740 · Issue 232865

Edit button page retrieval updated for better accuracy

Resolved in Pega Version 7.2.1

Due to the Edit button configuration for Data types passing the identical name "Data Type" to the Landing Page action configuration, the pages being retrieved for editing were inconsistent when moving between the Dashboard and the Manage Change screen. The system has now been updated to pass the unique pyInsHandle key for every data type to ensure expected results.

SR-A14740 · Issue 232864

Edit button page retrieval updated for better accuracy

Resolved in Pega Version 7.2.1

Due to the Edit button configuration for Data types passing the identical name "Data Type" to the Landing Page action configuration, the pages being retrieved for editing were inconsistent when moving between the Dashboard and the Manage Change screen. The system has now been updated to pass the unique pyInsHandle key for every data type to ensure expected results.

SR-A14774 · Issue 233421

Number formatting made consistent for Propositions

Resolved in Pega Version 7.2.1

In Proposition landing, a decimal property was rounded to three digits when shown in read-only mode but clicking on the edit option for the Proposition displayed the entire number with all the digits after the decimal. This was not a desired difference, and the presentation setting for Double type property has been modified to show all numbers after the decimal.

SR-A14781 · Issue 246050

Timeout value honored for ConnectSOAP using JMS Transport

Resolved in Pega Version 7.2.1

ConnectSOAP has a response timeout function, but this setting was not being honored when JMS transport was used. This has been corrected.

SR-A14826 · Issue 228519

Resolved IndexOutOfBounds extraction error for page list data

Resolved in Pega Version 7.2.1

When running BIX extract rules, it was failing to extract cases information for XML output formats containing data in Page Lists in the extract rule. Excluding the page lists from the extract rule would runs and extract the data successfully. To fix this, filter() in PropertyReferenceImpl will return unmatched strings.

SR-A14841 · Issue 234741

Multiple message deletion updated in MQ Server and MQ Explorer

Resolved in Pega Version 7.2.1

When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.

SR-A14841 · Issue 234742

Multiple message deletion updated in MQ Server and MQ Explorer

Resolved in Pega Version 7.2.1

When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.

SR-A14842 · Issue 233614

Screen reader updated to handle autocomplete

Resolved in Pega Version 7.2.1

The list in the dropdown was not read by the accessibility package if the focus was on the Autocomplete present in a modal dialogue. To correct this, the new function "AutoCompleteAG.updateLiveRegion" has been added to pega_autocompleteag.js for generating aria attributes for dropdown list items.

SR-A14862 · Issue 231106

TrimLog performance improved

Resolved in Pega Version 7.2.1

Activity log.trimlog is called several times from the systemCleaner agent to clean up old entries of generally unused Log- classes. In order to improve performance on large logs, the previous partial load and delete method has been updated to a bulk cleanup using the purgeTableContainingClass() API in the Pega Database.

SR-A14879 · Issue 232530

Improved security for JSON stack

Resolved in Pega Version 7.2.1

To increase security, the response to invalid JSON input will display a generic InvalidStream message rather than the full class name and method name. The complete information will be available in the log.

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