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-A19159 · Issue 237816

Enabled custom parameter input for PushBodyCountVar

Resolved in Pega Version 7.2.1

After importing custom markup language based on JSP 2.0 tlds and mustache templates and writing a custom HTML rule to generate JSP, the error s were generated relating to the default value of aTagPushBodyCountVar parameter. To enable the custom input, the generateCustomStart() method has been modified to use a passed-in parameter by way of aTagPushBodyCountVar instead aVisitor.getPushBodyCountVar().

SR-A19167 · Issue 242469

Modified decision table handling for Connect-REST

Resolved in Pega Version 7.2.1

Authorization problems in opening the pyOutboundIdentifierDecoder decision table were causing Connect-REST failures. While it is recommended to only initialize the decision tables for legacy mapping DSS(json/legacyMapping) and not initialize the decision tables for normal JSON mapping, ServiceHelper and RulegeneratorREST have been updated with a check to properly handle the presence of decision tables.

SR-A19172 · Issue 236714

Managed unique constraint violation error for BIX

Resolved in Pega Version 7.2.1

When running multiple extracts using agents and pxExtractDataWithArgs at the same time, a unique constraint violation error was produced in the logs. This occurred when the extracts had the same time stamp down to the millisecond and an entry is added to the pr_log table when each extract starts. The pzInsKey for two extracts that run at the same time was identical, thus leading to this error. To resolve this, the thread name will be appended when the extract is run from an activity.

SR-A19181 · Issue 240871

dropdown menu item names correctly persist after click

Resolved in Pega Version 7.2.1

Once a dropdown was selected from a number of menus in the user portal, the name of the clicked menu disappeared upon recheck. The API has been updated to read the tooltip from the icon element if it is not already present.

SR-A19219 · Issue 237911

RACache performance improved

Resolved in Pega Version 7.2.1

Pega0005 alerts were appearing during system startup, and queries were taking an excessive amount of time. Bind variables are now used in the RACache loading query at server start up to improve performance.

SR-A19242 · Issue 235997

Default team label localized in MyTeams screen

Resolved in Pega Version 7.2.1

Localization has been added to the default team label in the My Teams screen.

SR-A19249 · Issue 238895

Edit validate rule fires properly

Resolved in Pega Version 7.2.1

When submitting a flow action, the edit validate rule would catch properly catch and report an error, but the the same error submitted a second time did not fail. This has been corrected.

SR-A19281 · Issue 235998

Dialogue handling updated for WS-Security Profile password

Resolved in Pega Version 7.2.1

The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.

SR-A19287 · Issue 240328

Static value ProgressBar corrected

Resolved in Pega Version 7.2.1

Using the pzProgressBar control to display integer value on the UI screen was not working after upgrade if the progress bar was bound to a static value and not a update activity. This was caused by a Boolean parameter and an integer parameter to the control being passed as a string, and has been fixed.

SR-A19297 · Issue 237347

Added ability to set custom HTTP security headers

Resolved in Pega Version 7.2.1

XSS protections were interfering with the ability to set custom HTTP headers. To enable this, the system will use dynamic system settings from http/responseHeaders and add them to every HTTP response.

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