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-A22458 · Issue 243317

Plus '+' sign encoding corrected in connect-HTTP

Resolved in Pega Version 7.2.1

Using connect-http get to send an encrypted string to the external endpoint was not working due to missing encoding for the plus '+' string. The encoding has now been fixed.

SR-A22615 · Issue 244189

Fixed positioning for Options lightbox

Resolved in Pega Version 7.2.1

The Options lightbox in the calendar was floating with the screen while scrolling due to absolute positioning, and has been fixed.

SR-A22672 · Issue 243213

Use Pega Log Analyzer in place of Alerts.xls Excel Template

Resolved in Pega Version 7.2.1

A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer

SR-A22722 · Issue 246998

pxDereferenceEndpoint Activity can be overridden by the customer

Resolved in Pega Version 7.2.1

The generic pxDereferenceEndpoint Activity that applies to the Rule-Connect-REST class was not the functionality desired by the customer, so they wanted to be able to change it, but it was set to ?Final? and couldn?t be changed. The availability of the pxDereferenceEndpoint Activity has now been set to ?Available? so that customers may override it in any RuleSet. (No logic changes have been made to this activity.)

SR-A22750 · Issue 244061

Case Stages status updated by automated process

Resolved in Pega Version 7.2.1

Case stages that were completed by an automated process and not a person maintained their default "Future" status in the Case Stages data page instead of being marked "Past". The stage completion status is determined by value in "pxCompletedBy", but this field was empty due to the automation. A check has been added to resolve this.

SR-A22794 · Issue 245278

parseXML able to map multiple values

Resolved in Pega Version 7.2.1

In order to present more information for custom use, parseXML as been updated with a new pagelist property that can map multiple attribute values.

SR-A22813 · Issue 244103

Apostrophe(') escaped in tooltip property

Resolved in Pega Version 7.2.1

Whenever there was an apostrophe in the radio button's tooltip property, all the content of the tooltip after the apostrophe was not considered. When inspected in DOM, the label's title was considered only until apostrophe with all the remaining being generated out of title attribute and hidden. This has been fixed by properly escaping the apostrophe.

SR-A22816 · Issue 246151

Message clearing CME error fixed

Resolved in Pega Version 7.2.1

A Concurrent Modification Exception error as thrown in logs when navigating to from one row to another row in tree grid due to a data page being loaded while trying to clear messages in a page. This has been resolved by disabling auto populate while in the process of clearing messages in a page.

SR-A22841 · Issue 245073

All Data Flow keys considered for filtering

Resolved in Pega Version 7.2.1

When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.

SR-A22933 · Issue 241566

Check added to resolve Google Chrome-based value localization error

Resolved in Pega Version 7.2.1

A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.

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