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-125586 · Issue 188563

Drag and drop fixed for RDs with "SUM" functions

Resolved in Pega Version 7.1.8

If a report definition with 'SUM' function applied on one of the columns was included in a tree grid, the error "Exception when trying to execute dropOnSectionFromExternal" was generated. If the same report definition was used as a tree grid and the grid was dragged from the layout panel and dropped in a section, the columns in the repeat definition configured after the column having 'SUM' function were not displayed as tree grid columns. To correct this, changes have been made to the "populateSummaryReportColumns" method defined in "pzpega_ud_section.js".

SR-131611 · Issue 201761

Currency field 'save draft' function updated

Resolved in Pega Version 7.1.8

Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.

SR-117252 · Issue 174014

Modified SaveAs function for reports to avoid duplication

Resolved in Pega Version 7.1.7

After using "SaveAs" on an existing report, subsequently using "Save" caused two instances of the report to be saved into the database with the same key. The SaveAs function has been modified to correct this.

SR-117815 · Issue 170081

Updated UUID generation to function with Ping Identity

Resolved in Pega Version 7.1.7

Issues were experienced in trying to achieve connectivity using SAML 2.0 for an SSO solution. Ping Identity imposes a constraint on the format of the Request ID that it receives, and fails if that ID does not start with a letter or underscore. This ID is a random UUID generated by java code, and it had no set leading character. In order to allow full interoperability, the UUID generation has been replaced with a custom implementation which generates unique IDs starting with "_".

SR-A10464 · Issue 221099

Functions properly restricted with Decision Tree SaveAs

Resolved in Pega Version 7.2

A Decision Tree configured with with 'Allow changes to function lists' and 'Allow Selection of Additional Return Actions' checked in the 'Configuration' Tab was allowing unrestricted functions if SaveAs was used instead of saving and reopening the rule. The rule save handling has been updated to resolve this issue.

SR-A19599 · Issue 237365

Made getLocalizedValue function call fully qualified

Resolved in Pega Version 7.2.1

In environments where there are multiple versions of the function getLocalizedValue (which is true for any environment where the FSIF and KYC frameworks have been installed), pzFetchCaseStatusUpdate fails due to an unqualified function call. This has been corrected by providing the full context including library while calling functions in the property-set method in the mentioned activity.

SR-A23694 · Issue 246996

Timeliness functions modified to return 0 in place of NULL

Resolved in Pega Version 7.2.1

The "Timeliness" function aliases returned NULL for all the CASE statements that returned false, but NULL value using the AVERAGE summarize function in a report definition returned an incorrect result. The following Function Aliases have been updated to return a 0 instead of NULL when the result is false: - pxSLAAgeByClassTimeliness - pxSLAAgeTimeliness - pxSLAHistoryTimeliness - pxSLAAssignTimeliness

SR-A101107 · Issue 270079

TRUEFALSE function alias in report definition repaired

Resolved in Pega Version 7.2.2

After upgrade, attempting to use a Function alias with TRUEFALSE parameters in Report definition to return "false" in case the value is not set was causing a validation exception. This error was caused by a missing use case and has been fixed

SR-A75899 · Issue 256349

Character parsing improved for overridden sort function

Resolved in Pega Version 7.2.2

An overridden sort function could not be found when being called from a grid. This was due to the method name having two hyphens, and has been corrected by adding handling to strip and parse the methodName properly even when it contains "--".

SR-A75899 · Issue 260981

Character parsing improved for overridden sort function

Resolved in Pega Version 7.2.2

An overridden sort function could not be found when being called from a grid. This was due to the method name having two hyphens, and has been corrected by adding handling to strip and parse the methodName properly even when it contains "--".

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