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

SR-A14887 · Issue 230375

Support added for MSSQL datatype MONEY

Resolved in Pega Version 7.2.1

After upgrade, generating report definitions failed if the DB contained tables with columns that used the MSSQL-specific type MONEY, generating the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.MONEY". Support has now been added for this datatype.

SR-A14890 · Issue 230875

Tab title XSS decoding updated

Resolved in Pega Version 7.2.1

Tab titles were not correctly decoding the "(" and ")" characters in the caseID for display due to the XSS handling. This has been updated.

SR-A14892 · Issue 234201

Consistent Indexing initialization

Resolved in Pega Version 7.2.1

The first node in the cluster that was started was getting stuck at "Initializing Search Infrastructure." Elastic search was causing WAS7 to fail on startup due to the instances of indexerAgents (FTSindexerAgent, SystemIndexeragent) only being initialized in distributed mode, and an NPE was generated in non-distributed mode. This has been resolved by setting the indexerAgent instances to always initialize irrespective of the DASS indexing/distributed.

SR-A14917 · Issue 230745

Improved repeat grid filtering performance for Microsoft Internet Explorer

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, a repeat grid with source as report definition was taking 30 seconds to show filter options, and canceling the column filter results could take over 90 seconds. The functions have been tuned with updated jQuery code to resolve the issue.

SR-A14990 · Issue 230019

pyIsAccessible property defaults to false for AG unless checked

Resolved in Pega Version 7.2.1

The pyIsAccessible property was not being set by default for new access groups. This will now be set to false if the "Enable accessibility add-on" is not checked in pyDefault data transform (Applies to Data-Admin-Operator-AccessGroup).

SR-A15013 · Issue 233710

Localization added to AddCoveredWork InsAudit

Resolved in Pega Version 7.2.1

Localization has been added to param.InsAudit in the Pega Final activity AddCoveredWork.

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