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-A17672 · Issue 236191

Tab layout groups updated to retain status when switching

Resolved in Pega Version 7.2.1

Switching between tabs caused the harness to refresh. The tab layout groups have been updated to ensure expected behavior.

SR-A17683 · Issue 235082

Autocomplete JSON error resolved

Resolved in Pega Version 7.2.1

A JSON parse error was causing issues with autocomplete controls after updating. This was caused by a syntax error, and has been corrected.

SR-A17738 · Issue 234851

Authentication requirement removed from OnProcessEnd

Resolved in Pega Version 7.2.1

pzChangeStageWrapper calls pzOnProcessEnd, which requires Authentication and is a Final rule. This created an issue using the ChangeStageWrapper without authentication, and the authentication requirement has been removed from OnProcessEnd.

SR-A17748 · Issue 233597

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-A17758 · Issue 234057

Check added to avoid duplicate encryption

Resolved in Pega Version 7.2.1

When a property of type TextEncrypted was edited from the clipboard viewer, the encrypted value was being encrypted again. This was caused by the server side trimming the string values of parameters sent in a post body, removing '\t' from the encrypted value '\t{ps}XXXXX' and triggering encryption of an already encrypted value. To prevent this, the system has a check for strings starting with '\t{ps}' at the time of parsing URL Parameters or post body.

SR-A17773 · Issue 234118

Custom field value visible for maxloginattempts message

Resolved in Pega Version 7.2.1

In order to support a customized field value message once a user crosses the allowed invalid login attempts threshold, a new overloaded method of prepareStatusInfo() has been introduced in PRDiagnosticStream.java that will not mask the exception details with generic error message.

SR-A17852 · Issue 234570

Edit Validate passes parameters to message rule

Resolved in Pega Version 7.2.1

When using an Edit Validate rule in the condition, functions could not be passed as a parameter into a message rule. This has been fixed.

SR-A17881 · Issue 233850

Browser check added to TextArea for consistent rendering

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, an Enter key press / newline was calculated as two characters during rendering but as a single character in the character counter. This would cause the Text Area to behave differently depending on the browser. To avoid rendering issues, a check has been added to compensate for this difference.

SR-A17916 · Issue 234503

NPS Report drilldown filters corrected

Resolved in Pega Version 7.2.1

The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.

SR-A17916 · Issue 233771

NPS Report drilldown filters corrected

Resolved in Pega Version 7.2.1

The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.

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