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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A17654 · Issue 234844

Stack trace will not display in REST errors

Resolved in Pega Version 7.2.1

To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.

SR-A17654 · Issue 246367

Stack trace will not display in REST errors

Resolved in Pega Version 7.2.1

To improve security, the exception stacktrace generated by a REST Service response will not be displayed as part of the error. The message "An error occurred while processing the request. Please contact your Administrator." will be displayed instead, and the stack trace will be logged.

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-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-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-A18193 · Issue 238469

SystemCleaner correctly purges pr_perf_stats

Resolved in Pega Version 7.2.1

It was noticed that SystemCleaner was working well except for a periodic dramatic purge that suddenly filled logs and sometimes caused a system crash. When BIX runs via command line, this updates the associated DSS in the application. If the DSS usage/usagetrackingenabled or its associated prconfig.xml setting are set to false, Step 12 of the SystemCleaner does not perform a number of activities including regular purging the pr_perf_stats table. This has been modified to remove the setting usage/usagetrackingenabled from prconfig.xml as agents are by default enabled.

SR-A18404 · Issue 235467

New parameter to disable logging of Tidy PDF processing warnings

Resolved in Pega Version 7.2.1

When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.

SR-A18624 · Issue 239177

Fixed post-upgrade data table conversion to local storage

Resolved in Pega Version 7.2.1

After upgrade, updating a data table into a local storage source generated the error "Cannot change keys for a class with (725) instance(s) ". This occurred when the local variable ?classKeysChanged? is true, which happened during comparison of the Key fields of the step page (classPage) and the primary page (ClassForm) because the order of the keys had changed even though the number of keys were same. The "AddProperties" activity has now been modified to check if there are keys already set in the class and if there are any, then skip resaving the class and exit the activity.

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