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

SR-A17938 · Issue 236489

Custom header section of Calendar retained after Smartinfo popup displayed

Resolved in Pega Version 7.2.1

Due to the way the date/time parameters were handed, the Smartinfo popup was overriding a currency icon and logo set into a custom header of Calendar events to show currency market closings (holiday, etc.). A check for custom values has now been added.

SR-A17941 · Issue 235161

Compatibility mode modal resize resolved

Resolved in Pega Version 7.2.1

When using compatibility mode, launching a modal containing an RTE caused the old deprecated modal dialog to launch as opposed to the supported standards based modal. Clicking the "Maximize" icon caused the work area to go blank; since the modal was no longer displayed, it could not be re-sized or dismissed. The contents of the work area behind the modal also went blank. This was due to known resize issues with the deprecated modal dialog caused by the editor's maximize logic conflicting with the old modal dialog resize logic. To prevent this, the Ckeditor will not fire resizeHarness when the old modal is in use. This stops the resize of the deprecated modal dialog and avoids the conflict between RTE maximize and old modal resize.

SR-A17976 · Issue 239119

Updated SendEmailMessage to handle images with spaces in the filename

Resolved in Pega Version 7.2.1

When an image was inserted into a draft email and sent, the image was visible in PRPC but not at the receiving end. This was a problem with the regex available in the SendEmailMessage activity not being able to handle file names containing spaces: handling for this has now been added.

SR-A18009 · Issue 236493

Default values set for row properties missing after upgrade

Resolved in Pega Version 7.2.1

After upgrade, the default values for .pyUI.pySource.pyRowKeyInfo.pyGetRowKey and .pyUI.pyBody.pyUIFilters.pyGetDistinctRows properties were not set in Rule-Obj-Report-Definition!pzUpgradeOnOpen DataTransform. This caused old reports to not have click action on the grid in report viewer. The system will now set default values for these properties to help the old reports to run as expected post-upgrade.

SR-A18078 · Issue 234051

Hybrid Client errors will display in modal window

Resolved in Pega Version 7.2.1

When an error occurs on the hybrid client of a server, a new window should open with the error. This was not working as expected due to the client passing an invalid URL of "" to Window.open. To better handle this scenario, errors will be displayed in a modal window instead of performing a Window.open if a hybrid client container is in use.

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